Message-Id: <10737.126352@fatcity.com> From: Jacques Kilchoer Date: Wed, 10 Jan 2001 15:33:27 -0800 Subject: RE: sql statement "hanging" and unable to query v$lock - Oracle 8 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C07B5D.BBAC4C60 Content-Type: text/plain; charset="iso-8859-1" Please see my comments at the bottom. My question: > -----Original Message----- > Sent: Thursday, 11 January 2001 9:41 > To: Multiple recipients of list ORACLE-L > > But when I > try to query v$lock (I typed in "select * from v$lock" in > SQL*Plus on the > server) that query hangs too! At least it never returns back > to the prompt. > ... > How do I find out why the process is hanging? I don't see any > ORA- errors in > the alert log. Bruce suggested: > -----Original Message----- > From: Reardon, Bruce (CALBBAY) > [mailto:Bruce.Reardon@comalco.riotinto.com.au] > Sent: mercredi, 10. janvier 2001 15:05 > > Try querying dba_blockers and dba_waiters - these might give > the sid of the > blocking session. > If these views don't exist then you can create them with the > catblock.sql > script found in rdms/admin directory. > > Also, if you have OEM, try using the lock monitor tool. > > Alternatively, if it doesn't show up here, look in > dba_lock_internal. Thank you for your suggestions. I tried to run catblock.sql but the creation script is "hung" also. So I don't have access to the dba_ views you mention. As far as OEM goes, I'm brand new here and haven't installed it yet. The CD we have here is OEM 2.1 and I thought I needed to run a middle-end "management server" on some UNIX server for OEM, so I haven't tried it yet since I don't have any "management servers". I would apreciate any other advice. I think that at this point I may resort to re-booting the DB since it's development anyway. ------_=_NextPart_001_01C07B5D.BBAC4C60 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: sql statement "hanging" and unable to query v$lock = - Oracle 8

Please see my comments at the bottom.

My question:
> -----Original Message-----
> Sent: Thursday, 11 January 2001 9:41
> To: Multiple recipients of list ORACLE-L
>
> But when I
> try to query v$lock (I typed in "select * = from v$lock" in
> SQL*Plus on the
> server) that query hangs too! At least it never = returns back
> to the prompt.
> ...
> How do I find out why the process is hanging? I = don't see any
> ORA- errors in
> the alert log.

Bruce suggested:

> -----Original Message-----
> From: Reardon, Bruce (CALBBAY)
> [mailto:Bruce.Reard= on@comalco.riotinto.com.au]
> Sent: mercredi, 10. janvier 2001 15:05
>
> Try querying dba_blockers and dba_waiters - = these might give
> the sid of the
> blocking session.
> If these views don't exist then you can create = them with the
> catblock.sql
> script found in rdms/admin directory.
>
> Also, if you have OEM, try using the lock = monitor tool.
>
> Alternatively, if it doesn't show up here, look = in
> dba_lock_internal.

Thank you for your suggestions. I tried to run = catblock.sql but the creation script is "hung" also. So I = don't have access to the dba_ views you mention.

As far as OEM goes, I'm brand new here and haven't = installed it yet. The CD we have here is OEM 2.1 and I thought I needed = to run a middle-end "management server" on some UNIX server = for OEM, so I haven't tried it yet since I don't have any = "management servers".

I would apreciate any other advice. I think that at = this point I may resort to re-booting the DB since it's development =