RMAN L0 And L1 Backup taking long time with "ADR file lock" wait event
(Doc ID 2565120.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.4 and laterInformation in this document applies to any platform.
Goal
Rman Level 0 takes long time and does not complete.
Even L1 Backups end up in the same state
At the time when the rman backup seems to hang following error is reported in the database alert log.
Incremental checkpoint up to RBA [0x9c6e.11752.0], current log tail at RBA [0x9c6e.124dc.0]
Sun Jun 09 02:42:39 2019
Errors in file <path>/<SID>/trace/<SID>_ora_10225.trc:
ORA-48132: requested file lock is busy, [HM_RUN] [<path>/lck/AM_1618_3044626670.lck]
ORA-48170: unable to lock file - already in use
SVR4 Error: 11: Resource temporarily unavailable
Additional information: 8
Additional information: 10759
Sun Jun 09 02:56:30 2019
Incremental checkpoint up to RBA [0x9c6e.148ff.0], current log tail at RBA [0x9c6e.15967.0]
INST_ID SID CH SEQ# EVENT STATE SECONDS
---------- ---------- -------------------- ---------- ---------------------------------------- ------------------- ----------
2 4052 rman channel=ch06 20780 ADR file lock WAITING .43 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
...
2 1649 rman channel=ch12 14041 ADR file lock WAITING 2.30
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
References |