Oracle Database / Accounts, Security & Access
Inspect direct object grants for a stored program's owner
A package can become invalid after a required object privilege is removed, even when the developer can query through a role.
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 owner, table_name, grantee, privilege, grantable FROM dba_tab_privs WHERE grantee = 'APP_OWNER' AND owner = 'DATA_OWNER';Read the result
The rows show direct object grants matching these principals. They do not include every privilege path or determine whether the package should access the object.
Resolve and verify
Compare the failing compiler line with the intended dependency and rights model. Restore the smallest approved direct grant and recompile the affected object.
Operational precautions
Do not grant access to PUBLIC or add broad schema privileges simply to make compilation succeed.