Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Remove DBMS_LOCK Locks

Re: Remove DBMS_LOCK Locks

From: <sybrandb_at_hccnet.nl>
Date: Wed, 20 Jun 2007 23:34:10 +0200
Message-ID: <r87j739b8lkdc4ehtmqlr1l919hkaj48j4@4ax.com>


On Wed, 20 Jun 2007 15:41:52 -0400, "klabu" <klabu_at_mailinator.com> wrote:

><sybrandb_at_hccnet.nl>
>> From your post it is unclear how you are calling dbms_lock.release.
>> You didn't type *litterally*
>> exec dbms_lock.release(<lockid>);
>> did you?
>>
>> --
>> Sybrand Bakker
>> Senior Oracle DBA
>
>oh NO ! haha
>
>this is the real spool here:
>
>select * from sys.dbms_lock_allocated ;
>
>NAME LOCKID EXPIRATION
>---------------- ------------------ ----------------
>REINSCHUNKING28 1073742457 18-Mar-2007
>REINSCHUNKING301 1073742458 18-Mar-2007
>REINSCHUNKING302 1073742459 18-Mar-2007
>REINSCHUNKING303 1073742460 18-Mar-2007
>REINSCHUNKING304 1073742461 18-Mar-2007
>REINSCHUNKING305 1073742462 18-Mar-2007
><snip>
>
>
>SQL> exec dbms_output.put_line(DBMS_LOCK.RELEASE(1073742457));
>
>3
>
>PL/SQL procedure successfully completed
>
>SQL> exec dbms_output.put_line(DBMS_LOCK.RELEASE(1073742459));
>
>3
>
>PL/SQL procedure successfully completed
>

So it looks like you need to find out from the documentation (you know, that thingy you refuse to read) what a return status of *3* means.

-- 
Sybrand Bakker
Senior Oracle DBA
Received on Wed Jun 20 2007 - 16:34:10 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US