While configuring DBVisit standby disaster recovery software at one of my client end environment, when DBVisit standby configuration initiated it was smooth during backup of primary database, than transferred backup to DR server. When RMAN backup arrived at DR server and started creating standby database ( restore activity by RMAN ) DBVisit popped up with following error messages:
Error message 1:
ORA-19504: failed to create file "/RTS/prod/df/RTSapp_lob.dbf" ORA-27040: file create error, unable to create file Linux-x86_64 Error: 2: No such file or directory
Error message 2:
RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of restore command at 06/18/2015 16:06:05 RMAN-06026: some targets not found - aborting restore RMAN-06023: no backup or copy of datafile 7 found to restore
After giving hard diagnosis on above red highlighted error messages, It is came to know that it was the problem with /RTS/prod/df/ path.
On primary server there was multiple datafiles locations on multiple storage LUN’s for various tablespaces. DBVisit simply copied references from primary database server and searching exact path on secondary database server. But obviously same path would not available on secondary database server. Plus While taking RMAN backup at primary database server, RMAN recorded all path and locations while backup and try to search same path and location at secondary database server while restore activity. Which is again impossible. Due to above reasons DBVisit finally came out of configuration activity with above mentioned errors.
As a part of solution I would have two choices available in my hand, one is to discard all secondary server configuration and start from scratch (OS, oracle DB & DBVist installation) to meed exactly same path and partition scheme of primary database linux server.
Second is to create links between two directories.
So finally I have created directory link between /RTS/prod/df/ to the new datafile location of standby database server: /home/app/datafile/ifsprod/
lrwxrwxrwx. 1 oracle oinstall 27 Jun 18 18:21 df -> /u01/app/datafile/RTSprod/
After applying above fix, Resumes DBVisit configuration and it was successfully configured.
For more details on above DBVisit error, Please have a look here.
Dbvisit Standby Database Technology message from PR Message received from process: dbvisit_setup --csd --web --ddc prod (Dbvisit Standby: 220.127.116.1173 Process id: 6691) 201506181606 - Error executing RMAN command: Recovery Manager: Release 18.104.22.168.0 - Production on Thu Jun 18 16:06:02 2015 Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved. RMAN> connected to target database: prod (DBID=4119037639, not open) using target database control file instead of recovery catalog RMAN> RMAN configuration parameters for database with db_unique_name prod are: CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 10 DAYS; CONFIGURE BACKUP OPTIMIZATION ON; CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE MAXSETSIZE TO UNLIMITED; # default CONFIGURE ENCRYPTION FOR DATABASE OFF; # default CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO DISK; CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/ORACLE/app/oracle/product/11.2.0/db_1/dbs/snapcf_prod.f'; echo set off RMAN> allocated channel: C_DBVISIT channel C_DBVISIT: SID=202 device type=DISK executing command: SET NEWNAME Starting restore at 2015-06-18:16:06:04 channel C_DBVISIT: starting datafile backup set restore channel C_DBVISIT: specifying datafile(s) to restore from backup set channel C_DBVISIT: restoring datafile 00007 to /RTS/prod/df/RTSapp_lob.dbf channel C_DBVISIT: reading from backup piece /MISC/temp_dbvisit/dbv_prod_csd_dbf_7_9vq9pgmr_1_1.rman channel C_DBVISIT: ORA-19870: error while restoring backup piece /home/temp_dbvisit/dbv_prod_csd_dbf_7_9vq9pgmr_1_1.rman ORA-19504: failed to create file "/RTS/prod/df/RTSapp_lob.dbf" ORA-27040: file create error, unable to create file Linux-x86_64 Error: 2: No such file or directory failover to previous backup released channel: C_DBVISIT RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of restore command at 06/18/2015 16:06:05 RMAN-06026: some targets not found - aborting restore RMAN-06023: no backup or copy of datafile 7 found to restore RMAN> Recovery Manager complete. Dbvisit Standby terminated. Return code = 8002 (Tracefile required if contacting Dbvisit Standby support: /usr/local/dbvisit/standby/trace/5828_dbv_functions_prod_201506181606.trc (server:DR)) Dbvisit Standby terminated. Return code = 66 (Tracefile required if contacting Dbvisit Standby support: /usr/local/dbvisit/standby/trace/6691_dbvisit_setup_csd_prod_201506181008.trc (server:PR))
Stay tune. 🙂