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 184.108.40.206 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.
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
Migrated the database across different platform
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