How to Perform the Equivalent of SQL*Net Client Tracing with Oracle JDBC Thin Driver Releases Prior to 11.2
(Doc ID 793415.1)
Last updated on AUGUST 31, 2023
Applies to:
JDBC - Version 10.2.0.1 to 11.1.0.7 [Release 10.2 to 11.1]Oracle Database - Enterprise Edition - Version 19.13.0.0.0 to 19.13.0.0.0 [Release 19]
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
- The instructions in this document apply to JDK versions 8 and earlier. Please refer to <Document:401934.1> Starting With Oracle JDBC Drivers - Installation, Certification, and More! for JDBC and JDK certified combinations.
- From release 11.2 and forward , 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
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
| Goal |
| Solution |
| References |