Home Discussions Questions & Answers Investigating Unstable SQL Execution Plans (Bind Sensitivity)

Investigating Unstable SQL Execution Plans (Bind Sensitivity)

Avatar photoCustomer November 16, 2020 at 11:01 am

We noticed some high-load transactional SQLs in our AWR summary showing ‘Y’ for the ‘Is Bind Sensitive’ column. What does this mean in the context of EBS, and is it usually a good or bad sign?

Viewing 4 reply threads
  • Author
    Replies
    • Support November 16, 2020 at 3:31 pm  

      A value of ‘Y’ means the database might consider a different execution plan (Adaptive Cursor Sharing) based on different bind values. For typical Oracle EBS transactional SQLs, the execution path should generally remain stable. Therefore, ‘Y’ often indicates ‘instable’ SQL where the optimizer struggles to find the best execution path.

    • Avatar photoCustomer November 17, 2020 at 2:03 pm  

      Which report provides this ‘Is Bind Sensitive’ column?

    • Support November 18, 2020 at 2:09 am  

      You can find this column in the DBA AWR SQL Performance Summary report, which gives an overview of top SQL load and performance issues.

    • Avatar photoCustomer November 18, 2020 at 6:33 am  

      If we identify a poorly performing SQL, what is a quick way to check its average I/O performance per row retrieved?

    • Support November 19, 2020 at 10:56 am  

      Look at the ‘IO Row’ column in the DBA AWR SQL Performance Summary. This shows the average I/O per individual row retrieved. For data extraction queries without aggregation, this metric is a good indicator of efficiency.

Viewing 4 reply threads
  • You must be logged in to reply to this post.

Login with: