Top 10 documents that are linked to SRs as solutions, for JDBC issues, from Sept 2014 thru Dec 2014.
By jhpierce -Oracle on Jan 05, 2015
The following are the top 10 documents that are linked to SRs as solutions, for JDBC issues, from Sept. 2014 thru Dec. 2014.
|1361107.1||Troubleshooting ORA-3137  Errors Encountered When Using Oracle JDBC Driver: Oracle Customer Support has observed a large volume of issues reported by customers experiencing ORA-3137  and occasionally ORA-3137  errors when connecting to an Oracle RDBMS using the Oracle JDBC driver. This document enumerates troubleshooting approaches that have proven successful.|
|401934.1||Starting With Oracle JDBC Drivers: This FAQ provides practical information when starting with Oracle JDBC drivers. A description of the Oracle JDBC drivers is provided so that you can choose which Oracle JDBC driver can be used with your Java application.|
|467804.1||How To Determine The Exact JDBC Driver Version (9.x - 11.x) For Standalone Programs Retrieve diagnostic information about your JDBC/JDK environment that is especially useful for Support Analysts .Includes: database version, JDBC driver version, JDK version, PATH, BOOTSTRAP, list of jars in the JRE extensions directory, CLASSPATH and JDBC URL. (Standalone Programs)|
|467808.1||Standard JDBC diagnostics for Application Servers Retrieve diagnostic information about your JDBC/JDK environment used within a Java Enterprise container that is especially useful for Support Analysts. Includes: database version, JDBC driver version, JDK version, PATH, BOOTSTRAP, JRE Extensions directory, CLASSPATH and JDBC URL and debug flags information. ( Application Server specific)|
|334471.1||Understanding Transparent Application Failover (TAF) and Fast Connection Failover (FCF) This note is intended to give explanation on two RAC concepts, Transparent Application Failover (TAF) and Fast Connection Failover (FCF).|
|1555793.1||JDBC Connections Using SCAN Fail With ORA-12516/ORA-12520 JDBC thin connections using Single Client Access Name (SCAN) fail with errors: ORA-12520: TNS:listener could not find available handler for requested type of server ORA-12516: TNS : listener could not find instance with matching protocol stack|
|1050942.1||How to Trace the Network Packets Exchanged Between JDBC and the RDBMS in Release 11.2 This capability allows you to trace the network packets that the driver exchanges with the server.|
|1384829.1||This JDBC code sample demonstrates how LOB resources can be released without having to close the JDBC connection. This code sample implements the recommendation found in Note 802897.1 How to Release the Temp LOB Space and Avoid Hitting ORA-1652.|
|301999.1||The JDBC application reports one of the following errors when trying to execute stored procedures:java.sql.SQLException:
ORA-04068: existing state of packages has been discarded
ORA-04061: existing state of package body "xxxxx.xxxxxx" has been invalidated
ORA-04065: not executed, altered or dropped package body "xxxxx.xxxxxx"
ORA-06508: PL/SQL: could not find program unit being called
ORA-06512: at line 1
|793415.1||How to Perform the Equivalent of SQL*Net Client Tracing with Oracle JDBC Thin Driver The Oracle JDBC thin driver uses a java based implementation of the SQLNET protocol (JavaNet layer).|