ORA-245: In RAC environment from 11.2 onwards Backup Or Snapshot controlfile needs to be in shared l
In this Document
APPLIES TO:Oracle Database - Enterprise Edition - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
This issue is only applicable to RAC database.
From 11gR2 onwards, the controlfile backup happens without holding the controlfile enqueue. For non-RAC database, this doesn't change anything. But for RAC database, due to the changes made to the controlfile backup mechanism in 11gR2, any instance in the cluster may write to the snapshot controlfile. Due to this snapshot controlfile need to be visible to all instances.
The snapshot controlfile MUST be accessible by all nodes of a RAC database, if the snapshot controlfile does not reside on a shared device error will be raised at the time of RMAN backup while taking snapshot of controlfile.
This applies to backing up controlfile using sqlplus / having autobackup of controlfile configured on non
ORA-245 error message description
00245, 00000, "control file backup operation failed"
*Cause: Failed to create a control file backup because some process
signaled an error during backup creation.
*Action: Check alert files for further information. This usually happens
because some process could not access the backup file during
backup creation. Any process of any instance that starts a
read/write control file transaction must have an access to the
backup control file during backup creation.
Only affect Real application Cluster (RAC ), 11.2 specific.
In RAC environment any form of controlfile backup may fail with ORA-0245 if the location of the Snapshot Controlfile is not a shared location.
The backup of the controlfile actualy makes a backup of the SNAPSHOT controlfile. The Snapshot controlfile is created when the controlfile is about to be backed up.
The Snapshot controlfile is a read-consistent copy of the controlfile.
This is a RAC specific 'configuration' issue and the correct configuration is as described below
It is changed behaviour which requires that the snapshot controlfile in a RAC environment, is on a shared location.
1. Check the snapshot controlfile location:
2. Configure the snapshot controlfile to a shared disk:
Or in case of ASM use
02-07-2012 created and Published alert
BUG:12311429 - ALTER DATABASE BACKUP CONTROLFILE FAILS WITH ORA-245
BUG:13085539 - ORA-245 OCCURS DURING RMAN COPY CORRENT CONTROLFILE.
BUG:13780443 - CONTROLFILE BACKUP MUST RESIDE ON SHARED DEVICE WITH RAC DATABASE
NOTE:265623.1 - RESYNC CATALOG fails with ORA-15045
BUG:10263733 - SNAPSHOT CONTROLFILE USED BY RMAN MUST RESIDE ON SHARED DEVICE FOR RAC DATABASE
BUG:10252378 - CONTROLFILE AUTOBACKUP FAILS WITH ORA-00245: CONTROL FILE BACKUP OPERATION FAILE