My Oracle Support Banner

Oracle Rest Data Service (ORDS) Errors : 503 Service Unavailable, 403 error for ORA-28150 APEX REST or APEX Workspace / Application Static Files (Doc ID 1944864.1)

Last updated on APRIL 06, 2023

Applies to:

Oracle Application Express (APEX) - Version 4.0 and later
Oracle REST Data Services - Version 2.0 and later
Oracle Database Cloud Exadata 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
Information in this document applies to any platform.

Goal

After deploying ords.war and i.war in Weblogic, APEX runs successfully, however, when trying to test a RESTful service from SQL Workshop > RESTful Services > RESTful Service Module >Resource Template > Resource Handler, the request is failing with an HTTP 503 error.


Debugging was turned on for the ORDS by adding the following entries in defaults.xml and tested in standalone mode:
<entry key="debug.debugger">true</entry>
<entry key="debug.printDebugToScreen">true</entry>

The debug output showed the following error:
WebException [statusCode=503]
at oracle.dbtools.rt.web.WebException.webException(WebException.java:343)
at oracle.dbtools.rt.web.WebException.serviceUnavailable(WebException.java:323)
at oracle.dbtools.rt.web.HttpEndpointBase.restfulServices(HttpEndpointBase.java:443)
at oracle.dbtools.rt.web.HttpEndpointBase.service(HttpEndpointBase.java:164)

...

at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: oracle.dbtools.common.jdbc.ConnectionPoolException: The pool named: apex_rt is not correctly configured, error: ORA-28150 proxy not authorized to connect as client

at oracle.dbtools.common.jdbc.ConnectionPoolException.badConfiguration(ConnectionPoolException.java:65)

 

 

OR

APEX workspace and static application files fail. The errors in the log show the following:
<Oct 8, 2018 12:00:35,210 PM CDT> <Error> <oracle.dbtools> <BEA-000000> <oracle.dbtools.url.mapping.TargetNotAvailableException: The database user for the connection pool named apex_rt, is not authorize
d to proxy to the schema named <USER>
ServiceUnavailableException [statusCode=503, reasons=[The database user for the connection pool named apex_rt, is not authorized to proxy to the schema named <USER>]]
at oracle.dbtools.url.mapping.URLMappingBase.doFilter(URLMappingBase.java:109)
at oracle.dbtools.url.mapping.filter.URLMappingFilter.doFilter(URLMappingFilter.java:127)
at oracle.dbtools.http.filters.HttpFilter.doFilter(HttpFilter.java:47)
at oracle.dbtools.http.filters.FilterChainImpl.doFilter(FilterChainImpl.java:64)
at oracle.dbtools.http.auth.external.ExternalSessionFilter.doFilter(ExternalSessionFilter.java:59)
Truncated. see log file for complete stacktrace
Caused By: oracle.dbtools.url.mapping.TargetNotAvailableException: The database user for the connection pool named apex_rt, is not authorized to proxy to the schema named <USER>
at oracle.dbtools.url.mapping.db.PoolInjector.inject(PoolInjector.java:59)
at oracle.dbtools.url.mapping.db.DatabaseURLMappingImpl.addServices(DatabaseURLMappingImpl.java:306)
at oracle.dbtools.url.mapping.URLMappingBase.doFilter(URLMappingBase.java:80)
at oracle.dbtools.url.mapping.filter.URLMappingFilter.doFilter(URLMappingFilter.java:127)
at oracle.dbtools.http.filters.HttpFilter.doFilter(HttpFilter.java:47)
Truncated. see log file for complete stacktrace


How do you correct this error?

Solution

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
Goal
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.