oracle表锁的几种模式v$locked_object-locked_mode
0:none
1:null 空
2:Row-S 行共享(RS):共享表锁,sub share
3:Row-X 行独占(RX):用于行的修改,sub exclusive
4:Share 共享锁(S):阻止其他DML操作,share
5:S/Row-X 共享行独占(SRX):阻止其他事务操作,share/sub
exclusive
6:exclusive 独占(X):独立访问使用,exclusive
数字越大锁级别越高, 影响的操作越多。
1级锁有:Select,有时会在v$locked_object出现。
2级锁有:Select for update,Lock For Update,Lock Row
Share
select for update当对话使用for
update子串打开一个游标时,所有返回集中的数据行都将处于行级(Row-X)独占式锁定,
其他对象只能查询这些数据行,不能进行update、delete或select for update操作。
3级锁有:Insert, Update, Delete, Lock Row Exclusive
没有commit之前插入同样的一条记录会没有反应, 因为后一个3的锁会一直等待上一个3的锁,
我们必须释放掉上一个才能继续工作。
4级锁有:Create Index, Lock Share
locked_mode为2,3,4不影响DML(insert,delete,update,select)操作,
但DDL(alter,drop等)操作会提示ora-00054错误。
00054, 00000, "resource busy and acquire with NOWAIT
specified"
// *Cause: Resource interested is busy.
// *Action: Retry if necessary.
5级锁有:Lock Share Row Exclusive
具体来讲有主外键约束时update / delete ... ; 可能会产生4,5的锁。
6级锁有:Alter table, Drop table, Drop Index, Truncate table, Lock
Exclusive
以DBA角色, 查看当前数据库里锁的情况可以用如下SQL语句:
col owner for a16
col object_name for a16
SELECT b.owner, b.object_name, l.session_id, s.serial#,
l.locked_mode
FROM v$locked_object l, dba_objects b, v$session s
WHERE b.object_id = l.object_id
AND s.sid = l.session_id
ORDER BY 1,2,3,4;
set linesize 200;
SELECT s.username, s.sid, s.serial#,
to_char(s.logon_time,'yyyy-mm-dd hh24:mi:ss') logon_time
FROM v$locked_object l, v$session s
WHERE l.session_id = s.sid
ORDER BY 3;
SELECT d.object_name,s.sid, s.serial#
FROM v$locked_object l, dba_objects d, v$session s
WHERE l.object_id = d.object_id
AND l.session_id = s.sid
ORDER BY 1, 2, 3;
SELECT s.sid, s.serial#, d.object_name, d.owner
FROM v$lock l, dba_objects d, v$session s
WHERE l.id1 = d.object_id
AND l.sid = s.sid
AND d.owner = 'PROENV_PREPAID'
ORDER BY 1, 2, 3, 4;
set linesize 200;
col username for a16
col object_owner for a16
col object_name for a16
col locked_mode for a12
col machine for a12
col os_user_name for a14
SELECT l.session_id AS sid, s.serial#, s.machine,
to_char(s.logon_time,'yyyy-mm-dd hh24:mi:ss')
logon_time,
NVL(l.oracle_username, '(oracle)') AS
username,
d.owner AS object_owner,
d.object_name,
Decode(l.locked_mode, 0,
'None',
1, 'Null
(NULL)',
2, 'Row-S
(SS)',
3, 'Row-X
(SX)',
4, 'Share
(S)',
5, 'S/Row-X
(SSX)',
6,
'Exclusive (X)',
l.locked_mode)
locked_mode,
l.os_user_name
FROM dba_objects
d,
v$locked_object l,
v$session s
WHERE d.object_id = l.object_id
AND s.sid = l.session_id
ORDER BY 3, 1, 2, 4, 5;
如果有长期出现的一列,可能是没有释放的锁。我们可以用下面SQL语句杀掉长期没有释放非正常的锁:
alter system kill session 'sid,serial#';
如果出现了锁的问题, 某个DML操作可能等待很久没有反应。
当你采用的是直接连接数据库的方式,也不要用OS系统命令 $kill process_num 或者 $kill -9
process_num来终止用户连接,
因为一个用户进程可能产生一个以上的锁, 杀OS进程并不能彻底清除锁的问题。
!!The End!!