Oracle Database / Multitenant, Patching & Deployment
ORA-65011: verify the PDB name in the current CDB
A PDB name can be correct in another CDB but absent from the current target. Check database identity and visible PDB names.
Environment and inputs: Oracle Database 19c baseline · SQL*Plus-compatible SQL unless RMAN, DGMGRL, ADRCI or a host shell is specified. Check release, patch level, edition and container first.
Start with this diagnostic
Use the stated SQL, RMAN, DGMGRL or host shell and replace sample names with approved targets. DBA and V$ views need authorized catalog access in the correct container. Do not grant broad privileges for an example.
SELECT name, db_unique_name FROM v$database;
SELECT con_id, name, open_mode FROM v$pdbs;Read the result
The pair distinguishes a misspelled PDB from a connection to the wrong CDB. Visibility also depends on session context and privileges.
Resolve and verify
Compare the deployment inventory and exact PDB name, then route the operation to the intended CDB through the approved admin path.
Operational precautions
Do not create a replacement PDB merely because a script used the wrong target.