EM SQL Monitor Impact

In case anyone needs a reminder, its always a good idea to determine the impact of your monitoring tools on the very database you are monitoring. Some monitoring tools are lightweight and others are more obtrusive. I am using Enterprise Manager 13c to monitor a specific SQL statement while its running. I noticed in another monitoring tool (Lighty by Orachrome) the following SQL statement was consuming a good amount of resources:

WITH MONITOR_DATA AS (
SELECT
INST_ID
,KEY
,NVL2 (
PX_QCSID
,NULL
,STATUS
) STATUS
,FIRST_REFRESH_TIME
,LAST_REFRESH_TIME
,REFRESH_COUNT
,PROCESS_NAME
,SID
,SQL_ID
,SQL_EXEC_START

 

I cut off the rest of the text. This SQL statement is literally a few thousand lines long. Yikes! But that isn’t the issue.  In Lighty, I noticed the activity in this screen shot.

Its focus is to treat the underlying cause of a variety of super cheap viagra http://frankkrauseautomotive.com/sample-page/ health problems including physical and psychological ones. GET orden viagra viagra REAL, ANY business worth it’s while, will need hard work and dedication, and will take time to develop into something substantial. Here, let us take a look at some of the common proceeds that enlargement supplements target? Every formula is designed to support circulatory health which basically the cost cialis viagra most important thing in erections. For a long time, many patients want to seek an discounts on viagra efficacy and safe way to manage the conditions, because antibiotic therapy only remains the basis of treatment for male impotency. sql_monitor1

 

 

 

The top SQL statement is my CPU pig. I blacked out the SQL text to protect potentially proprietary information. Notice that last SQL statement. It is consuming a fair amount of resources for just monitoring the system.

Here is a screenshot of the EM13c window.

sql_monitor2

 

 

 

When I turned off the Auto Refresh (it defaults to 15 seconds), the activity ceased on the system. I then manually press the refresh button when I need an update.
There are certainly times to use the auto refresh, even every 15 seconds. Just be mindful of the potential negative impact on the database.