Re: "Oracle Lock Won't Go Away : ORA-00054: resource busy and acquire with NOWAIT specified

Hi,

Stopping and starting did not help ?? Sounds impossible and like somnething that is
executed before you look again. Oracle doesn't remove sessions if they're doing something rather essential. For me also a bit vague. Are you sure you're looking at the right session ? Try to find out through v$session and v$sqlarea which script is doing exactly what because i suspect something
else is doing something unexpected. Maybe you can put a commit or rollback in this Unix-script when it ends prematurely to be sure it doesn't happen again.

Jeroen

matthew.deal_at_cox.com wrote:

> Hi: I've got a scenario where a UNIX script acquired a DML lock on a table.
> This was evident by performing query "select v$session". The script was
> terminated prematurely, but the lock still exists on the table. No INSERTs
> or DROP of table is allowed or the message "ORA-00054: resource busy and
> acquire with NOWAIT specified" is presented. A simple SELECT works ok. I
> performed an "alter system kill session '22,33'" in an attempt to remove the
> lock. The status of the lock changed to "killed", but the lock still exists.
> The method of "alter system ..." had worked previously for other locks
> resulting from the initial lock. If I can't commit or rollback, and I can't
> drop the table, how do I remove the lock? Stopping and starting the db did
> nothing to the lock.
>
> -----== Posted via Deja News, The Leader in Internet Discussion ==-----
> http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum
Received on Mon Aug 03 1998 - 05:13:56 CDT