The database user for the connection pool named |apex|pu|, is not able to proxy to the schema named <schem_user>. (Doc ID 2810884.1)

Last updated on FEBRUARY 14, 2022

Applies to:

Oracle REST Data Services - Version 18.1 and later
JDBC - Version 18.0.0.0.0 and later
Information in this document applies to any platform.

Symptoms

ORDS is installed in 19c DB and when attempting to test RESTFul Services, we get below error:

2021-08-26T07:42:24.324Z SEVERE The database user for the connection pool named |apex|pu|, is not able to proxy to the schema named <schem_user>. This could be a configured restriction on the maximum number of database sessions or an authorization failure.
oracle.dbtools.url.mapping.TargetNotAvailableException: The database user for the connection pool named |apex|pu|, is not able to proxy to the schema named <schem_user>. This could be a configured restriction on the maximum number of database sessions or an authorization failure.
at oracle.dbtools.url.mapping.db.PoolInjector.inject(PoolInjector.java:64)
at oracle.dbtools.common.jdbc.DataSourceConnection.getPooledConnection(DataSourceConnection.java:210)
... 78 more
Caused by: java.sql.SQLException: ORA-01017: invalid username/password; logon denied

We can connect on <schema_user> using ORDS_PUBLIC_USER as proxy from SQPLUS and SQLDEV

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

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

The database user for the connection pool named |apex|pu|, is not able to proxy to the schema named <schem_user>. (Doc ID 2810884.1)

Applies to:

Symptoms

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!