How to Perform the Equivalent of SQL*Net Client Tracing with Oracle JDBC Thin Driver (Doc ID 793415.1)

Last updated on AUGUST 11, 2017

Applies to:

JDBC - Version 10.2.0.1 to 11.1.0.7 [Release 10.2 to 11.1]
Information in this document applies to any platform.

Goal

The Oracle JDBC thin driver uses a java based implementation of  the SQLNET protocol (JavaNet layer).

Unlike the JDBC OCI driver, the SQLNET trace is not available with the JDBC thin driver at the client side for Oracle JDBC Driver versions < 11.2.  Therefore, to diagnose JDBC connection or other database related error conditions, only the SQLNET server side trace is available. As a result, it can be difficult to get a good understanding of the problem with only one end of the equation. 

This article describes how to enable a similar sqlnet client trace with  the JDBC thin driver. This can be done by using a new utility (packaged as a JAVA jnettrace.jar library), the JavaNet utility, which allows tracing of  the JavaNet layer. 

This utility,  attached to the article, is available on OTN:

http://www.oracle.com/technetwork/database/enterprise-edition/jnettrace.jar

From release 11.2, the JDBC Thin Driver includes a network trace capability. Please refer to <Document: 1050942.1> How to Trace the Network Packets Exchanged Between JDBC and the RDBMS.

 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms