Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> 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_at_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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2652.35">
<TITLE>RE: sql statement "hanging" and unable to query v$lock =
- Oracle 8</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Please see my comments at the bottom.</FONT>
</P>
<P><FONT SIZE=3D2>My question:</FONT>
<BR><FONT SIZE=3D2>> -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>> Sent: Thursday, 11 January 2001 9:41</FONT>
<BR><FONT SIZE=3D2>> To: Multiple recipients of list ORACLE-L</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> But when I</FONT>
<BR><FONT SIZE=3D2>> try to query v$lock (I typed in "select * =
from v$lock" in </FONT>
<BR><FONT SIZE=3D2>> SQL*Plus on the</FONT>
<BR><FONT SIZE=3D2>> server) that query hangs too! At least it never =
returns back </FONT>
<BR><FONT SIZE=3D2>> to the prompt.</FONT>
<BR><FONT SIZE=3D2>> ...</FONT>
<BR><FONT SIZE=3D2>> How do I find out why the process is hanging? I =
don't see any </FONT>
<BR><FONT SIZE=3D2>> ORA- errors in</FONT>
<BR><FONT SIZE=3D2>> the alert log. </FONT>
</P>
<P><FONT SIZE=3D2>Bruce suggested:</FONT>
</P>
<P><FONT SIZE=3D2>> -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>> From: Reardon, Bruce (CALBBAY)</FONT>
<BR><FONT SIZE=3D2>> [<A =
HREF=3D"mailto:Bruce.Reardon_at_comalco.riotinto.com.au">mailto:Bruce.Reard=
on_at_comalco.riotinto.com.au</A>]</FONT>
<BR><FONT SIZE=3D2>> Sent: mercredi, 10. janvier 2001 15:05</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Try querying dba_blockers and dba_waiters - =
these might give </FONT>
<BR><FONT SIZE=3D2>> the sid of the</FONT>
<BR><FONT SIZE=3D2>> blocking session.</FONT>
<BR><FONT SIZE=3D2>> If these views don't exist then you can create =
them with the </FONT>
<BR><FONT SIZE=3D2>> catblock.sql</FONT>
<BR><FONT SIZE=3D2>> script found in rdms/admin directory.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Also, if you have OEM, try using the lock =
monitor tool.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Alternatively, if it doesn't show up here, look =
in </FONT>
<BR><FONT SIZE=3D2>> dba_lock_internal.</FONT>
</P>
<P><FONT SIZE=3D2>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.</FONT></P>
<P><FONT SIZE=3D2>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".</FONT></P>
<P><FONT SIZE=3D2>I would apreciate any other advice. I think that at =
this point I may resort to re-booting the DB since it's development =
Received on Wed Jan 10 2001 - 17:33:27 CST
![]() |
![]() |