11g High Version Count – Bind Mismatch

The Problem

While running Oracle version I noticed that there were a high number of SQL statements which had a high version count. The CURSOR_SHARING parameter was set to FORCE. When looking in V$SQL_SHARED_CURSOR you will see a Y in the column BIND_LENGTH_UPGRADEABLE.

The Cause

The reason for this happening is described in detail in Metalink note 9689310.8 and is recorded as BUG 9689310. Also, the application  is using different MAX bind variable lengths.

The Solution

This is fixed in or you can get the application developers to change the MAX sizes of the bind variable lengths to be constant which has the same desired effect. To be honest, there are quite a few bugs in so I would upgrade to as soon as you can.

Like it, share it...

Category: 11g

Related Posts

Leave a Reply

Your email address will not be published. Required fields are marked *