RMAN restore to ASM - ORA-17503: ksfdopn:2 Failed to open file
(Doc ID 336200.1)
Last updated on JULY 07, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 10.1.0.2 and laterOracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
You are using Oracle Database 10g and are restoring backups taken using RMAN. The backup was taken on HOST A and you are restoring the database to HOST B. The parameter DB_CREATE_FILE_DEST is set to a new location. Almost all of the files restore without error but there are some files that show failure and their restore job will failover and spawn a new process to execute the failed RPC. The restore fails with the error:
Errors in file /<database_diag_location>/dm2gp1_dbw0_26350.trc:
ORA-01157: cannot identify/lock data file 51 - see DBWR trace file
ORA-01110: data file 51: '+<DISKGRP>/<db_unique_name>/datafile/data_part02_1'
ORA-17503: ksfdopn:2 Failed to open file '+<DISKGRP>/<db_unique_name>/datafile/data_part02_1
ORA-15173: entry '<db_unique_name>' does not exist in directory '/'
Note that the datafile name is not an OMF name. If it were an OMF name a different error is raised:
Errors in file /<database_diag_location>/dm2gp1_dbw0_26350.trc:
ORA-01157: cannot identify/lock data file 45 - see DBWR trace file
ORA-01110: data file 45: '+<DISKGRP>/<db_unique_name>/datafile/undotbs02.281.562308511'
ORA-17503: ksfdopn:2 Failed to open file '+<DISKGRP>/<db_unique_name>/datafile/undotbs02.281.562308511
ORA-15012: ASM file '+<filename>' does not exist
But the restore succeeds because the file is an OMF file.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |