Beginning with Oracle 18.104.22.168, for any form of database control file backup operations, Oracle no longer acquires the controlfile enqueue lock.
This change requires snapshot control file accessibility to all instances in a RAC database, in contrast to a single-instance database, to successfully complete a manual or auto control file backup operation.
When the snapshot control file is not accessible or does not exist across instances, the backup of control file operations, including RMAN backups, will fail with an
ORA-00245: control file backup operation failed
To prevent an ORA-00245 error, the snapshot control file must be placed on a shared location
or on ASM DISKGROUP, ensuring that each instance of RAC database has the read and write ability on the file.
The following procedure explains the process to configure the snapshot control file on an ASM DISK GROUP:
RMAN> CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+DG_RONDB/snapcf_RONDB.f';
Upon configuration, the following message will be displayed at RMAN prompt:
using target database control file instead of recovery catalog new RMAN configuration parameters:
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+DG_RONDB\snapcf_RONDB.f;
new RMAN configuration parameters are successfully stored
To display snapshot control file configuration details, connect to an RMAN prompt and execute one of the following commands: