In this post, we’ll be looking at how to troubleshoot error ORA-65101: Container database set up incorrectly while restoring standby control file using RMAN from On-Premise to Oracle Cloud to configure hybrid data guard.
Note: To read about what is hybrid data guard and hybrid data guard deployment process key points click here
First to give you some context, With the launch of database 12c in 2013, Oracle introduced a new architectural concept, called “Multitenant Databases”, where you have one super database (=container; CDB) and one or more sub-databases (= pluggable; PDB). When you migrate the databases from On-Prem to Oracle Cloud using the DB version like 12c or higher, you can have a Multi-Tenant Architecture (CDB/PDB), or you can have a non-container (non-pluggable) database.
Note: In database 20c the multi-tenant architecture is mandatory.
Note: To read more about Multi-Tenant Architecture click here
The majority of databases that are running On-Premise are still non- container databases. The database I was using to migrate via hybrid data guard was also a non-container database.
Architecture On Cloud
When you create database 12c or higher on Cloud you get multi-tenant architecture (CDB/PDB) by default where you have a container database and inside it, you get a pluggable database and you can add more pluggable database as well.
Note: We cover all this including how to add additional pluggable database in my DBA to Cloud Training…to know more about training program join our FREE masterclass click here
We encountered the error ORA-65101: container database set up incorrectly while configuring the standby database on Oracle Cloud (OCI) using RMAN when we tried to restore the standby control file.
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-03002: failure of sql statement command at 12/30/2019 06:50:38
ORA-65101: container database set up incorrectly
Primary database on On-premise is non-container database where as all databases on Oracle cloud (OCI) are pluggable database inside container databases. Therefore, while restoring the standby file it was expecting a non container(non pluggable) database whereas it was set up as pluggable database.
Note: Read more about 12c Multitenant architecture and Container Database(CDB)/Pluggable Database(PDB).
———————————— ———– ——————————
enable_pluggable_database boolean FALSE
- 2270420.1 ORA-65101 Wrong option for CDB parameter in a Template which created by DBCA with silent mode
- 2472112.1 OCI-C DBCS: Launching new DB Service Instance using instantiate from backup failed with ORA-65101/ORA-1507
- Know more about Zero Downtime Migration To Oracle Cloud Using Hybrid Data Guard
- Read about Overview: Oracle Data Guard Broker
- Restore of Standby Control File On Standby DB In ExaCS failing With ERROR (ORA-600, RMAN-03002)
Next Task For You
Join our FREE training on Migrate E-Business Suite database and application to Cloud using hybrid data guard, in this training, we cover Migration Overview & Options, Migration Tools: ZDM, MV2ADB, RMAN, Migration Solution: 4 Phase using Hybrid DR, Customer Case Study: Migration Requirement, Live Q/A Session & Much More.