Oracle Database / Accounts, Security & Access
Explain why CURRENT_SCHEMA does not grant access
Changing the default schema affects name resolution but does not make a session the schema owner. Verify the relevant identities before changing permissions.
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','SESSION_USER') AS session_user, SYS_CONTEXT('USERENV','CURRENT_USER') AS current_user, SYS_CONTEXT('USERENV','CURRENT_SCHEMA') AS current_schema FROM dual;Read the result
The values can differ, especially in stored-code execution. CURRENT_SCHEMA affects unqualified object names and is not a replacement for authorization.
Resolve and verify
Check the intended rights model and actual object grants for the executing principal. Correct target naming or narrow privileges as appropriate.
Operational precautions
Do not treat ALTER SESSION SET CURRENT_SCHEMA as an impersonation or privilege-escalation mechanism.