EXP-00054: error on row %lu of subpartition %s
ORA-00054: Resource busy and acquire with NOWAIT specified
Wait and try the command again after a few minutes.
or
Execute the command without the NOWAIT keyword.
Let's say we have 2 session, one session updates a table:
SQL> create table test (n number);
Table created.
SQL> insert into test values(1);
1 row created.
SQL> commit;
Commit complete.
SQL> update test set n=2;
1 row updated.
--> NO COMMIT yet
Now, the other session is trying to select a record for update:
eg:
SQL> declare
2 n number;
3 begin
4 select n into n from test for update nowait;
5 end;
6 /
declare
*
ERROR at line 1:
ORA-00054: resource busy and acquire with NOWAIT specified
ORA-06512: at line 4
Welcome to our forum for Oracle error: ORA-00054 Add your own message
I have one TBS in 8i which consists only one DBF , which is under one user it contains 53 master tables and 19 transaction tables, each tx table contains 5 10 lakh rows , performance is very low how shold i increase d performance ? and if i want to migrate it to 11g then how can i ? its on windows.
plz do help me
It might be of missing indexes, invalid joins, ...
For the transfer to Oracle 11g, you have a number of options.
You can use the old exp/imp, use datapump or investigate using transportable tablespaces
I started importing meanwhile i forget to disable the constraints,while the table is about to start import i tried to disable the constraints.then i got this error.how can i proceed now.Please respond fast clint is waiting.
It is possible the latter 2 data dictionary views do not exist, if that is the case, run ?/rdbms/admin/catblock as SYS user to create the Data dictionary views
Thanks a lot
How can i know (which value of column )can indicate me what is caused the lock and shall i keep a session on line or not ?
Thanks for help
can see in this link : http://programacion.com/simple/foros/34/msg/79372/
maybe.. is the answer.
i cant able to rebuild the index in peak hour
since that particular table has 1 crore of records..
what would be the solution for this issue
select sid from v$lock where id1=(select object_id from dba_objects where owner='HERE_OWNER' and object_name='HERE_OBJECT');
You can then kill that session
Check v$lock and dba_dml_locks and/or dba_ddl_locks to see what is causing the lock.
Helped a lot, it was real pain in ass, to get rid of this error. Almost finalized to take shutdwon. But this article helpled a lot.
GONAGPUR.COM
Add your message
If you need more information about this particular error message, you can leave a forum message.
We are replying to this message whenever we have some spare time, so please do not consider this as a private 'solve my critical issue asap' service.
Should you need professional Oracle Assistance to make your project a success, please have a look at our consultancy services.
In order to prevent automatic generation of messages, we are asking for a validation code. This code is unique and is generated every time a new message is asked.
If you do not enter the validation correctly, your message will not be recorded.