Upgrade Of Database From 22.214.171.124 To 126.96.36.199 Caused RMAN Duplication To Error On Spfile
(Doc ID 1951266.1)
Last updated on MARCH 14, 2019
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Source and Target Oracle Databases were upgraded from 184.108.40.206 to 220.127.116.11.
Duplication is accomplished with no connection to target using BACKUP LOCATION Or using Normal rman duplicate process.
The duplication worked fine in 18.104.22.168 before the upgrade.
Now the spfile is missing after the duplication, even though it exists before the duplication starts.
In the alert.log, the following error reported:
ORA-01565: Unable to open Spfile /<$ORACLE_HOME>/dbs/spfile$ORACLE_SID.ora
The script has been running successfully for over 1 year.
Auxiliary instance was started using pfile.
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