"Protocol Violation" or "OALL8 is in an inconsistent state" after java.lang.OutOfMemoryError
(Doc ID 1269551.1)
Last updated on JANUARY 29, 2022
Applies to:
JDBC - Version 10.2.0.1 to 11.2.0.3.0 [Release 10.2 to 11.2]Information in this document applies to any platform.
Symptoms
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
- java.lang.NullPointerException
- OALL8 is in an inconsistent state
Changes
a program is catching with one of the following Classes and continues after the catch has completed.
java.lang.Object
java.lang.Throwable
java.lang.Error
java.lang.VirtualMachineError
java.lang.OutOfMemoryError
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 |
| Changes |
| Cause |
| Solution |
| References |