RMAN DUPLICATE: Errors in Krbm_getDupCopy Found in the Alert.log
(Doc ID 1476641.1)
Last updated on JULY 15, 2020
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 to 12cBETA2 [Release 11.2 to 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 02-JUL-2015***
Executing active duplicate for standby:
duplicate target database for standby from active database ...
In the alert.log appear messages like this:
This happens after a previous failed duplicate trial, if the files copied to auxiliary destination have been deleted.
Before 11.2 when active duplicate is used although a previous (failed) duplicate had already copied the datafiles to the new database the second execution of the duplicate will not be able to use 'restore optimization' and will copy again the previously copied datafiles.
Similar problem happens for a backup based duplicate in which the new datafile names are OMF, as there is no record of the OMF names generated by the previous command, so
restore optimization is not possible and new datafiles will be restored.
Only when a backup based duplicate uses non-OMF names restore optimization is possible for a second duplicate after a failed duplicate.
This has changed, from 11.2 RMAN always checks if the file copy exists at destination hosts to avoid copying it again.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!