RMAN> show snapshot controlfile name; starting full resync of recovery catalog full resync complete RMAN configuration parameters for database with db_unique_name ORCLare: CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0.4/dbhome_1/dbs/snapcf_ORCL2.f'; # default
Here you can see that controlfile is on a local file system, so to fix this issue configure it to a shared location.
To Configure the snapshot controlfile to a shared disk
Connect to target database, and issue the following command on RMAN prompt.
rman target / RMAN> CONFIGURE SNAPSHOT CONTROLFILE NAME TO '<shared_disk>/snapcf_<DBNAME>.f';
Let us take an example,
RMAN> CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+RC_DATA/ORCL/snapcf_orcl.f'; new RMAN configuration parameters: CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+RC_DATA/ORCL/snapcf_orcl.f'; new RMAN configuration parameters are successfully stored starting full resync of recovery catalog full resync complete
Due to the changes made to the controlfile backup mechanism any instances in the cluster may write to the backup controlfile when making changes to the current controlfile. Therefore, the backup file needs to be visible to all instances.
Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Skant Gupta’s LinkedIn: www.linkedin.com/in/skantali/
Joel Perez’s LinkedIn: www.linkedin.com/in/SirDBaaSJoelPerez
Anuradha’s LinkedIn: https://www.linkedin.com/in/dbaanuradhamudgal/
LinkedIn Group: Oracle Cloud DBAAS
Facebook Page: OracleHelp
