Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
TX-000d0000-00037316 40 829 X 48 976 X
TX-0002002a-0004002d 48 976 X 40 829 X
session 829: DID 0001-0028-000F18E1 session 976: DID 0001-0030-0014B716
session 976: DID 0001-0030-0014B716 session 829: DID 0001-0028-000F18E1
Rows waited on:
Session 976: obj - rowid = 0000E44C - AAAORMAAEAAAFPiAA3
(dictionary objn - 58444, file - 4, block - 21474, slot - 55)
Session 829: obj - rowid = 0000E44C - AAAORMAAEAAAE/qABJ
(dictionary objn - 58444, file - 4, block - 20458, slot - 73)
Information on the OTHER waiting sessions:
Session 976:
pid=48 serial=14234 audsid=-1 user: 0/SYS
O/S info: user: oracle, term: , ospid: 18860, machine: BJ-FT-1F-118-2
program: rman@192-168-118-2 (TNS V1-V3)
application name: rman@192-168-118-2 (TNS V1-V3), hash value=2232638999
action name: 0000009 FINISHED129, hash value=347821186
Current SQL information unavailable
End of information on OTHER waiting sessions.
Current SQL statement for this session:
DELETE FROM AUDIT_LOGIN_DB WHERE LOGON_DATE < SYSDATE-30
从以上的报错信息来看，删除audit_login_db表的数据。
分析后的结果是有可能的，不过这个情况也实属罕见。登陆审计，然后清理数据。一交叉死锁了。不是RMAN的错。
RMAN会连接数据库，审计表记录登陆信息，删除。这些因素就够了。不是备份本身引起的，原因是登陆。我觉得。
RMAN会多进程连接的，很容易交叉了。具体分析trace吧。应该看得出来。
rman会造成delete死锁吗
原文：http://blog.itpub.net/12798004/viewspace-1744513/
