Error
WARNING: File being created with same name as in Primary
Existing file may be overwritten
Errors in file /ccbs/appl/oracle/orabase/diag/rdbms/prodtabs/TABS1/trace/TABS1_pr00_4213.trc:
ORA-01119: error in creating database file '+DATA_DG1/tabsdr/u14/prodtabs/tabsxl01_f09.dbf'
ORA-17502: ksfdcre:4 Failed to create file +DATA_DG1/tabsdr/u14/prodtabs/tabsxl01_f09.dbf
ORA-15001: diskgroup "DATA_DG1" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
File #308 added to control file as 'UNNAMED00308'.
Originally created as:
'+DATA_DG1/tabsdr/u14/prodtabs/tabsxl01_f09.dbf'
Recovery was unable to create the file as:
'+DATA_DG1/tabsdr/u14/prodtabs/tabsxl01_f09.dbf'
MRP0: Background Media Recovery terminated with error 1274
Errors in file /ccbs/appl/oracle/orabase/diag/rdbms/prodtabs/TABS1/trace/TABS1_pr00_4213.trc:
ORA-01274: cannot add datafile '+DATA_DG1/tabsdr/u14/prodtabs/tabsxl01_f09.dbf' - file could not be created
Tue Jun 12 11:03:40 2018
Managed Standby Recovery not using Real Time Apply
Recovery interrupted!
Recovery stopped due to failure in applying recovery marker (opcode 17.30).
Cause
Our DR was prepared from filesystem to ASM, after switchover standby_file_management was set to 'AUTO' but DB_FILE_NAME_CONVERT wasn't (missed).
So, when we added datafile in new primary database as '+DATA_DG1/tabsdr/u14/prodtabs/tabsxl01_f09.dbf' it tries to create this file on Standby using the same path as of primary database, as this path is not exist it got failed.
Solution
Frist of all there are many ways to fix, what i followed is as below.
1. Stop recovery
recover managed standby database cancel;
2. Shutdown database
3. Update pfile with all subsequent location of datafiles in DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT
4. Create spfile from pfile
5. Start database in standby mode.
6. Start recovery
Alter database recover managed standby database using current logfile disconnect;
By the time i checked the system and applied all these changes huge archive gap generated and archive logs were deleted from production server too.
Now i have to sync DR from incremental bacukp from the SCN from which logs were missing.
To avoid this i used another way.
7. Restore archive logs of primary datatabase directly to standby database server.
8. No need to register archive logs with database, database will read from the location where i'm doing restore.
WARNING: File being created with same name as in Primary
Existing file may be overwritten
Errors in file /ccbs/appl/oracle/orabase/diag/rdbms/prodtabs/TABS1/trace/TABS1_pr00_4213.trc:
ORA-01119: error in creating database file '+DATA_DG1/tabsdr/u14/prodtabs/tabsxl01_f09.dbf'
ORA-17502: ksfdcre:4 Failed to create file +DATA_DG1/tabsdr/u14/prodtabs/tabsxl01_f09.dbf
ORA-15001: diskgroup "DATA_DG1" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
File #308 added to control file as 'UNNAMED00308'.
Originally created as:
'+DATA_DG1/tabsdr/u14/prodtabs/tabsxl01_f09.dbf'
Recovery was unable to create the file as:
'+DATA_DG1/tabsdr/u14/prodtabs/tabsxl01_f09.dbf'
MRP0: Background Media Recovery terminated with error 1274
Errors in file /ccbs/appl/oracle/orabase/diag/rdbms/prodtabs/TABS1/trace/TABS1_pr00_4213.trc:
ORA-01274: cannot add datafile '+DATA_DG1/tabsdr/u14/prodtabs/tabsxl01_f09.dbf' - file could not be created
Tue Jun 12 11:03:40 2018
Managed Standby Recovery not using Real Time Apply
Recovery interrupted!
Recovery stopped due to failure in applying recovery marker (opcode 17.30).
Cause
Our DR was prepared from filesystem to ASM, after switchover standby_file_management was set to 'AUTO' but DB_FILE_NAME_CONVERT wasn't (missed).
So, when we added datafile in new primary database as '+DATA_DG1/tabsdr/u14/prodtabs/tabsxl01_f09.dbf' it tries to create this file on Standby using the same path as of primary database, as this path is not exist it got failed.
Solution
Frist of all there are many ways to fix, what i followed is as below.
1. Stop recovery
recover managed standby database cancel;
2. Shutdown database
3. Update pfile with all subsequent location of datafiles in DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT
4. Create spfile from pfile
5. Start database in standby mode.
6. Start recovery
Alter database recover managed standby database using current logfile disconnect;
By the time i checked the system and applied all these changes huge archive gap generated and archive logs were deleted from production server too.
Now i have to sync DR from incremental bacukp from the SCN from which logs were missing.
To avoid this i used another way.
7. Restore archive logs of primary datatabase directly to standby database server.
8. No need to register archive logs with database, database will read from the location where i'm doing restore.