rman會造成delete死鎖嗎

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吧。應該看得出來。