My Oracle Support Banner

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 JUNE 24, 2021

Applies to:

JDBC - Version 12.1.0.2.0 and later
Information 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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.