My Oracle Support Banner

Using Remote Diagnostic Agent (RDA) to diagnose a JDBC client (Doc ID 1376181.1)

Last updated on MAY 19, 2017

Applies to:

JDBC - Version 10.1.0.5 to 11.2.0.3.0 [Release 10.1 to 11.2]
Information in this document applies to any platform.

Goal

The Remote Diagnostic Agent can provide some useful information when run on an Oracle installation such as an Oracle Client, Oracle Database, Oracle Application Server (Weblogic-based or the older OC4J-based) installations.  This note highlights the feature that are useful to debug a JDBC client. Please note however that you cannot run an RDA on a downloaded JDBC driver  jar file or other type of ad-hoc environment not provided by an Oracle installation,  which is often the case with JDBC/thin environments such as downloaded drivers or third party application server installations bundling Oracle JDBC driver jar files.

For general information about RDA please refer to <Note 314422.1> Remote Diagnostic Agent (RDA) 4 - Getting Started

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
 Setting up the JDBC module:
 Running the RDA:
 Viewing the RDA JDBC reports:
 Limitations of RDA with JDBC
 Use of RDA in diagnosing JDBC connectivity issues
References

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