Hello DMC-Team,
I'm getting confused by the display of the event monitor status in DMC in context with blackout.
While testing the blackout feature I came across a couple of scenarios where the DMC console displays inconsistent information about event monitor status, which is not in line with what I see in DB2 with respect to the status of the event monitors either.
I'm testing on SLES15, DMC 3.1.8.0 Enterprise Build: 20220617-034828, DB2 V11.5 repository DB and DB2 V10.5.9 monitored database.
Scenario 1:
While having set an active full_blackout or monitor_and_alert_blackout on a connection profile the Event Monitor Profile screen shows the various event monitors as <Enabled> but in a greyed out fashion, i.e. as de-activated. For instance:
At the very same time I still see the event monitors in the DB2 monitored database in status <active>:
SELECT SUBSTR(EVMONNAME,1,30), CASE WHEN EVENT_MON_STATE(EVMONNAME) = 0 THEN 'INACTIVE' WHEN EVENT_MON_STATE(EVMONNAME) = 1 THEN 'ACTIVE' END AS STATE FROM SYSCAT.EVENTMONITORS
EVMON STATE
------------------------------ --------
RTMON_EVMON_ACTIVITIES_1662035 ACTIVE
RTMON_EVMON_LOCKING ACTIVE
RTMON_EVMON_STATS ACTIVE
RTMON_EVMON_UTILITY ACTIVE
I would have expected that the event monitors get de-activated during the process of blackout window activation, i.e. short before disconnecting the connection profile from the target database.
When running e.g. a RUNSTATS in the monitored database during the blackout period its statistics get still captured to the IBM_RTMON.UTIL_START table.
Scenario 2:
Another confusing situation I frequently see after releasing a full_blackout or monitor_and_alert_blackout is that for instance the locking event monitor does not come up properly or its status is not displayed correctly.
On Event Monitor Profile screen the Locking event monitor is enabled and displayed in green:
But when listing the event monitor status on the summary screen, the Locking event monitor is still shown as disabled:
When creating a lockwait in the monitored database the lockwait does not get displayed in DMC Locking metrics, but it is visible in the SYSIBMADM.MON_LOCKWAITS view.
In the monitored database I can see the following event monitor status:
SELECT SUBSTR(EVMONNAME,1,30) AS EVMON, CASE WHEN EVENT_MON_STATE(EVMONNAME) = 0 THEN 'INACTIVE' WHEN EVENT_MON_STATE(EVMONNAME) = 1 THEN 'ACTIVE' END AS STATE FROM SYSCAT.EVENTMONITORS
EVMON STATE
------------------------------ --------
RTMON_EVMON_ACTIVITIES_1662035 ACTIVE
RTMON_EVMON_LOCKING INACTIVE
RTMON_EVMON_STATS ACTIVE
RTMON_EVMON_UTILITY ACTIVE
So to me it looks as if the Locking event monitor is actually disabled, although shown as enabled in DMC.
The only way I can remediate the situation is by disable/re-enable the Locking event monitor on the monitoring configuration screen in DMC. Simply logout from /login into the DMC web console does not help fixing the conflicting displays.
Scenario 3:
Another question I have is about the difference in scope between full_blackout and monitor_and_alert_blackout.
Why gets the connection profile in a monitor_and_alert_blackout disconnected and also reported as disconnected on the dashboard?
I would have expected that with this type of blackout the database is simply not monitored and reported as such, but not disconnected. See the example below. Connection profile OV_TEST_GARTRP is in a monitor_and_alert_blackout state, the Panier_PNR00_yval connection profile is in a full_blackout state. Both are counted under <Disconnected>.
Thanks for your feedback in advance
Best regards - Matthias
------------------------------
Matthias Gärtner-Schür
DBA
------------------------------
#Db2