Rman Backups Failing with RMAN-20004
(Doc ID 1254144.1)
Last updated on APRIL 01, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 8.1.7.0 to 11.2.0.2 [Release 8.1.7 to 11.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
- Database is in 10g.
- Recovery catalog has been configured.
- Production Database has been cloned and a connection has been made from the clone to Catalog database using rman.
- DBID of the clone instance has not been changed, (so is identical with source DBID).
Rman backup fails with
Changes
Production Database has been cloned and a connection has been made from the clone to Catalog database using rman.
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 |