Why is the Apptune current interval missing after DB2 subsystem termination?

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    APPTUNE for DB2


    COMPONENT:

    APPTUNE for DB2


    APPLIES TO:

    BMC Performance for SQL, SQL Performance for DB2



    QUESTION:

    Why is the Apptune current interval missing after DB2 subsystem termination?

    ASQEQRTN/I VIEW A REPORT  
    COMMAND ====> _______________________________________________ SCROLL ===> CSR_ 
    BMCSftwr.SQMINTVD -- SELECT ANALYSIS INTERVAL -- 05/17 15:50:07 
    SELECT A SINGLE INTERVAL OR A RANGE OF INTERVALS. TYPE "S" BESIDE A SINGLE 
    INTERVAL OR BESIDE THE FIRST AND LAST INTERVALS IN THE RANGE, AND PRESS 
    ENTER. EXIT WHEN FINISHED. 

    ACTIONS: F-FILTERING CRITERIA 
    +------------------- INTERVAL -----------------+ NUMBER ACTIVE 
    BEGIN END DURATION DB2 ENTRIES FILTER 
    ------------------ ------------------ -------- ---- ------- -------- 
    + 05/17/16 15:31:59 05/17/16 15:50:06 00:18:08 DEGQ 4 !BMCTEST  <<<<<<
    Current interval 
    + 05/17/16 12:53:59 05/17/16 15:26:59 02:33:00 DEGQ 2 !BMCTEST 
    + 05/17/16 00:00:00 05/17/16 12:51:59 12:51:59 DEGQ 0 !BMCTEST 


    ANSWER:

     

    Apptune data is maintained in DBM1 storage and is designed to not hold up DB2 termination. When DB2 terminates normally or abnormally, the DBM1 storage is released and the current interval is not written to the NGL log files.

    Interval data is summarized in an internal reduction table. At the end of the interval, the summarized data is written to NGL log files. The following types of data are categorized as interval data:
    Interval data (BMC IFCID 006)
    Filter data (BMC IFCID 318)
    Statement object data (BMC IFCID 008)
    Accessed objects data (BMC IFCID 009)
    Statement summaries (BMC IFCIDs 307-310)

    Event data is written immediately to the NGL log files. The following types of data are categorized as event data:
    Statement text data (BMC IFCID 005)
    SQL error data (BMC IFCID 007)
    Exception data (BMC IFCID 004)
    Host variable data (BMC IFCID 010)
    Exception object data (BMC IFCID 011)

     

      

    It is recommended that prior to stopping DB2, enter command APPOFF or APPRESET to unload the data in the reduction table to save the current interval for the DB2. Enter APPON to start data collection after data collection has been stopped by an APPOFF command. APPOFF stops the data collection and avoids the possibility of any event data that may be captured that does not belong to any interval in the case of APPRESET command. Not issuing an APPOFF prior to stopping DB2 should not prevent automatic restart of Apptune monitoring. 

    In case of DB2 abnormal termination, the current interval is lost.

     


    Article Number:

    000250894


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles