"Protocol Violation" or "OALL8 is in an inconsistent state" after java.lang.OutOfMemoryError
Last updated on AUGUST 03, 2016
Applies to:JDBC - Version 10.2.0.1 to 126.96.36.199.0 [Release 10.2 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 09-May-2013***
A program is catching java.lang.OutOfMemoryError and continues after this (maybe after clearing some internal large Objects).
After this various Exceptions can occur in the JDBC stack:
- Protocol violation
- OALL8 is in an inconsistent state
a program is catching with one of the following Classes and continues after the catch has completed.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms