After ORDS 18 Installation 503 Error Occurs - The database user for the connection pool named |apex|pu|, is not authorized to proxy to the schema named APEX_PUBLIC_USER
(Doc ID 2485210.1)
Last updated on APRIL 14, 2024
Applies to:
Oracle REST Data Services - Version 18.3 and laterInformation in this document applies to any platform.
Symptoms
1. New installation of ORDs18 solely to use RESTful services.
2. APEX is not installed.
3. RAC DB. RAC Status is set in DBA Registry.
4. ORDS log shows:
WARNING: The database user for the connection pool named |apex|pu|, is not authorized to proxy to the schema named APEX_PUBLIC_USER
oracle.dbtools.common.jdbc.ConnectionPoolConfigurationException: The database user for the connection pool named |apex|pu|, is not authorized to proxy to the schema named APEX_PUBLIC_USER
............................
............................
............................
Caused by: oracle.dbtools.common.ucp.ConnectionLabelingException: Error occurred when attempting to configure url: jdbc:oracle:thin:@//machine:port/service_name with labels: {oracle.dbtools.jdbc.label.schema=APEX_PUBLIC_USER}
.....................................
Caused by: java.sql.SQLException: ORA-01017: invalid username/password; logon denied
5. DBA_AUDIT_TRAIL view is showing connections are being made by ORDS_PUBLIC_USER and indicates attempt to logon by APEX_PUBLIC_USER:
Changes
New installation of ORD 18 or upgrade to ORDS 18.
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 |