Database Tuning (MOSC)

MOSC Banner

OQueries with large number of versions. HASH_MATCH_FAILED.

edited Nov 8, 2018 4:00AM in Database Tuning (MOSC) 1 commentAnswered ✓

EE 12.1.0.2 running on Linux

CURSOR_SHARING=FORCE

ADDM lists Hard Parse Due to Sharing Criteria as one of it's concerns.  Doing a little research I found that HASH_MATCH_FAILED is the most common culprit. 

HASH_MATCH_FAILED    38461  

ROLL_INVALID_MISMATCH    23576 

BIND_EQUIV_FAILURE    4174  

...

Looking at a query that has 1024 children that is being parsed due to HASH_MATCH_FAILED it appears that the query is fine.  The query uses bind variables and doesn't use any timestamp columns.

Statistics and histograms are current.

I have 36 other queries with the same problem (1024 children and HASH_MATCH_FAILED).

Any hints on getting to the bottom of this?  What haven't I looked at.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center