Re: AW: not able to connect to the database

From: Martin Berger <martin.a.berger_at_gmail.com>
Date: Sat, 29 Nov 2008 10:17:16 +0100
Message-Id: <0E733F89-ED52-416F-833F-CF324892909C@gmail.com>

If you are really waiting for a library lock and NEVER get it, event 10046 will not show this issue, as it gets only written when the lock comes back
(otherwise it could not write any timing information.

So if you doesn't find anything useful in the tracefile, you might have to start tracing the session on OS-level. See Tanel Põders blog for a lot of information how to do this. http://blog.tanelpoder.com/

best regards,
  Martin

--
Martin Berger
http://berxblog.blogspot.com

Am 29.11.2008 um 10:10 schrieb Stefan Knecht:


> If you are able to connect as sys, and query v$session, but not v
> $lock this may be some library cache issue.
>
> Try this:
>
> sqlplus / as sysdba
> alter session set tracefile_identifier='FOO';
> alter session set events '10046 trace name context forever, level 12';
> select * from v$lock;
>
> Then, let that session sit there and wait for a couple moments - a
> minute or two, and look in user_dump_dest for a file with FOO in its
> name. What's the WAIT lines that you see in there ?
>

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

  • application/pkcs7-signature attachment: smime.p7s
Received on Sat Nov 29 2008 - 03:17:16 CST

Original text of this message