[Solved] Container Database Set Up Incorrectly With Error ORA-65101 For Hybrid DR

Note: To read about what is hybrid data guard and hybrid data guard deployment process key points click here

Background

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

Problem Statement

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.

Error 

Root Cause

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.

Fix