In this Document
  Symptoms
  Cause
  Solution
  References

Applies to:

Symptoms

Cause

This is due to the bind buffer mismatch of the current child cursor. If oracle is unable to bind the current value to the existing child cursors bind buffer, oracle upgrades the existing child cursor with a high bind buffer. This will force the query to
do a hard parse and a new child cursor will be created.

The previous one will be marked 'dont use'.  

These types of cursors are never re-used.  As a result, they permanently occupy a slot in the child table which will result in increasing the version count. 

This issue has been described in the Bug: 2450264  base bug to Bug: 3012881

Solution

The fix of the bug 2450264 has introduced a new event (10503) which enables users to specify a character bind buffer length. Depending on the length used, the character  binds  in the child cursor can all be created using the same bind length; 

ALTER SESSION SET EVENTS '10503 trace name context forever, level '; 

Eg:
ALTER SESSION SET EVENTS '10503 trace name context forever, level 4096';

References