My Oracle Support Banner

Opening a Plugged-in PDB Fails with ORA-65011 at Standby with Active Data Guard (Doc ID 2639559.1)

Last updated on MARCH 16, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 18.4.0.0.0 and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

Opening a newly plugged-in PDB in a standby database running active dataguard can return ORA-65011 despite the fact that it was plugged in and opened in the primary with no errors. The ‘show pdbs’ command in the standby will list the new PDB, but will not allow it to open. This occurs despite TDE tablespaces, RAC (Real Application Cluster) and/or ASM (Automatic Storage Management).

For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:

Database Name: ORCL2, ORCLA2

Pluggable Database Names: PDB1, PLUGIN_PDB

Disk Group Name: +DATA

 

Performed a PDB plugin at Primary site without placing datafiles in appropriate ways at Standby site.

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.