Identifying Java Client Software

The best minds from Teradata, our partners, and customers blog about relevant topics and features.
Teradata Employee

Beginning with Teradata Database 14.0 and Teradata JDBC Driver, the Client Attributes feature records a variety of information about the client system and client software in the system tables DBC.SessionTbl and DBC.EventLog.

The Client Attributes are recorded at session logon time. Subsequently, the system views DBC.SessionInfoV and DBC.LogOnOffV can be queried to obtain information about the client system and client software on a per-session basis.

Database administrators may wish to identify Java client software used to access the Teradata Database. Sessions that use the Teradata JDBC Driver can be identified by the Client Attribute ClientJavaVersion with a non-NULL value. Another Client Attribute, ClientProgramName, identifies the client Java application. The system views DBC.SessionInfoV and DBC.LogOnOffV contain the ClientJavaVersion and ClientProgramName columns.

The following query will list the combinations of Java JDK/JRE version and Java client software used to access the Teradata Database:

    select distinct ClientJavaVersion, ClientProgramName from DBC.LogOnOffV where ClientJavaVersion is not null order by 1, 2;

The table below lists the ClientProgramName reported for commonly-used Java client software. Note that the ClientProgramName values may be in mixed-case, or may be in all uppercase.

Java Client Software


Apache Tomcat

IBM WebSphere


Oracle WebLogic


Teradata Studio

Viewpoint Data Collection Service (DCS)


Viewpoint Portal (which uses Apache Tomcat)

The source file reference in parentheses following the class name may differ from one version of the JDK to another, and will not be available (saying "Unknown Source") if the JIT compiler has converted the Java bytecode into native CPU instructions.

1 Comment

Thank you for posting this, it is extremely helpful.