Oracle Database / Multitenant, Patching & Deployment
ORA-65040: identify an operation that requires a different container context
Some administrative operations cannot run inside a PDB. Verify the operation's documented scope instead of switching containers blindly.
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_NAME') AS con_name, SYS_CONTEXT('USERENV','SESSION_USER') AS session_user FROM dual;Read the result
The session context identifies where the failing command was attempted and by whom. It does not establish that running it in root is appropriate.
Resolve and verify
Check the command's multitenant restrictions and intended effect. Have an authorized DBA execute the approved operation in its supported scope.
Operational precautions
Root-scoped commands can affect multiple PDBs. Do not move a maintenance script to root without reviewing every statement.