My Oracle Support Banner

REGISTRY$DATABASE IS NEVER UPDATED AFTER RMAN CONVERT (Doc ID 2242818.1)

Last updated on MARCH 14, 2019

Applies to:

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

Symptoms

After Cross-Platform Database Migration (across same endian) using RMAN Transportable Database, the table REGISTRY$DATABASE is never updated to reflect the new platform.

The steps used were taken from Note 1401921.1 - Cross-Platform Database Migration (across same endian) using RMAN Transportable Database

The view V$DATABASE is updated once the controlfile is recreated, but there is no process in place to update REGISTRY$DATABASE

Example :

 

Changes

 Migrated the database across different platform

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


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