alert 告警提示信息
ORA-48132: requested file lock is busy, [HM_FINDING] [/db1/XXXXX/oraadmin/diag/rdbms/XXXXXX/XXXXX/lck/ ]
ORA-48170: unable to lock file - already in use
Linux-x86_64 Error: 11: Resource temporarily unavailable
处理方法
MMON Process Fails with Errors ORA-48132 and ORA-48170 (Doc ID 2265173.1)
Caused by OS level locks on the files being accessed by Oracle.
1. To release the OS level locks on the files being accessed by Oracle, please restart the database
2. If restarting the database does not work, then restart the server so that all OS level locks will be cleared
根据以上方法处理完成之后，两三天后客户反馈出现同样的问题，接下来查看具体的trc文件信息如下：
继续MOS查找方法
RMAN L0 And L1 Backup taking long time with "ADR file lock" wait event (Doc ID 2565120.1)
Oracle Database - Enterprise Edition - Version 11.2.0.4 and later
Information 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
RMAN backup was taking time due to ADR file lock wait event.
Similar issue was reported in Below bug but closed as not a Bug
Bug 10125939 - GSFBDRA: RMAN VALIDATE HANG WAITING FOR 'ADR FILE LOCK' Closed as could not reproduce
Currently we have the following workaround for the issue
RMAN does not write findings to ADR if we set this event.
Setting below event disables updates to the online dictionary .
On every instance of RAC database we need to set event then only it will work :
Krb tracing needs to enabled on all nodes.
alter system set event='logon trace name krb_options level 20' scope=spfile; <==== To set it.
alter system set event='logon trace name krb_options off' scope=spfile; <==== To set it off
最后处理方法：
在RMAN备份的会话级别设置，暂时不在系统级别设置 ，后续继续跟进。
