Home » SQL & PL/SQL » SQL & PL/SQL » Drop table wouldn't work
Drop table wouldn't work [message #19353] Tue, 12 March 2002 23:03 Go to next message
Julez
Messages: 6
Registered: March 2002
Junior Member
Hi,
i was trying to do this

SQL> drop table abs02;
drop table abs02
*
ERROR at line 1:
ORA-00054: resource busy and acquire with NOWAIT specified

SQL> desc abs02;
Name Null? Type
---------------------- -------- --
id NOT NULL VARCHAR2(10)
eop NOT NULL CHAR(6)
salary NUMBER(9)
create_dt DATE

while it is working with abs01, abs03 ... etc
why is it happening.. what should i do ?

thank you
Re: Drop table wouldn't work [message #19369 is a reply to message #19353] Wed, 13 March 2002 04:57 Go to previous messageGo to next message
Cindy
Messages: 88
Registered: November 1999
Member
It means you are attempting to perform an operation that would be blocked, but the operation does not permit blocking. Oracle issues TM locks to ensure that the structure of a table is not altered while you are modifying its contents. For Example: if you have updated, inserted, or deleted a table, you will acquire a TM lock on that table. This will prevent you or other users from executing DROP or ALTER commands on that table. Therefore if you attempt to perform DDL on the table while you have a TM lock on it, you will receive the ORA-00054 error message. To release TM lock do a commit or rollback then try dropping the table again.
Re: Drop table wouldn't work [message #20302 is a reply to message #19353] Sun, 12 May 2002 11:36 Go to previous message
Tom Reger
Messages: 1
Registered: May 2002
Junior Member
I am also trying to drop the table but one of my own processes has the table locked. (ORA-00054). How do I find that process or unlock the table
Previous Topic: How do I callprocedure from trigger
Next Topic: Debugging tool
Goto Forum:
  


Current Time: Thu Apr 25 08:04:06 CDT 2024