Same SQL ID and Bind Variables in two different applications cause different execution plans
(Doc ID 2952272.1)
Last updated on FEBRUARY 21, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 19.7.0.0.0 and later
Information in this document applies to any platform.
Symptoms
- Same SQL ID, same bind variable values, different execution plans
- Sub optimal execution plan with the nested loops
- Change in bind variable values for oacflg
Changes
Database restart
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
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.