How do I troubleshoot the "javasqlSQLException" error when I try to connect to my Amazon RDS for Oracle instance?

Resolution

You get the error javasqlSQLException: No more data to read from socket because of a connectivity issue between the Oracle server and the client JDBC driver.

The following are the most common reasons and resolution steps for these connection failures:

The connection is abruptly stopped because of network interruptions

Check the alert.log file of the instance for TNS timeout errors posted when the connection timed out from the application end.

For more information on alert log access for RDS instances, see Amazon RDS for Oracle database log files.

The connection is stopped because of Oracle errors on the server side

Check the alert.log file for ORA-0600 or ORA-07445 errors. Collect the trace dump for specific Oracle errors. Check whether these errors have a known fix provided by Oracle support.

The client-server connection isn't active

Set the parameter SQLNET.EXPIRE_TIME to a specified interval to send a probe that verifies that the client-server connections are active.

For more information, see SQLNET. EXPIRE_TIME on the Oracle website.

The RDS for Oracle instance isn't available or was restarted when the JDBC client was trying to use an existing connection to the Oracle server

Retrieve events for the RDS instance. Then, check whether the instance was restarted or stopped when the connections was established from the JDBC client.

The JDBC drivers used to connect to the RDS for Oracle Instance are incompatible

Confirm that the version of JDBC driver is compatible with the DB instance. For the list of compatible JDBC drivers, see Oracle Fusion Middleware supported system configurations on the Oracle website. If the JDBC driver is incompatible, first download the latest JAR file in your source code. Then, include this file in your classpath when you compile the class that creates connections to the database.

For more information, see Downloading the JDBC driver.

The memory components on the client side cause timeouts

Check whether the Oracle Data Integrator has memory components on the client side that cause unwanted timeouts. Be sure that you set the correct values for these components on the client side.

Related information

No more data to read from socket error from an ODI Mapping or integration interface on the Oracle website

Compatibility matrix for Java machines and JDBC drivers used with ODI on the Oracle website

How to define Java options (such as the limits of memory heap, the location of non-Java libraries, etc.) in ODI on the Oracle website