1 Reply Latest reply on Dec 11, 2019 12:48 PM by MatthiasHoys

    ORDS 19.2 error: The database user for the connection pool named |apex|rt|, is not authorized to proxy to the schema named APEX_PUBLIC_USER

    MatthiasHoys

      Hi,

      Version of APEX used is 5.1.4, Oracle Database is 12.2.0.1.

      We recently upgraded from ORDS 3.0.12 to ORDS 19.2 and now I'm seeing following errors in the Tomcat log file:

       

      Caused by: oracle.dbtools.common.jdbc.ConnectionPoolConfigurationException: The database user for the connection pool named |apex|rt|, is not authorized to proxy to the schema named APEX_PUBLIC_USER

      at oracle.dbtools.common.jdbc.ConnectionPoolExceptions.from(ConnectionPoolExceptions.java:46)

      at oracle.dbtools.common.jdbc.ConnectionPoolExceptions.from(ConnectionPoolExceptions.java:53)

      at oracle.dbtools.common.jdbc.DataSourceConnection.getPooledConnection(DataSourceConnection.java:233)

      at oracle.dbtools.common.jdbc.DataSourceConnection.getPooledConnection(DataSourceConnection.java:192)

      at oracle.dbtools.common.jdbc.DataSourceConnection.getDefaultConnection(DataSourceConnection.java:145)

      at oracle.dbtools.common.jdbc.DataSourceConnection.getConnection(DataSourceConnection.java:59)

      at oracle.dbtools.common.pools.DataSourceTargetImpl.getConnection(DataSourceTargetImpl.java:60)

      at oracle.dbtools.common.config.db.SchemaConnectionFactoryBase.inject(SchemaConnectionFactoryBase.java:84)

      at oracle.dbtools.url.mapping.db.PoolInjector.inject(PoolInjector.java:57)

      ... 52 more

      Caused by: oracle.dbtools.common.ucp.ConnectionLabelingException: Error occurred when attempting to configure url: unknown with labels: {oracle.dbtools.jdbc.label.schema=APEX_PUBLIC_USER}

      at oracle.dbtools.common.ucp.LabelingCallback.handle(LabelingCallback.java:147)

      at oracle.dbtools.common.ucp.LabelingCallback.proxyToSchema(LabelingCallback.java:210)

      at oracle.dbtools.common.ucp.LabelingCallback.configure(LabelingCallback.java:76)

      at oracle.ucp.common.UniversalConnectionPoolImpl.getAvailableConnectionHelper(UniversalConnectionPoolImpl.java:711)

      at oracle.ucp.common.UniversalConnectionPoolImpl.getAvailableConnection(UniversalConnectionPoolImpl.java:650)

      at oracle.ucp.common.UniversalConnectionPoolImpl.borrowConnectionWithoutCountingRequests(UniversalConnectionPoolImpl.java:261)

      at oracle.ucp.common.UniversalConnectionPoolImpl.borrowConnectionAndValidate(UniversalConnectionPoolImpl.java:153)

      at oracle.ucp.common.UniversalConnectionPoolImpl.borrowConnection(UniversalConnectionPoolImpl.java:122)

      at oracle.ucp.jdbc.JDBCConnectionPool.borrowConnection(JDBCConnectionPool.java:174)

      at oracle.ucp.jdbc.oracle.OracleJDBCConnectionPool.borrowConnection(OracleJDBCConnectionPool.java:613)

      at oracle.ucp.jdbc.oracle.OracleConnectionConnectionPool.borrowConnection(OracleConnectionConnectionPool.java:103)

      at oracle.ucp.jdbc.PoolDataSourceImpl.getConnection(PoolDataSourceImpl.java:1981)

      at oracle.ucp.jdbc.PoolDataSourceImpl.access$400(PoolDataSourceImpl.java:201)

      at oracle.ucp.jdbc.PoolDataSourceImpl$31.build(PoolDataSourceImpl.java:4279)

      at oracle.ucp.jdbc.PoolDataSourceImpl.getConnection(PoolDataSourceImpl.java:1917)

      at oracle.dbtools.common.config.db.PoolDataSourceThunk.getConnection(PoolDataSourceThunk.java:116)

       

      The proxy grants look ok:

      select * from proxy_users

       

      APEX_REST_PUBLIC_USER APEX_PUBLIC_USER NO PROXY MAY ACTIVATE ALL CLIENT ROLES

      ORDS_PUBLIC_USER APEX_REST_PUBLIC_USER NO PROXY MAY ACTIVATE ALL CLIENT ROLES

      ORDS_PUBLIC_USER APEX_PUBLIC_USER NO PROXY MAY ACTIVATE ALL CLIENT ROLES

       

      Any idea what could be wrong? I tested a number of RESTful web services, either defined in APEX or by using ORDS_METADATA, but they look to be working fine.

      So I'm not sure if there's an actual issue or not (nobody has reported anything so far).

       

      Thanks

      Matthias