Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: ideas needed to track down a mysterious problem
On Sun, 13 May 2007 13:01:03 +0200, "Matthias Hoys" <anti_at_spam.com>
wrote:
>
>"prunoki" <hegyvari_at_ardents.hu> wrote in message
>news:1179045404.300974.260720_at_y80g2000hsf.googlegroups.com...
>> Hi,
>>
>> Currently we are in the process of establishing a diagnostic sheet in
>> order to help us track down a problem. One of our clients is running a
>> 8.1.7.2 database on Solaris. Sometimes the application this database
>> supports comes to a halt. When this happened we made sure that there
>> were no locks to justify this situation and we started to log off
>> everyone, set job_queue_processes to 0, killed the jobs, so basically
>> stopped everyone from using the database. The database was still
>> unresponsive and we could not get a system state dump (it just would
>> not finish doing the dump). After restarting everything became normal.
>>
>> Right now I started to establish a protocol, organizing the todo-s
>> into steps which should be taken before restarting. It is something
>> like:
>>
>> - examine the active sessions
>> - examine the logs
>> - check the CPU and disk resources
>> - etc
![]() |
![]() |