Oracle外键不加索引引起死锁示例
更新时间:2014年05月15日 16:22:23 作者:
这篇文章主要介绍了Oracle外键不加索引引起死锁的情况及解决,需要的朋友可以参考下
--创建一个表,此表作为子表
create table fk_t as select *from user_objects;
delete from fk_t where object_id is null;
commit;
--创建一个表,此表作为父表
create table pk_t as select *from user_objects;
delete from pk_t where object_id is null;
commit;
--创建父表的主键
alter table PK_t add constraintpk_pktable primary key (OBJECT_ID);
--创建子表的外键
alter table FK_t addconstraint fk_fktable foreign key (OBJECT_ID) references pk_t (OBJECT_ID);
--session1:执行一个删除操作,这时候在子表和父表上都加了一个Row-S(SX)锁
delete from fk_t whereobject_id=100;
delete from pk_t where object_id=100;
--session2:执行另一个删除操作,发现这时候第二个删除语句等待
delete from fk_t whereobject_id=200;
delete from pk_t whereobject_id=200;
--回到session1:死锁马上发生
delete from pk_t whereobject_id=100;
session2中报错:
SQL> delete from pk_table where object_id=200;
delete from pk_table where object_id=200
*
第 1 行出现错误:
ORA-00060: 等待资源时检测到死锁
当对子表的外键列添加索引后,死锁被消除,因为这时删除父表记录不需要对子表加表级锁。
--为外键建立索引
create index ind_pk_object_id on fk_t(object_id) nologging;
--重复上面的操作session1
delete from fk_t whereobject_id=100;
delete from pk_t whereobject_id=100;
--session2
delete from fk_t whereobject_id=200;
delete from pk_t whereobject_id=200;
--回到session1不会发生死锁
delete from pk_t whereobject_id=100;
create table fk_t as select *from user_objects;
delete from fk_t where object_id is null;
commit;
--创建一个表,此表作为父表
create table pk_t as select *from user_objects;
delete from pk_t where object_id is null;
commit;
--创建父表的主键
alter table PK_t add constraintpk_pktable primary key (OBJECT_ID);
--创建子表的外键
alter table FK_t addconstraint fk_fktable foreign key (OBJECT_ID) references pk_t (OBJECT_ID);
--session1:执行一个删除操作,这时候在子表和父表上都加了一个Row-S(SX)锁
delete from fk_t whereobject_id=100;
delete from pk_t where object_id=100;
--session2:执行另一个删除操作,发现这时候第二个删除语句等待
delete from fk_t whereobject_id=200;
delete from pk_t whereobject_id=200;
--回到session1:死锁马上发生
delete from pk_t whereobject_id=100;
session2中报错:
SQL> delete from pk_table where object_id=200;
delete from pk_table where object_id=200
*
第 1 行出现错误:
ORA-00060: 等待资源时检测到死锁
当对子表的外键列添加索引后,死锁被消除,因为这时删除父表记录不需要对子表加表级锁。
--为外键建立索引
create index ind_pk_object_id on fk_t(object_id) nologging;
--重复上面的操作session1
delete from fk_t whereobject_id=100;
delete from pk_t whereobject_id=100;
--session2
delete from fk_t whereobject_id=200;
delete from pk_t whereobject_id=200;
--回到session1不会发生死锁
delete from pk_t whereobject_id=100;
相关文章
Oracle插入数据时出现ORA-00001:unique constraint问题
这篇文章主要介绍了Oracle插入数据时出现ORA-00001:unique constraint问题,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教2024-03-03
Oracle在表中有数据的情况下修改字段类型或长度的解决方法
这篇文章主要介绍了Oracle在表中有数据的情况下修改字段类型或长度,修改其某个字段的类型或改变他的长度,由于表中有数据,不能直接修改,需要换个方法,接下来通过本文给大家介绍下解决方法,需要的朋友可以参考下2022-10-10
Oracle 中 row_number()、rank()、dense_rank() 函数的
rank() 与 row_number() 的区别在于,rank() 会按照排序值相同的为一个序号(以下称为:块),第二个不同排序值将显示所有行的递增值,而不是当前序号加1,下面通过示例介绍下Oracle 中 row_number()、rank()、dense_rank() 函数的用法,一起看看吧2024-03-03


最新评论