Oracle錯誤ORA-00054:resource busy and acquire with nowait specified解決方法
(select * from talbe for update nowait)
當某個數據庫用戶在數據庫中插入、更新、刪除一個表的數據，或者增加一個表的主鍵時或者表的索引時，常常會出現ora-00054:resource busy and acquire with nowait specified這樣的錯誤。
主要是因爲有事務正在執行（或者事務已經被鎖），所有導致執行不成功。
1、用dba權限的用戶查看數據庫都有哪些鎖
select t2.username,t2.sid,t2.serial#,t2.logon_time
from v$locked_object t1,v$session t2
where t1.session_id=t2.sid order by t2.logon_time;
如：testuser 339 13545 2009-3-5 17:40:05
知道被鎖的用戶testuser，sid爲339，serial#爲13545
2、根據sid查看具體的sql語句，如果sql不重要，可以kill
select sql_text from v$session a,v$sqltext_with_newlines b
where DECODE(a.sql_hash_value, 0, prev_hash_value, sql_hash_value)=b.hash_value
and a.sid=&sid order by piece;
查出來的sql，如： begin :id := sys.dbms_transaction.local_transaction_id; end;
3、kill該事務
alter system kill session '339,13545';
4、這樣就可以執行其他的事務sql語句了
如增加表的主鍵：
alter table test
add constraint PK_test primary key (test_NO)；
· alter system kill session 'sid , serial# ';
· alter system kill session '119, 34889';
· --SELECT * FROM V$SESSION;
--1.查出鎖定object的session的信息以及被鎖定的object名
SELECT l.session_id sid, s.serial#, l.locked_mode,l.oracle_username,
l.os_user_name,s.machine, s.terminal, o.object_name, s.logon_time
FROM v$locked_object l, all_objects o, v$session s
WHERE l.object_id = o.object_id
AND l.session_id = s.sid
ORDER BY sid, s.serial# ;
--2.查出鎖定表的session的sid, serial#,os_user_name, machine name, terminal和執行的語句
--比上面那段多出sql_text和action
SELECT l.session_id sid, s.serial#, l.locked_mode, l.oracle_username, s.user#,
l.os_user_name,s.machine, s.terminal,a.sql_text, a.action
FROM v$sqlarea a,v$session s, v$locked_object l
WHERE l.session_id = s.sid
AND s.prev_sql_addr = a.address
ORDER BY sid, s.serial#;
--3.查出鎖定表的sid, serial#,os_user_name, machine_name, terminal，鎖的type,mode
SELECT s.sid, s.serial#, s.username, s.schemaname, s.osuser, s.process, s.machine,
s.terminal, s.logon_time, l.type
FROM v$session s, v$lock l
WHERE s.sid = l.sid
AND s.username IS NOT NULL
ORDER BY sid;
這個語句將查找到數據庫中所有的DML語句產生的鎖，還可以發現，
任何DML語句其實產生了兩個鎖，一個是表鎖，一個是行鎖。
殺鎖命令
alter system kill session 'sid,serial#'
SELECT /*+ rule */ s.username,
decode(l.type,'TM','TABLE LOCK',
'TX','ROW LOCK',
NULL) LOCK_LEVEL,
o.owner,o.object_name,o.object_type,
s.sid,s.serial#,s.terminal,s.machine,s.program,s.osuser
FROM v$session s,v$lock l,dba_objects o
WHERE l.sid = s.sid
AND l.id1 = o.object_id(+)
AND s.username is NOT NULL
如果發生了鎖等待，我們可能更想知道是誰鎖了表而引起誰的等待
以下的語句可以查詢到誰鎖了表，而誰在等待。
以上查詢結果是一個樹狀結構，如果有子節點，則表示有等待發生。
如果想知道鎖用了哪個回滾段，還可以關聯到V$rollname，其中xidusn就是回滾段的USN
col user_name format a10
col owner format a10
col object_name format a10
col object_type format a10
select lpad(' ',decode(l.xidusn ,0,3,0))||l.oracle_username user_name,
o.owner,o.object_name,o.object_type,s.sid,s.serial#
from v$locked_object l,dba_objects o,v$session s
where l.object_id=o.object_id
and l.session_id=s.sid
order by o.object_id,xidusn desc
附：
select
s.username,
decode(l.type,'tm','table lock','tx','row lock',null) lock_level,
o.owner,
o.object_name,
o.object_type,
s.sid,
s.serial#,
s.terminal,
s.machine,
s.program,
s.osuser
from v$session s,v$lock l,dba_objects o
where l.sid = s.sid
and l.id1 = o.object_id(+)
and s.username is not null;
--kill session語句
alter system kill session'50,492';
--以下幾個爲相關表
SELECT * FROM v$lock;
SELECT * FROM v$sqlarea;
SELECT * FROM v$session;
SELECT * FROM v$process ;
SELECT * FROM v$locked_object;
SELECT * FROM all_objects;
SELECT * FROM v$session_wait;
