Oracle Database / Multitenant, Patching & Deployment
Include container identity in every Oracle support capture
The same schema or object name can exist in several PDBs. A diagnostic collected in the wrong container can lead to an incorrect grant or schema change.
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 SYS_CONTEXT('USERENV','CON_ID') AS con_id, SYS_CONTEXT('USERENV','CON_NAME') AS con_name, SYS_CONTEXT('USERENV','SERVICE_NAME') AS service_name FROM dual;Read the result
These values identify the current session's container and service. Another connection may use a different target despite the same username.
Resolve and verify
Attach the sanitized container identity to the ticket and rerun relevant read-only checks through the intended service. Correct misrouting before changing data or privileges.
Operational precautions
Do not assume CDB root metadata represents every PDB's local objects and grants.