Db2

 View Only
Expand all | Collapse all

Performance problems due to DB2 automatic tasks such as REORG RECOMPRESS daemon

  • 1.  Performance problems due to DB2 automatic tasks such as REORG RECOMPRESS daemon

    Posted yesterday

    Hello, 

    There may be performance problems when executing automatic DB2 tasks such as REORG RECOMPRESS daemon. Users report slowness in the application and I see the following message in the log and I see that the databases are restarted. Is this due to these maintenance tasks? is it normal? And how can I ensure that these tasks do not affect the daily processes?


    FUNCTION: DB2 UDB, base sys utilities, sqleCompDaemon, probe:256
    DATA #1 : String, 279 bytes
    REORG RECOMPRESS: Ending compression daemon.  Data items:
    (2) checkForForceInterrupts
    (3) agentForced
    (4) dbStateMap
    (5) compDaemonWakeupIntervalTime (milliseconds)
    (6) compDaemonTCBScanListInterval (seconds)
    (7) mMaxNumAutoGroomJobs
    (8) lastTCBScanTime
    (9) totalNumAutoGroomJobs
    DATA #2 : Boolean, 1 bytes
    true
    DATA #3 : Boolean, 1 bytes
    true
    DATA #4 : Hex integer, 4 bytes
    0x00000941
    DATA #5 : Time in milliseconds, PD_TYPE_CDE_TIME_MILLIS, 8 bytes
    10000
    DATA #6 : unsigned integer, 4 bytes
    120
    DATA #7 : unsigned integer, 8 bytes
    8
    DATA #8 : sqlo_datetime timestamp, PD_TYPE_SQLO_DATETIME, 12 bytes
    2025-02-13-08.33.49
    DATA #9 : unsigned integer, 8 bytes
    0


    DUID   : 8005                 EDUNAME: db2loggr () 0
    FUNCTION: DB2 UDB, data protection services, sqpLoggrEdu::sqlpghck, probe:2988
    DATA #1 : <preformatted>
    Hard checkpoint during shutdown.

    List of transactions (logStreamId : tid : state : {firstLfs/firstLsn/firstLso})
    ===============================================================================
    0 : 0000000038C55F8F : SQLP_TPREP : {0/00000002E97D5369/3729120577211}
    0 : 0000000038C55FCC : SQLP_TPREP : {0/00000002E97DA168/3729123903667}
    0 : 0000000038C5693E : SQLP_TPREP : {0/00000002E989207B/3729243167508}
    0 : 0000000038C56AF5 : SQLP_TPREP : {0/00000002E98AD2B6/3729260943645}
    0 : 0000000038C56D40 : SQLP_TPREP : {0/00000002E98D6B2C/3729287890931}
    0 : 0000000038C574E5 : SQLP_TPREP : {0/00000002E994D1E6/3729366468634}
    0 : 0000000038C59376 : SQLP_TPREP : {0/00000002E9B2553D/3729674303236}
    0 : 0000000038C5943F : SQLP_TPREP : {0/00000002E9B339EC/3729683632450}
    0 : 0000000038C596DA : SQLP_TPREP : {0/00000002E9B67AC8/3729717469332}
    0 : 0000000038C5976E : SQLP_TPREP : {0/00000002E9B7E5D1/3729732424322}
    0 : 0000000038C59848 : SQLP_TPREP : {0/00000002E9B83376/3729735710613}
    0 : 0000000038C59C2A : SQLP_TPREP : {0/00000002E9BD1DD5/3729787162265}





    ------------------------------
    Paola MARTINEZ VELASQUEZ
    ------------------------------


  • 2.  RE: Performance problems due to DB2 automatic tasks such as REORG RECOMPRESS daemon

    Posted 7 hours ago
    Edited by Gerhard Paulus 7 hours ago

    Hello Paola,

    this message "REORG RECOMPRESS" does not indicate that an AUTOMATIC REORG is currently running.

    It indicates that the database is shutting down. So when you see this message very often then I assume the database was not explicitly activated but with implicit connect. This could explain the slow performance in the application.

    Just issue the following command after Db2 instance restart "ACTIVATE DATABASE <dbname>" to ensure the database is always up and running and not shutting down after the last connection disconnects.

    db2 "ACTIVATE DATABASE <dbname>"

    Best regards,
    Gerhard



    ------------------------------
    Gerhard Paulus
    Senior Consultant
    mip GmbH
    München
    ------------------------------