One of the best parts of my job at Oracle:
I still learn something new every day.
Yesterday I’ve learned from my colleague from Oracle Switzerland, Thomas Teske, that SQL Real Time Monitoring has an embedded default limitation on the number of lines in the statement. If the limit (default: 300 lines) is exceeded the statement won’t be monitored. We both work with a leading Swiss company and we wanted to monitor a complex plan.
Now you may think: Who the heck has statements longer than 300 lines?
Well … sometimes that is beyond your influence as in this particular case this is of course done by the application.
SQL> alter system set “_sqlmon_max_planlines”=800 scope=both;
or set in your spfile:
This limitation is described in:
How to Monitor SQL Statements with Large Plans Using Real-Time SQL Monitoring?
If you’d like to read a bit more about SQL Real Time Monitoring please follow one of these links – and be aware that it’s part of the Tuning Pack license and VERY helpful in many everyday situations. You’ll have to have STATISTICS_LEVEL either TYPICAL (the default) or ALL and CONTROL_MANAGEMENT_PACK_ACCESS=’DIAGNOSTIC+TUNING’ (the default as well).
- Short Support overview:
Monitoring SQL statements with Real-Time SQL Monitoring
- Oracle White Paper from 2009:
Real Time SQL Monitoring
- Very good 4min video and an article by Jeff Smith on how to monitor in SQL Developer:
Real Time SQL Monitoring in SQL Developer On Real Time SQL Monitoring with SQL Developer
very useful. Thanks