You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
asqlmon.sql: SQL Monitoring-like execution plan line level drilldown into SQL response time | Tanel Poder Consulting
I don’t have much time for a thorough blog post, so I’ll just paste in an example output of my asqlmon.sql script, which uses ASH sql_plan_line columns for displaying where inside your execution plan response time has been spent. Why not just use Oracle’s own SQL Monitoring reports? Well, SQL monitoring is meant for “long running” queries, which are not executed very frequently. In other words, you can’t use SQL Monitoring for drilling down into your frequently executed OLTP-style SQL. - Linux, Oracle, SQL performance tuning and troubleshooting - consulting & training.
I haven't updated the gasqlmon.sql for a while, I think. I probably should conver the asqlmon.sql to use the GV$ views, although there's some complexity regarding linking up different child cursor#'s across RAC nodes. For now I've just used the dasqlmon.sql (might have to wait until enough v$ash data is written there).
asqlmon.sql: SQL Monitoring-like execution plan line level drilldown into SQL response time | Tanel Poder Consulting
I don’t have much time for a thorough blog post, so I’ll just paste in an example output of my asqlmon.sql script, which uses ASH sql_plan_line columns for displaying where inside your execution plan response time has been spent. Why not just use Oracle’s own SQL Monitoring reports? Well, SQL monitoring is meant for “long running” queries, which are not executed very frequently. In other words, you can’t use SQL Monitoring for drilling down into your frequently executed OLTP-style SQL. - Linux, Oracle, SQL performance tuning and troubleshooting - consulting & training.
https://tanelpoder.com/2013/03/17/asqlmon-sql-sql-monitoring-like-execution-plan-line-level-drilldown-into-sql-response-time/
The text was updated successfully, but these errors were encountered: