Tuesday, 10 January 2017

ORA-00245: control file backup failed; target is likely on a local file system



While performing RMAN operations you will hit below errors

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of allocate command at 01/10/2017 12:28:40
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of full resync command on default channel at 01/10/2017 12:28:40
ORA-00245: control file backup failed; target is likely on a local file system


Cause:-


This is down to the snapshot control file being on a local disk and it needs to be on a shared disk for all of the cluster in our case we need to put it on our +DATA ASM disk group


RMAN> show snapshot controlfile name;

Using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name DEV are:
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u00/app/oracle/product/11.2.0.3/DB/dbs/snapcf_DEV.f'; # default

Above Location is Local File system location. WE need to set

FIX:-

So to fix the issue we need to configure the SNAPSHOT CONTROLFILE to the +DATA ASM disk group in RMAN, this is done as follows:

RMAN>  CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+ DATA/DEV/snapcf_DEV.f';

new RMAN configuration parameters:
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+ DATA/DEV/snapcf_DEV.f';
new RMAN configuration parameters are successfully stored

RMAN> show snapshot controlfile name;

RMAN configuration parameters for database with db_unique_name DEV are:
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+ DATA/dev/snapcf_DEV1.f';

No comments:

Post a Comment