The cursor is not marked bind sensitive because the bind variable value can potentialy alter the plan, but because the column used in the predicate part has histogram. The column might be higly skewed but if Oracle dosn't know this information via histogram the cursor will not be maked bind sensitive. There are two other reasons that might mark a cursor bind sensitive (a) range predicate (b) partition key used in the predicate part
Hi Thanks for more insight into the reasons that make a child cursor bind aware, enjoyed reading the above blog posts.
>Check if the SQL is bind sensitive or Bind aware?
Where is that query?
I am not sure why the screenshot got truncated, But the query is as below
select is_bind_sensitive, is_bind_aware, sql_id, inst_id, child_number from gv$sql where sql_text like '%UPDATE XXG.XXG_ORD_STATUS_IN_JMS_QT tab set tab.user_data.text_lob%';
If you want to see the screen shot fully you can goto :- oracledbascriptsfromajith.blogspot.com/.../find-details-of-troublesome-sql-that.html