AFTER LOGON Triggers Don't Allow DBMS_SESSION.SET_ROLE to Keep Roles Enabled
(Doc ID 106140.1)
Last updated on AUGUST 15, 2023
Applies to:
Oracle Database Exadata Express Cloud Service - Version N/A and laterOracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Information in this document applies to any platform.
Purpose
When called from an AFTER LOGON trigger, DBMS_SESSION.SET_ROLE does not keep roles enabled within the session after logon, although the AFTER LOGON trigger executes correctly. The note is investigating this problem and clarifies why this is not possible.
Scope
Any DBA wanting to enable the roles dynamically.
Details
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |