RMAN duplicate of multitenant database reports RMAN-06064 for pdb$seed datafiles
(Doc ID 2589368.1)
Last updated on MAY 31, 2020
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.1 and laterInformation in this document applies to any platform.
Symptoms
Regular backups of the target database were taken using the below incremental level 0 and incremental level 1 backups scripts:
run {
#allocate channel ch1 device type disk;
backup format '${RMAN_BACKUP_LOC}/%d_%U' device type disk incremental level 0 as compressed backupset database filesperset=1 plus archivelog ;
delete archivelog all completed before 'sysdate-1' device type disk backed up 1 times to device type disk;
delete noprompt obsolete;
}
run {
backup format '${RMAN_BACKUP_LOC}/%d_%U' device type disk incremental level 1 as compressed backupset database filesperset=1 plus archivelog ;
delete archivelog all completed before 'sysdate-1' device type disk backed up 1 times to device type disk;
}
When a duplicate was tried using the below command it failed with the error "RMAN-06053: unable to perform media recovery because of missing log"
{
allocate auxiliary channel dupe1 type disk;
allocate auxiliary channel dupe2 type disk;
duplicate target database to SDTEST pluggable database lcdt1, root until time "to_date('30-AUG-2019 19:16:10','DD-MON-YYYY HH24:MI:SS')";
}
Changes
No changes were done in backup schedule or the backup and duplicate scripts.
All the backups taken using the above mentioned scripts were present at the desire location.
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 |
Changes |
Cause |
Solution |
References |