I have seen this happen a few times as a result of mutex blocking. Oracle's
suggestion is to turn off mutexes (assuming you are using them). I can dig
up the parameter if you are interested. Because you cannot login, they are a
bear to trace. You can go after them with a debugger like gdb or the popular
shared-memory linkers that a few geniuses have worked on.
On 3/15/07, ryan_gaffuri_at_comcast.net <ryan_gaffuri_at_comcast.net> wrote:
>
> no error messages. Nothing in any of the logs.
>
> sqlplus
> <hang>
>
> I saw this happen when you do a bulk collect with no limit clause and suck
> up so much memory you can't log in. I searched the code. This is not the
> issue.
>
>
> -------------- Original message --------------
> From: "Don Seiler" <don_at_seiler.us>
>
> > On 3/14/07, ryan_gaffuri_at_comcast.net wrote:
> > > I had a problem last night where you could not log into sql plus.
> >
> > What, exactly, is the ORA error you are seeing? That would probably
> > go a long way to identifying exactly why you can't log in. And by
> > "log into sql plus" I assume you mean using sqlplus to log into your
> > database, and not just launch sqlplus without connecting
> >
> > Don.
> >
> > --
> > Don Seiler
> > http://seilerwerks.blogspot.com
>
>
--
Charles Schultz
--
http://www.freelists.org/webpage/oracle-l
Received on Thu Mar 15 2007 - 10:20:49 CDT
