REMOTE_RECOVERY_FILE_DEST Does Not Work When Performing PDB Refresh
(Doc ID 2408829.1)
Last updated on SEPTEMBER 06, 2021
Applies to:
Oracle Database - Enterprise Edition - Version 12.2.0.1 to 12.2.0.1 [Release 12.2]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
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
When perform pdb refresh, do below
1. Configure REMOTE_RECOVERY_FILE_DEST in target DB, copy archive log from source to REMOTE_RECOVERY_FILE_DEST
2. Modify dblink to simulate a failure in source
3. Refresh target, it does not read archive log from REMOTE_RECOVERY_FILE_DEST, but returns
Changes
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 |