>Hello,
>
>System Specs:
> Sun Enterprise 5000
> 1 Gb RAM
> IDS 7.24.UC5
>
>Earlier this week, our database engine hung. There was no error
>message,
>users could not connect, and we could not shut the database down. We
>finally did a 'kill -9' on the processes, rebooted the server, and then
>did
>an index check. We have no idea what is causing this problem. Informix
>support hasn't been able to give us any good clues.
>
>Anyone have any ideas?
>
>Thanks,
>
>cindy
>
Cindy,
In order to diagnose a problem like this, we will have to have information
about what was going on at the time of the hang, several onstat -g ath, onstat
-g stk of any threads which seem to be constantly running, etc.
However, in most hung system situations, there is so much confusion and urgency
to get the system back running, that the capture of this information is not of
the highest priority. Hopefully you were able to capture this information. If
so then this information would need to be in the case notes.
The fact that you could not run onmode -ky indicates that the onmonitor thread
was not able to get serviced. This could indicate a mutex deadly embrace, tcp
socket hang, or possibably a run-a-way thread that prevented the onmonitor
thread from getting access to the cpuvp.
Do you have the case number?
Madison Pruet