OraFAQ Forum: SQL & PL/SQL » Oracle NOWAIT ERROR. ORA-00054:

Home » SQL & PL/SQL » SQL & PL/SQL » Oracle NOWAIT ERROR. ORA-00054:

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

Oracle NOWAIT ERROR. ORA-00054: [message #179220]

Mon, 26 June 2006 07:22

frank.svs
Messages: 162
Registered: February 2006

Senior Member

Hi Team,

I am constantly encountering the below NOWAIT error problem. What must be done to avoid this Error.

ORA-00054: resource busy and acquire with NOWAIT specified.

I browsed the net and got the answer as follows :
Cause:
The NOWAIT keyword forced a return to the command prompt because a resource was unavailable for a LOCK TABLE or SELECT FOR UPDATE command.

Action:
Try the command after a few minutes or enter the command without the NOWAIT keyword.

But is there any other answers and what could be the other proberbilities of getting this error.

Regards,
Frank.

Report message to a moderator

Re: Oracle NOWAIT ERROR. ORA-00054: [message #179232 is a reply to message #179220]

Mon, 26 June 2006 07:52

Littlefoot
Messages: 21808
Registered: June 2005
Location: Croatia, Europe

Senior Member
Account Moderator

Usual scenario: you and your colleague are working on the same table. He updated several records and didn't commit changes. Now you want to update (or delete, for example) records in the same table. They are locked and you'll get ORA-00054.

He should either COMMIT or ROLLBACK his transaction(s) in order to allow you to work with the same table.

Does this help? If not, could you better describe your situation?

Report message to a moderator

Re: Oracle NOWAIT ERROR. ORA-00054: [message #179247 is a reply to message #179220]

Mon, 26 June 2006 08:26

navkrish
Messages: 189
Registered: May 2006
Location: NJ,USA

Senior Member

Ask ur administrator to kill the session which is imposing the NOWAIT condition...But make sure that killing the session does not create any production issue...

Report message to a moderator

Re: Oracle NOWAIT ERROR. ORA-00054: [message #179252 is a reply to message #179247]

Mon, 26 June 2006 08:43

Frank
Messages: 7901
Registered: March 2000

Senior Member

navkrish wrote on Mon, 26 June 2006 15:26

Ask ur administrator to kill the session which is imposing the NOWAIT condition...But make sure that killing the session does not create any production issue...

This makes no sense. The session using the nowait is the session that is terminated with an error, so there is no session to be killed.

Investigate which lock you are trying to get, then which session holds this lock
Note that you could also get this error if you did not explicitly ask for a nowait-lock, but tried a DDL statement.

hth

Report message to a moderator