Intermittent ORA-174012 Protocol Violation Messages Are Received when Reading Data with ojdbc6.jar and Java 1.6 32-bit on Solaris 64-bit Machine (Doc ID 1245755.1)

Last updated on SEPTEMBER 26, 2023

Applies to:

Symptoms

Intermittent "Protocol violation" (ORA-17401) messages are signaled when using Oracle Data Integrator (ODI) -- or pure Java code -- to execute a SELECT statement that reads a large amount of data from an Oracle database using a JDBC Driver.

The ODI Agent / Java code is running on Oracle Solaris 64-bit operating system, and uses:

• a JVM 1.6 32-bit, and
• the THIN Oracle JDBC driver present in the ojdbc6.jar file.

Changes

The issue only occurs when the executions are performed on Solaris 64-bit platform, with a 32-bit Java Machine 1.6, and the ojdbc6.jar Oracle JDBC driver.

Below is a brief description of tests that have been run:

• On Windows XP 32-bit:
  

  Java VM	Oracle JDBC driver (version 11.1 0 7.0 and/or 11.2.0.1.0)	Result
  1.5 (32-bit)	ojdbc5.jar	OK
  1.6 (32-bit)	ojdbc6.jar	OK

• On Oracle Solaris 64-bit:
  

  Java VM	Oracle JDBC driver (version 11.1 0 7.0 and/or 11.2.0.1.0)	Result
  1.5 (32-bit)	ojdbc5.jar	OK
  1.5 (32-bit)	ojdbc6.jar	Irrelevant (incompatibility between the JVM and the JDBC version/compile)
  1.6 (32-bit)	ojdbc5.jar	OK
  1.6 (32-bit)	ojdbc6.jar	Not OK (tested with JVM 1.6.0_18 and 1.6.0_21)
  1.6 (64-bit)	ojdbc6.jar	OK (tested with JVM 1.6.0_18 and 1.6.0_21)

Cause