The JDBC Call Connection.setClientInfo() Does Not Update V$SESSION if Value is the Same as a Previous Call
(Doc ID 2613559.1)
Last updated on OCTOBER 17, 2022
Applies to:
JDBC - Version 12.1.0.2.0 and laterInformation in this document applies to any platform.
Symptoms
When using the JDBC driver, calls to setClientInfo() do not get set if the value being set is the same as a previous call.
For example, con.setClientInfo("OCSID.CLIENTID", ...) doesn't set the supplied value if it's the same as the one supplied last time.
This should always be set, because it can be wiped out in various ways (for example, if a proxy session ends).
For reference, this method call is discussed in the 12.1.0.2 JDBC Developer's Guide here.
Changes
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 |
Changes |
Cause |
Solution |
References |