Child Cursor Increase Due To BIND MISMATCH Even When Using Same Bind Values
(Doc ID 2936464.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 19.11.0.0.0 to 21.1 [Release 19 to 21.0]Information in this document applies to any platform.
Symptoms
When running a n query using bind variables, the query creates new child cursor due to "bind mismatch" each time the query is run, even though there are no changes in the bind variables.
Changes
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 |