Dimitri Gielis
Dimitri Gielis's Blog

Follow

Dimitri Gielis's Blog

Follow
Fix for ORDS connection pool named |default|lo| is not able to proxy to the schema

Fix for ORDS connection pool named |default|lo| is not able to proxy to the schema

Dimitri Gielis's photo
Dimitri Gielis
·Jan 13, 2023·

1 min read

Play this article

Today on our server running ORDS 22.4 and Oracle APEX 22.2 we had a weird error:

The database user for the connection pool named |default|lo|, is not able to proxy to the schema named ET_DEV. This could be a configured restriction on the maximum number of database sessions or an authorization failure.

I have seen 503 errors before, but not one with default|lo. It might be because we imported the REST web services from another system and only noticed it now or it might have been other things, we are not sure what caused it. Other Oracle APEX workspaces and schemas didn't have this issue.

The fix for us was a 4-step process:

  1. Export All Web Services

  2. De-Register the schema from ORDS

  3. Enable the schema again

  4. Import All Web Services again

Hope it helps you when you have it.

 
Share this