AFTER LOGON Triggers Don't Allow DBMS_SESSION.SET_ROLE to Keep Roles Enabled
(Doc ID 106140.1)
Last updated on MARCH 01, 2019
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 to 188.8.131.52 [Release 8.1.7 to 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Checked for relevance on 10-Jan-2012
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.
Any DBA wanting to enable the roles dynamically.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!