Change of "SESSION_EDITION_NAME" at the DB Level Is Not Reflecting at Apex Level When Tested Using the SQL Workshop
(Doc ID 2796550.1)
Last updated on OCTOBER 06, 2022
Applies to:
Oracle Application Express (APEX) - Version 18.1 and laterOracle Database 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.
Symptoms
After patching the database and a new session is enabled at the DB level, the edition change is not appearing at the Apex Level when tested using the following query.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |