Any idea why we can't get an oncheck -cc on our big database ?
We have 5 instances on this box, one of them is a terabyte, with about 80,000 tables.
Oncheck -cc runs perfectly on all of them except the big one. It seems to just hang there. After 2 days, it has given zero output, is still showin up in the ps -ef, and the onstat -u, but is gaining no time, as if it is just hung.

Thanks,
floyd









========================
-<<Floyd Wellershaus>>-
Database Administrator
Unix Administrator



email: fwellers@yahoo.com


Home: 703-430-0805


Cell: 703-477-6045
========================


http://www.one.org/

Floyd Wellershaus wrote:
> Any idea why we can't get an oncheck -cc on our big database ?
> We have 5 instances on this box, one of them is a terabyte, with about 80,000 tables.
> Oncheck -cc runs perfectly on all of them except the big one. It seems to just hang there. After 2 days, it has given zero output, is still showin up in the ps -ef, and the onstat -u, but is gaining no time, as if it is just hung.
>
> Thanks,
> floyd
>

Which IDS version?

onstat -g ath ..what state are the oncheck threads in?

onstat -g stk on each thread. what does that give? does it change?

onstat -g tpf - do any values for the threads change?

select sid from sysrstcb where tid = <thread id>

onstat -g ses <sid> what does that give?

select * from syssesprof where sid = <sid> does that change?

onstat -s and onstat -g lmx.. any mutexes /latches begin held for > 5
minutes?

Is an archive running?

If nothing appears to be moving then contact IBM Tech Support.

NOTE: With that many tables consider increasing DS_ and DD_ onconfig
parameters to cache the table info.
They are documented in the IDS 10 docs and available (sometimes
undocumented) in all versions.

David.