My Oracle Support Banner

"OALL8 is in an inconsistent state" Following "Stuck" Thread, "Unstuck" Thread, and "No more data to read from socket" (Doc ID 943327.1)

Last updated on FEBRUARY 22, 2019

Applies to:

JDBC - Version 10.2.0.3 and later
Information in this document applies to any platform.
***Checked for relevance on 11-Sep-2012***

Symptoms

An application runs on a WebLogic application server and connects to a version 10.2.0.3 database via JDBC/Thin 10.2.0.3 ojdbc14.jar. The application uses a connection pool.

Intermittently, for a period of time, a few times a day, repeated executions of one particular query "spin". Instead of returning results in less than one second (the normal situation) the query fails to return results.

At the times the query "spins", WebLogic logs show "stuck" threads. These threads are waiting at java.net.SocketInputStream.socketRead0.

About 10 minutes after the stuck thread warning, a "No more data to read from socket" exception occurs and the thread becomes unstuck. A few seconds later an "OALL8 is in an inconsistent state" exception occurs and the connection is closed.

The series of events and exceptions are shown in the following excerpts from the WebLogic log.

To remove customer specific information from the log excerpts, some names have been replaced with various combinations of "xxx", "yyy", and "zzz". Also some text has been replaced with "<... text omitted ...>".


Cause

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
Symptoms
Cause
Solution
References

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