My Oracle Support Banner

RMAN-6216 on Crosscheck after Switchover (Doc ID 1308712.1)

Last updated on FEBRUARY 13, 2019

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 11.1 to 11.2]
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.


From 11g onwards RMAN catalog includes DB_UNIQUE_NAME along with the DB_NAME to store the backup metadata.

RMAN backups are running on primary with catalog database.
After switchover:
 If we connect to new primary and catalog database,
 Then the crosscheck will fail with RMAN-6216 on files associated with the other DB_UNIQUE_NAME:

RMAN-6216: WARNING: db_unique_name mismatch - 1 objects could not be updated
RMAN-6218: List of objects requiring same operation on database with db_unique_name chicago
RMAN-6211: ==========================
RMAN-6212: Object Type Filename/Handle
RMAN-6213: ---------------




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.