Statement Caching Needs Table Structure to Be Retained in the Database
(Doc ID 1361340.1)
Last updated on OCTOBER 17, 2022
Applies to:
JDBC - Version 10.2.0.1 and laterInformation in this document applies to any platform.
Symptoms
When the table is altered in its structure and a Statement is reused on client side (Statement originally created and executed before the alter) in JDBC, this results in various errors:
- Protocol Violation
- java.lang.ArrayIndexOutOfBoundsException
- lockup (hang) forever, causing 100% cpu usage
For example:
Changes
- table structure was altered and a Statement is reused
- select * is being used
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 |