My Oracle Support Banner

Known Issue related to Using RMAN Active Duplicate With Standby as Source (Doc ID 2420613.1)

Last updated on MARCH 06, 2019

Applies to:

Oracle Database Exadata Express Cloud Service - Version N/A and later
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 Backup Service - Version N/A and later
Information in this document applies to any platform.


Database refresh /Duplicate is done  using RMAN active duplication with  Physical Standby as Source .

There are Multiple bug due to which this issue might be reported.

Below are the symptoms reported by Each bug . The Cause session contains information about each bug associated with this symptom.

It would be advisable to apply the Merge fix if available for these bug fix

Following errors Might be reported


Restrictions :- With Standby database being used as Source database for Active duplicate from we have the restriction introduced with respect to the Standby database needing to be in Open state for the active duplicate to work successfully while using  Standby as Source. (For Non ADG envirnoment you can just open standby read only ).

This is documented in Unpublished Bug  Bug 27442063 - RMAN-6054/RMAN-3009 ON RMAN DUPLICATE FROM STANDBY







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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.