Duplicate PDB Using Backup Location option Without connection to Target Fails RMAN-05556 RMAN-03015 RMAN-06023
(Doc ID 2802549.1)
Last updated on APRIL 17, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 12.2.0.1 and laterInformation in this document applies to any platform.
Symptoms
Rman duplicate of pdb using Backup location Option on Clone server Fails with
RMAN-05556: not all datafiles have backups that can be recovered to SCN xxxxxx
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile xx found to restore
RMAN-06023: no backup or copy of datafile xx found to restore
RMAN-06023: no backup or copy of datafile xx found to restore
RMAN-06023: no backup or copy of datafile xx found to restore
RMAN-06023: no backup or copy of datafile xx found to restore
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile xx found to restore
RMAN-06023: no backup or copy of datafile xx found to restore
RMAN-06023: no backup or copy of datafile xx found to restore
RMAN-06023: no backup or copy of datafile xx found to restore
RMAN-06023: no backup or copy of datafile xx found to restore
Syntax used for backup on Source
Backup on Source database was taken using
Command 1 :-
backup database plus archivelog format '<NFS mount point which is accessible by clone server>/%U';
On Clone databsae below command is used
rman auxiliary /
duplicate database to <name> pluggable database <pdb name> backup location '<nfs mount point used by the backup command 1>';
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 |