Db2 (On Premises and Cloud)

Expand all | Collapse all

DMC 3.1.5 How to find the culprit application of transaction log full on database from historical/current data

  • 1.  DMC 3.1.5 How to find the culprit application of transaction log full on database from historical/current data

    Posted Tue July 13, 2021 02:12 AM
    There are few occurrences of transaction log full on database caused by application query but we unable to find the same in either current or historical data from the DMC. How to get this data i.e. which monitoring element does show this? 

    Example:

    We found following entry in diag.log however there is no such application id reported in DMC application/connection monitoring data. 

    2021-07-13-05.27.44.308230+000 I3679371E668 LEVEL: Error
    PID : 7698 TID : 139815618078464 PROC : db2sysc 0
    INSTANCE: db2psin1 NODE : 000 DB : DBNVMPOC
    APPHDL : 0-3656 APPID: 10.160.100.232.46562.210713052707
    UOWID : 3758 ACTID: 1
    AUTHID : DBOVN1D HOSTNAME: sl73psdbmbd03.visa.com
    EDUID : 2215 EDUNAME: db2agent (DBNVMPOC) 0
    FUNCTION: DB2 UDB, data protection services, sqlpWriteLR, probe:6680
    MESSAGE : ZRC=0x85100009=-2062548983=SQLP_NOSPACE
    "Log File has reached its saturation point"
    DIA8309C Log file was full.

    2021-07-13-05.27.44.305354+000 E3680040E707 LEVEL: Error
    PID : 7698 TID : 139833510979328 PROC : db2sysc 0
    INSTANCE: db2psin1 NODE : 000 DB : DBNVMPOC
    APPHDL : 0-3854 APPID: 10.160.100.232.46966.210713052702
    UOWID : 3350 ACTID: 1
    AUTHID : DBOVN1D HOSTNAME: sl73psdbmbd03.visa.com
    EDUID : 2413 EDUNAME: db2agent (DBNVMPOC) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgResSpace, probe:7869
    MESSAGE : ADM1823E The active log is full and is held by application handle
    "0-2101". Terminate this application by COMMIT, ROLLBACK or FORCE
    APPLICATION.



    ------------------------------
    Krishna Murakonda
    ------------------------------


  • 2.  RE: DMC 3.1.5 How to find the culprit application of transaction log full on database from historical/current data

    Posted Sat August 14, 2021 07:32 PM
    MESSAGE : ADM1823E The active log is full and is held by application handle 
    "0-2101".

    It's telling you the application handle holding the oldest transaction.  in this case the log was hold by app handle 2101. 

    Go back to historical mode, before this timestamp 2021-07-13-05.27.44.305354 under Application / Connections  and try to find the connection for this handle.  


    ------------------------------
    Samuel Pizarro
    ------------------------------