Db2 (On Premises and Cloud)

Expand all | Collapse all

Statistics event monitor

  • 1.  Statistics event monitor

    Posted 10 days ago
    Hello DMC Team,

    with the new version Build: 20200121-103505 Version: 3.1.1.0

    every five minutes I got a db2diag log entry in each monitored system:
    2020-01-28-13.21.54.731290+060 I92648523A738        LEVEL: Error
    PID     : 14680336             TID : 16391          PROC : db2sysc 0
    INSTANCE: db2bet               NODE : 000           DB   : BET
    APPHDL  : 0-12080              APPID: xxx.xxx.xxx.xxx.200128122154
    UOWID   : 6                    ACTID: 1
    AUTHID  : DB2BET               HOSTNAME: xxxxxx
    EDUID   : 16391                EDUNAME: db2agent (BET) 0
    FUNCTION: DB2 UDB, database monitor, sqm_evmon_mgr::set_evmon_active, probe:20
    MESSAGE : ZRC=0x800D0029=-2146631639=SQLM_RC_EVNSET "evmon not set"
              DIA8050E Event monitor already active or inactive.
    CALLED  : DB2 UDB, database monitor, sqm_evmon_mgr::start_evmon
    DATA #1 : String with size, 17 bytes
    RTMON_EVMON_STATS
    ​

    Do you know how can I avoid that these messages flooding the db2diag.log?

    For the same time the db2diag.log file form the DMC repository show these messges:
    2020-01-28-13.26.09.873334+060 E6444877E556          LEVEL: Error
    PID     : 25000                TID : 139710932444928 PROC : db2sysc 0
    INSTANCE: db2dmc               NODE : 000            DB   : DMC
    APPHDL  : 0-49162              APPID: xxx.xxx.xxx.xxx.50648.200128122603
    UOWID   : 31                   ACTID: 1
    AUTHID  : DB2DMC               HOSTNAME: xxxxxx
    EDUID   : 80                   EDUNAME: db2agent (DMC) 0
    FUNCTION: DB2 UDB, database monitor, sqmSqlTarget::readSystables, probe:20
    MESSAGE : ADM2016W  The table "WLSTATS" (ID "0") was not found.
    
    2020-01-28-13.26.09.874089+060 I6445434E727          LEVEL: Warning
    PID     : 25000                TID : 139710932444928 PROC : db2sysc 0
    INSTANCE: db2dmc               NODE : 000            DB   : DMC
    APPHDL  : 0-49162              APPID: xxx.xxx.xxx.xxx.50648.200128122603
    UOWID   : 31                   ACTID: 1
    AUTHID  : DB2DMC               HOSTNAME: xxxxxx
    EDUID   : 80                   EDUNAME: db2agent (DMC) 0
    FUNCTION: DB2 UDB, database monitor, sqmSqlTarget::readSystables, probe:20
    MESSAGE : ZRC=0x800D014C=-2146631348=SQLM_RC_NOTAB "table not found"
    DATA #1 : String, 135 bytes
    Event Monitor Name: RTMON_EVMON_STATS;
    TableName: WLSTATS;
    The table is not found, and corresponding event type will not be recorded!​


    Best regards,
    Joachim

    ------------------------------
    Joachim Müller
    ------------------------------


  • 2.  RE: Statistics event monitor

    Posted 10 days ago
    Hi Joachim,

    In each data collection point (5 mins by default), DMC will disable event monitor RTMON_EVMON_STATS firstly, and then move the data from the monitored database to repository database, finally RTMON_EVMON_STATS will be enabled again.Does your statistics event monitor function work properly? If yes, would you please ignore such logs? We will look into and improve duplication actions if there is any.

    For the repository database log, did you add your repository database as one of the monitored connection? Would you please check the monitor profile setting towards the connection? If you don't used statistics event monitor, would you please disable it in monitor profile?

    Thanks!

    ------------------------------
    XIAO MIN ZHAO
    ------------------------------



  • 3.  RE: Statistics event monitor

    Posted 10 days ago
    Hello XIAO MIN ZHAO,

    Added a new database for monitoring within DMC and found that I have also the same behavior as described above.
    Do you find together with your development team the root cause for this messages?

    Best regards,
    Joachim


    ------------------------------
    Joachim Müller
    ------------------------------



  • 4.  RE: Statistics event monitor

    Posted 10 days ago
    Edited by Jessica Long 10 days ago
    Hi Joachim,

    We've exposed the root cause for the issue, and already delivered an improvement fix for it. For now, if statistics event monitor works properly, would you please ignore this kind of log in db2diag? Thanks for your feedback!

    ------------------------------
    XIAO MIN ZHAO
    ------------------------------