Hi guys,
just a little point to mention about the SQL_PLAN_HASH_VALUE. The
SQL_PLAN_HASH_VALUE is not based on the whole execution plan and its
attributes. The
hash value can be the same, even if the predicate section is different for
example. Please check out Kerry's & Randolf's blog post for further
details:
http://kerryosborne.oracle-guy.com/2013/06/sql-gone-bad-but-plan-not-changed/
Unfortunately the predicate section is also not included in AWR.
Best Regards
Stefan Koehler
Freelance Oracle performance consultant and researcher
Homepage: http://www.soocs.de
Twitter: @OracleSK
Tim Gorman <tim@xxxxxxxxx> hat am 3. April 2015 um 17:39 geschrieben:--
Please note that there is only SQL_PLAN_HASH_VALUE value reported, so plan
instability is not an issue.
On Apr 2, 2015, at 20:54, Kumar Madduri < ksmadduri@xxxxxxxxx
<mailto:ksmadduri@xxxxxxxxx> > wrote:
I found sql_plan_hash_value 2624643529 was executed 4100 times and
this was what was running yesterday when the problem happened(can confirm
that from the time period).
