Looking in OEM today i see:
Look for top reason for cursor environment mismatch in V$SQL_SHARED_CURSOR.
Performance Finding Details: Hard Parse Due to Sharing Criteria
Finding SQL statements with the same text were not shared because of cursor environment mismatch. This resulted in additional hard parses which were consuming significant database time
In that V$SQL_SHARED_CURSOR view i'm seeing 'Y'(s) in some of the columns.
Is top-level DDL cursor
The remote base objects of the existing child cursor do not match
Cursor is not shared because value of one or more user binds is different
and this has a potential to change the execution plan
What is the significance of these?