My Oracle Support Banner

Master Note: Understanding the "OALL8 is in an Inconsistent State" Exception (Doc ID 944692.1)

Last updated on FEBRUARY 03, 2019

Applies to:

JDBC - Version 10.1.0.2 to 11.1.0.7 [Release 10.1 to 11.1]
Oracle WebLogic Server - Version 10.3.3 to 10.3.3
Information in this document applies to any platform.
***Checked for relevance on 05-Apr-2013***

Goal

Over the past couple of years you have occasionally seen the exception "OALL8 is in an inconsistent state" - primarily in application server log files but also sometimes in the log file from a large standalone Java application. The exceptions were intermittent and could not be reproduced at will. You were not able to identify a cause for any of the occurrences of the exception. You ask if there is any information that will help you to understand this exception.

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
 1. Generic exception
 2. JDBC code
 3. Relationship to "Protocol Violation"
 4. Causes
 4.1. Cause due to earlier problem that gave an error or exception
 4.1.1. Preceding exception: java.lang.NullPointerException, Cause: Unpublished JDBC Bug 4390875
 4.1.2. Preceding exception: Bigger type length than Maximum, Cause: JDBC Bug 3923624
 4.1.3. Preceding exception: java.lang.OutOfMemoryError
 4.1.4. Preceding exception: No more data to read from socket, Cause: Database Bug 5851267
 4.1.5. Preceding exception: No more data to read from socket, Cause: Database Bug 5364143
 4.2. Cause due to earlier problem that did not give an error or exception
 4.2.1. Sharing a connection between threads
 4.2.2. Insufficient memory
 4.3. Cause not due to earlier problem
 4.3.1. JDBC syntax, Note 370271.1
 5. No cause found and no earlier problem found
 5.1. Test with JDBC 11.2
 5.2. Keep looking for an earlier problem
 5.3. Provide a reproducible test case
 6. Possible workarounds
 6.1. If the exception does not cause a problem ignore it
 6.2. Validate connection before borrowing from pool
 6.3. Catch exception, get new connection, and redo whatever failed
References

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