Re: SQL*Net message to client

Let me first give thanks for your help.

If you don't mind teaching me to fish, how could I have ascertained this explanation on my own?

Little more can be collected on this event. The impatient dba took the sledge hammer approach to the log switch-hung db.

There were no user sessions listed in v$session. The other wait events were the log switch and a 220 buffer busy, both waiting for the same period of time. Oradocs say the 220 is, "during buffer lookup for a CURRENT copy of a buffer we have found the buffer but someone holds it in an incompatible mode so we have to wait."

So, I'm curious who this client might have been. There is no knowing for certain since the evidence has been destroyed. What are the possible "clients?" Seems like a bug, unless client means something I don't think it means.

On Wed, Nov 23, 2005 at 07:56:01PM -0000, Jonathan Lewis wrote:
> wait_time=-1 means less than 1 hundredth
> of a second for 8i, and less than 50 milliseconds
> for later versions of 9.

--
http://www.freelists.org/webpage/oracle-l