ORA-02391 and Invalid life cycle state When SESSIONS_PER_USER Below InitPoolSize
(Doc ID 2567174.1)
Last updated on JULY 19, 2019
Applies to:Universal Connection Pool - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
When using Oracle UCP 220.127.116.11 with Oracle JDBC 18.104.22.168 with Oracle JDK 8 on Linux x86_64 to communicate with an Oracle Database 12c (single instance w DataGuard), if the initPoolSize of the UCP is set to a value higher than the SESSIONS_PER_USER database profile parameter, the following behavior is seen:
- up to SESSIONS_PER_USER connections are established.
- ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit is received.
- the pool life cycle state is set the FAILED .
This is an expected behavior, as the number of SESSIONS_PER_USER is exceeded to simulate the failure.
The pool is not usable in the FAILED state, and stopping the pool using the UCP manager stopConnectionPool() API does not have any effect on the available connections,
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