DRCP Session Purity Value Incorrectly Set to NEW Rather Than SELF When Using LDAP Connection
(Doc ID 3053957.1)
Last updated on OCTOBER 16, 2024
Applies to:
JDBC - Version 19.3 and laterInformation in this document applies to any platform.
Symptoms
JDBC connections using DRCP (Database-Resident Connection Pooling) are working correctly when using both LDAP and non-LDAP connections.
However, when using an LDAP connection, the value for Session Purity incorrectly shows "NEW" rather than "SELF".
Specifically: When querying the view GV$CPOOL_CONN_INFO, the value returned for PURITY correctly shows "SELF" for non-LDAP connections, but incorrectly shows "NEW" for LDAP connections.
This does not impact the connectivity or functionality of the JDBC connection.
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
Symptoms |
Cause |
Solution |
References |