APEX_PUBLIC_USER Account Gets Locked Continuously after Upgrade From APEX Listener 2.0.1 to ORDS
(Doc ID 1940699.1)
Last updated on DECEMBER 01, 2023
Applies to:
Oracle Application Express (APEX) - Version 4.2.5 and laterOracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
APEX 4.2.5 is using with APEX Listener 2.0.1, and is deployed in a managed server.
The managed server configured with APEX has been configured so that it can be called by the Oracle HTTP Server (OHS), using the WebLogic plug-in / mod_wl_ohs.conf.
After upgraded the APEX listener 2.0.1 to Oracle Rest Data Service (ORDS) 2.0.9, the account APEX_PUBLIC_USER gets locked when running APEX application:
http://<OHS_HOST>:<OHS_PORT>/apex
Changes
Upgraded the APEX Listener 2.0.1 to Oracle Rest Data Service 2.0.9.
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 |
| Changes |
| Cause |
| Solution |
| References |