I got ” ORA-19505: failed to identify file “string” ” error in Oracle database.
ORA-19505: failed to identify file “string”
Details of error are as follows.
ORA-19505: failed to identify file "string" Cause: call to identify the file returned an error Action: check additional messages, and check if the file exists
During a RMAN DUPLICATE, the following errors occurs: ORA-19505: failed to identify file "/<path>/flash_recovery_area/<SID>/backupset/2007_07_16/o1_mf_nnndf_FULL_DB_BKUP_39qkz853_.bkp" ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: ORA-19870: error reading backup piece /<path>/flash_recovery_area/<SID>/backupset/2007_07_16/o1_mf_nnndf_FULL_DB_BKUP_39qkz867_.bkp ORA-19505: failed to identify file "/<path>/flash_recovery_area/<SID>/backupset/2007_07_16/o1_mf_nnndf_FULL_DB_BKUP_39qkz867_.bkp" ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: failover to previous backup
failed to identify file “string“
This ORA-19505 error is related to the call to identify the file returned an error.
To solve this error, check additional messages, and check if the file exists.
Run the crosscheck, then delete the expired archivelog as follows.
RMAN> crosscheck archivelog all; RMAN> delete expired archivelog all;
If you got this error during a RMAN DUPLICATE, A backup was taken on the target and moved to the auxiliary server in a different location. The auxiliary instance is a separate standalone box with a different file structure. RMAN duplicate is attempting to access the backup from the location from which it was taken. I.e., from the target server location.
The error is occurring because the auxiliary server cannot access the backup files on the destination server.
The following must work on the Auxiliary instance:
$ ls /<path>/flash_recovery_area/<SID>/backupset/2020_07_16/
As long as RMAN is able to connect to the primary and duplicate instances, the RMAN client can run on any machine. However, all backups, copies of datafiles, and archived logs used for creating and recovering the duplicate database must be accessible by the auxiliary instance on the auxiliary host.
If the duplicate host is different from the target host, then you must make backups and copies on the primary/target host available to the remote node with the same full path name as the primary/target database. You can accomplish this goal in two ways:
1) Using an operating system utility to move the backup pieces, image copies,
and archived logs from the primary host to the remote host to an identical path
2) Using NFS or shared disks and making sure that the same path is accessible in the remote host
196 views last month, 3 views today