RMAN

How to Resolve ORA-19505 and ORA-27037 in Error Stack

ORA-19505 with ORA-27037

When I tried to duplicate a target database to an auxiliary one by this run block.

RUN {
  ALLOCATE AUXILIARY CHANNEL c1 DEVICE TYPE DISK;
  ALLOCATE AUXILIARY CHANNEL c2 DEVICE TYPE DISK;
  ALLOCATE AUXILIARY CHANNEL c3 DEVICE TYPE DISK;
  ALLOCATE AUXILIARY CHANNEL c4 DEVICE TYPE DISK;
  DUPLICATE TARGET DATABASE
  FOR STANDBY
  DORECOVER
  NOFILENAMECHECK;
}

As you can see, this run block indicated that the duplication should use a most recent backup set to accomplish this with disk channels . But I got the errors:

...
channel c1: reading from backup piece /u01/app/oracle/recovery_area/DB11204/backupset/2017_03_01/o1_mf_ncsnf_TAG20170301T232055_dcfsrj3d_.bkp
channel c1: ORA-19870: error while restoring backup piece /u01/app/oracle/recovery_area/DB11204/backupset/2017_03_01/o1_mf_ncsnf_TAG20170301T232055_dcfsrj3d_.bkp
ORA-19505: failed to identify file "/u01/app/oracle/recovery_area/DB11204/backupset/2017_03_01/o1_mf_ncsnf_TAG20170301T232055_dcfsrj3d_.bkp"
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3

This is because the auxiliary database can’t SEE the backup files from its standing. So I copied the backup files to the same location of the auxiliary database and make it able to SEE the backup files. That’s how we solve ORA-19505.

2 thoughts on “How to Resolve ORA-19505 and ORA-27037 in Error Stack

Leave a Reply

Your email address will not be published. Required fields are marked *