Our problem was minimal - this is strictly a demo environment, the
services had been interrupted over the weekend during power testing.
We haven't seen any deadlocks yet, but I'll keep that in mind in the
I just found the http message amusing since our sys admins are always
convinced the DBA's have done something bad that we're neglecting to
mention. Of course, the DBA believe the same thing of the developers
and the developers expect the same from the users ...
On 7/18/05, Pakhutkin, Maxim (Max) <maxim.pakhutkin@(protected):
> Were there any deadlocks (ORA-00060
) reported in the repository alert log at the same time? I've seen occasions where I would get a "page cannot be displayed" at about the same time a deadlock is detected in the repository. It's back to normal once the deadlock is resolved by the database server. The agent on the web server host may, depending on timing, also notify you that OC4J instance is down at that time. I've had 2 deadlocks in 11 most recent days with 129 monitoring targets and 14 agents.
> Max Pakhutkin
> -----Original Message-----
> From: oracle-l-bounce@(protected)
> Sent: Monday, July 18, 2005 9:31 AM
> To: oracle-l@(protected)
> Subject: 10g grid control error
> Came in this morning to the following error from the 10g Grid control
> console login:
> Internal Server Error
> The server encountered an internal error or misconfiguration and was
> unable to complete your request.
> Please contact the server administrator, you@(protected)
> them of the time the error occurred, and anything you might have done
> that may have caused the error.
> More information about this error may be available in the server error log.
> Oracle-HTTP-Server/1.3.28 Server at kirk Port 4889
> Guess I need to call my unix admin and start confessing my sins...