Database Tuning (MOSC)

MOSC Banner

Find root cause of “High Version Count”.

edited May 5, 2014 2:12PM in Database Tuning (MOSC) 7 commentsAnswered ✓

We have two SQL_ID's with a “High Version Count”.

On separate occasions, these queries have been involved in blocking sessions and In the AWR report we are seeing “Cursor: mutex S” wait events.

We also tried the Version Report Tool [ID:438755.1] to help determine the root cause we are getting so many child versions of the same SQL.

For one SQL_ID I had 1273 version count. The report stated:

LANGUAGE_MISMATCH:1264 

ROLL_INVALID_MISMATCH :1269

BIND_LENGTH_UPGRADEABLE :1228

(Q)Can anyone explain or direct me to a document that can help me understand this output?

Both SQL_ID's are apart of the Manhattan WMOS system, so we can't really change the application code without a lot of effort.

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