SQL ID changes Plan hash value [message #683717] |
Tue, 16 February 2021 07:38 ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
JackBauer
Messages: 24 Registered: February 2021
|
Junior Member |
|
|
Hello,
When you see that an SQL ID has changed its plan hash value and you notice that the old plan hash value is better, do you just fix the old plan hash value with a profile?
I assume that Oracle changed the plan for a reason, right? So why keep the old one?
Thanks
|
|
|
|
Re: SQL ID changes Plan hash value [message #683856 is a reply to message #683717] |
Thu, 25 February 2021 01:01 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
John Watson
Messages: 8944 Registered: January 2010 Location: Global Village
|
Senior Member |
|
|
You could investigate why the optimizer felt it necessary to reparse and create a new cursor. There are many reasons, and either plan may be appropriate depending on circumstances. v$sql_shared_cursor will help.
|
|
|
|
|
|