Db2

 View Only
Expand all | Collapse all

IBM DMC 3.1.7.1 causing huge number of zrc -2146435004 errors in db2diag.log

  • 1.  IBM DMC 3.1.7.1 causing huge number of zrc -2146435004 errors in db2diag.log

    Posted Mon November 13, 2023 09:39 AM

    Hello,

    we are noticing a huge number of the following errors in db2diag.log:

    2023-11-11-11.12.50.211601+060 I9005307A559         LEVEL: Error
    PID     : 47515394             TID : 537143         PROC : db2sysc 0
    INSTANCE: inst1             NODE : 000           DB   : DB1P
    APPHDL  : 0-25027              APPID: xxx.xxx.xxx.233.59028.231227040444
    UOWID   : 20                   ACTID: 1
    AUTHID  : OPTIM                HOSTNAME: xyz
    EDUID   : 537143               EDUNAME: db2agent (DCPG201P) 0
    FUNCTION: DB2 UDB, catalog services, sqlrlAdminGetIndexInfo, probe:2428
    DATA #1 : signed integer, 4 bytes
    -2146435004

    2023-11-11-11.12.50.212239+060 I9005867A1280        LEVEL: Error
    PID     : 47515394             TID : 537143         PROC : db2sysc 0
    INSTANCE: inst1               NODE : 000           DB   : DB1P
    APPHDL  : 0-25027              APPID: xxx.xxx.xxx.233.59028.231227040444
    UOWID   : 20                   ACTID: 1
    AUTHID  : OPTIM                HOSTNAME: xyz
    EDUID   : 537143               EDUNAME: db2agent (DCPG201P) 0
    FUNCTION: DB2 UDB, catalog services, sqlrlAdminGetIndexInfo, probe:2665
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    0x0A000001D7BF3688 : 0000 0000 0000 0000 0000 0000 FFFF FC71    ...............q
    0x0A000001D7BF3698 : 0002 3638 0000 0000 0000 0000 0000 0000    ..68............
    0x0A000001D7BF36A8 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x0A000001D7BF36B8 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x0A000001D7BF36C8 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x0A000001D7BF36D8 : 0000 0000 0000 0000 7371 6C72 6C41 646D    ........sqlrlAdm
    0x0A000001D7BF36E8 : 8010 0044 0000 0044 0000 0000 0000 0000    ...D...D........
    0x0A000001D7BF36F8 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x0A000001D7BF3708 : 0000 0000 0000 0000                        ........

    db2diag -rc -2146435004 reports "LockTimeOut - tran rollback Reason code 68"

    They are caused by IBM DMC, there is a way to avoid them ?

    We are using IBM DMC version 3.1.7.1 and cannot upgrade it at the moment due to the AUTHENTICATION = DATA_ENCRYPT.

    Thanks in advance.

    Ciao. Roberto.



    ------------------------------
    Roberto Stradella
    ------------------------------



  • 2.  RE: IBM DMC 3.1.7.1 causing huge number of zrc -2146435004 errors in db2diag.log

    Posted Mon November 13, 2023 10:00 AM

    Hello Roberto,

    I have found an old case with a similar issue:

    1. This db2diag error is probably caused by the locking of the table. When console tries to collect monitoring metrics on this table, the locking causes the conflict, that's why there are some errors in db2diag. However, console itself may still work properly. 

    2. The index storage monitoring KPI is added in DMC 3.1.7 (sqlrlAdminGetIndexInfo).

    For that particular case, the customer was running an offline reorgs on the monitored database tables causing the locking.

    After DMC V3.1.9, we do have an option in DMC to either stop the index storage KPI collection, or schedule the collection for a specif time when the database is not too busy.

    If you can not migrate, my recommendation is to find what is the process that is causing the conflict with DMC, and disable DMC during that process using the Blackout Event.

    I hope that helps!



    ------------------------------
    Cintia Ogura
    ------------------------------

    Original Message