11 Replies Latest reply: Aug 7, 2009 4:51 PM by Jörg Müller-Herrmann RSS

fast growing db2diag.log (FP4 V9.5)

Jörg Müller-Herrmann
Currently Being Moderated

Does anyone have experiences with V9.5 FP4SAP?

We have implemented this FP4 last week (from FP2a). Since this a db2diag.log of about 1MB were written (and the system usage is really low).

We have another system on FP2a which is used heavier (as a productive system) and the db2diag.log is about 2,5 MB within two months.

We have checked SAP note 1086130 for DB parameters and did not find a required change (from FP2a to FP4).

Any idea is welcome!

Best regards.

  • Re: fast growing db2diag.log (FP4 V9.5)
    Markus Doehr
    Currently Being Moderated

    Did you have a look what is being logged?

     

     

     

    Markus

  • Re: fast growing db2diag.log (FP4 V9.5)
    Jörg Müller-Herrmann
    Currently Being Moderated

    db2diag.log extract 2009-08-02 23:00-23:59

     

    2009-08-02-23.24.20.577179+120 I1019336A362       LEVEL: Warning

    PID     : 602270               TID  : 4114        PROC : db2sysc 0

    INSTANCE: db2mes               NODE : 000

    EDUID   : 4114                 EDUNAME: db2logmgr (MES) 0

    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108

    MESSAGE : Started archive for log file S0001678.LOG.

     

    2009-08-02-23.24.21.914535+120 I1019699A422       LEVEL: Warning

    PID     : 602270               TID  : 4114        PROC : db2sysc 0

    INSTANCE: db2mes               NODE : 000

    EDUID   : 4114                 EDUNAME: db2logmgr (MES) 0

    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180

    MESSAGE : Completed archive for log file S0001678.LOG to TSM chain 0 from

              /db2/MES/log_dir/NODE0000/.

     

    2009-08-02-23.28.53.621596+120 I1020122A483       LEVEL: Event

    PID     : 602270               TID  : 3342        PROC : db2sysc 0

    INSTANCE: db2mes               NODE : 000         DB   : MES

    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318

    AUTHID  : MESADM 

    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0

    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20

    CHANGE  : STMM CFG DB MES: "Locklist" From: "3712" <automatic>  To: "3552" <automatic>

     

    2009-08-02-23.28.53.627724+120 I1020606A545       LEVEL: Event

    PID     : 602270               TID  : 3342        PROC : db2sysc 0

    INSTANCE: db2mes               NODE : 000         DB   : MES

    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318

    AUTHID  : MESADM 

    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0

    FUNCTION: DB2 UDB, access plan manager, sqlra_resize_pckcache, probe:150

    CHANGE  : APM : Package Cache : FROM "5208760" : TO "4191641" : success

    IMPACT  : None

    DATA #1 : String, 29 bytes

    Package Cache Resized (bytes)

     

    2009-08-02-23.28.53.629400+120 I1021152A485       LEVEL: Event

    PID     : 602270               TID  : 3342        PROC : db2sysc 0

    INSTANCE: db2mes               NODE : 000         DB   : MES

    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318

    AUTHID  : MESADM 

    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0

    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20

    CHANGE  : STMM CFG DB MES: "Pckcachesz" From: "1311" <automatic>  To: "1055" <automatic>

     

    2009-08-02-23.28.54.510395+120 I1021638A507       LEVEL: Info

    PID     : 602270               TID  : 3342        PROC : db2sysc 0

    INSTANCE: db2mes               NODE : 000         DB   : MES

    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318

    AUTHID  : MESADM 

    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0

    FUNCTION: DB2 UDB, buffer pool services, sqlbAlterBufferPoolAct, probe:90

    MESSAGE : Altering bufferpool "IBMDEFAULTBP" From: "19552" <automatic> To:

              "15648" <automatic>

     

    2009-08-02-23.29.24.543188+120 I1022146A494       LEVEL: Event

    PID     : 602270               TID  : 3342        PROC : db2sysc 0

    INSTANCE: db2mes               NODE : 000         DB   : MES

    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318

    AUTHID  : MESADM 

    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0

    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20

    CHANGE  : STMM CFG DB MES: "Database_memory" From: "205060" <automatic>  To: "185520" <automatic>

     

    2009-08-02-23.29.54.555357+120 I1022641A483       LEVEL: Event

    PID     : 602270               TID  : 3342        PROC : db2sysc 0

    INSTANCE: db2mes               NODE : 000         DB   : MES

    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318

    AUTHID  : MESADM 

    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0

    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20

    CHANGE  : STMM CFG DB MES: "Locklist" From: "3552" <automatic>  To: "3392" <automatic>

     

    2009-08-02-23.29.54.559234+120 I1023125A545       LEVEL: Event

    PID     : 602270               TID  : 3342        PROC : db2sysc 0

    INSTANCE: db2mes               NODE : 000         DB   : MES

    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318

    AUTHID  : MESADM 

    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0

    FUNCTION: DB2 UDB, access plan manager, sqlra_resize_pckcache, probe:150

    CHANGE  : APM : Package Cache : FROM "4191641" : TO "3937361" : success

    IMPACT  : None

    DATA #1 : String, 29 bytes

    Package Cache Resized (bytes)

     

    2009-08-02-23.29.54.560050+120 I1023671A484       LEVEL: Event

    PID     : 602270               TID  : 3342        PROC : db2sysc 0

    INSTANCE: db2mes               NODE : 000         DB   : MES

    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318

    AUTHID  : MESADM 

    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0

    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20

    CHANGE  : STMM CFG DB MES: "Pckcachesz" From: "1055" <automatic>  To: "991" <automatic>

     

    2009-08-02-23.29.55.097984+120 I1024156A507       LEVEL: Info

    PID     : 602270               TID  : 3342        PROC : db2sysc 0

    INSTANCE: db2mes               NODE : 000         DB   : MES

    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318

    AUTHID  : MESADM 

    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0

    FUNCTION: DB2 UDB, buffer pool services, sqlbAlterBufferPoolAct, probe:90

    MESSAGE : Altering bufferpool "IBMDEFAULTBP" From: "15648" <automatic> To:

              "13914" <automatic>

     

    2009-08-02-23.30.25.137828+120 I1024664A494       LEVEL: Event

    PID     : 602270               TID  : 3342        PROC : db2sysc 0

    INSTANCE: db2mes               NODE : 000         DB   : MES

    APPHDL  : 0-8                  APPID: *LOCAL.DB2.090729131318

    AUTHID  : MESADM 

    EDUID   : 3342                 EDUNAME: db2stmm (MES) 0

    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20

    CHANGE  : STMM CFG DB MES: "Database_memory" From: "185520" <automatic>  To: "176480" <automatic>

     

    2009-08-02-23.41.12.098793+120 I1025159A362       LEVEL: Warning

    PID     : 602270               TID  : 4114        PROC : db2sysc 0

    INSTANCE: db2mes               NODE : 000

    EDUID   : 4114                 EDUNAME: db2logmgr (MES) 0

    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108

    MESSAGE : Started archive for log file S0001679.LOG.

     

    2009-08-02-23.41.13.334331+120 I1025522A422       LEVEL: Warning

    PID     : 602270               TID  : 4114        PROC : db2sysc 0

    INSTANCE: db2mes               NODE : 000

    EDUID   : 4114                 EDUNAME: db2logmgr (MES) 0

    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180

    MESSAGE : Completed archive for log file S0001679.LOG to TSM chain 0 from

              /db2/MES/log_dir/NODE0000/.

  • Re: fast growing db2diag.log (FP4 V9.5)
    Jörg Müller-Herrmann
    Currently Being Moderated

    yes, STMM were activated with FP2a too

  • Re: fast growing db2diag.log (FP4 V9.5)
    Jörg Müller-Herrmann
    Currently Being Moderated

    This maybe more readable:

    2009-07-30-16.13.26.330086+120 E336507A564        LEVEL: Warning

    PID     : 602270               TID  : 20048       PROC : db2sysc 0

    INSTANCE: db2mes               NODE : 000         DB   : MES

    APPHDL  : 0-1882               APPID: *LOCAL.db2mes.090730141316

    AUTHID  : DB2MES 

    EDUID   : 20048                EDUNAME: db2agent (MES) 0

    FUNCTION: DB2 UDB, lock manager, sqlpRefillAgentLRBCache, probe:1000

    DATA #1 : <preformatted>

    Locklist has synchronously grown into overflow memory to avoid lock escalation.

    Previous locklist size: 608

    Current locklist size: 736

     

    2009-07-30-16.13.26.847280+120 E337072A552        LEVEL: Warning

    PID     : 602270               TID  : 20048       PROC : db2sysc 0

    INSTANCE: db2mes               NODE : 000         DB   : MES

    APPHDL  : 0-1882               APPID: *LOCAL.db2mes.090730141316

    AUTHID  : DB2MES 

    EDUID   : 20048                EDUNAME: db2agent (MES) 0

    FUNCTION: DB2 UDB, lock manager, sqlpCheckAndDecreaseLocklistOverflowUsag, probe:80

    DATA #1 : <preformatted>

    Locklist overflow reduced.

    Previous locklist size: 2400   New locklist size: 448

    Pages still in overflow: 0

     

    2009-07-30-16.13.27.005082+120 E337625A564        LEVEL: Warning

    PID     : 602270               TID  : 20048       PROC : db2sysc 0

    INSTANCE: db2mes               NODE : 000         DB   : MES

    APPHDL  : 0-1882               APPID: *LOCAL.db2mes.090730141316

    AUTHID  : DB2MES 

    EDUID   : 20048                EDUNAME: db2agent (MES) 0

    FUNCTION: DB2 UDB, lock manager, sqlpRefillAgentLRBCache, probe:1000

    DATA #1 : <preformatted>

    Locklist has synchronously grown into overflow memory to avoid lock escalation.

    Previous locklist size: 576

    Current locklist size: 704

     

    2009-07-30-16.13.27.612172+120 E338190A552        LEVEL: Warning

    PID     : 602270               TID  : 20048       PROC : db2sysc 0

    INSTANCE: db2mes               NODE : 000         DB   : MES

    APPHDL  : 0-1882               APPID: *LOCAL.db2mes.090730141316

    AUTHID  : DB2MES 

    EDUID   : 20048                EDUNAME: db2agent (MES) 0

    FUNCTION: DB2 UDB, lock manager, sqlpCheckAndDecreaseLocklistOverflowUsag, probe:80

    DATA #1 : <preformatted>

    Locklist overflow reduced.

    Previous locklist size: 2496   New locklist size: 448

    Pages still in overflow: 0

  • Re: fast growing db2diag.log (FP4 V9.5)
    Jens Ullmann
    Currently Being Moderated

    Hello Adam,

    do you know how to get it solved earlier - as v95fp5 will be released by SAP not before Oct-09 (?).

    Will SAP provide (release) this APAR too or a special build of FP4 (only on customer request)?

     

    And where can I find more information about IZ50728? Currently I could not get any information from the SAP Marketplac or the IBM web or a search in the Web.

    Best regards!

    • Re: fast growing db2diag.log (FP4 V9.5)
      Adam Wilson
      Currently Being Moderated

      Hello Jörg,

       

      If you require a special build you will need to open a customer message with SAP. SAP Support will open a PMr to request the special build.

       

      A workaround would be to archive the db2diag.log on a regular basis.

      You can archive the db2diag.log using the db2diag tool. You can specify the -A or -archive  option:

       

      http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=/com.ibm.db2.luw.admin.cmd.doc/doc/r0011728.html

       

      -A | -archive dirName

       

      Archives a diagnostic log file. When this option is specified, all other options are ignored. If one or more file names are specified, each file is processed individually. A timestamp, in the format YYYY-MM-DD-hh.mm.ss, is appended to the file name.

      You can specify the name of the file and directory where it is to be archived. If the directory is not specified, the file is archived in the directory where the file is located and the directory name is extracted from the file name.

      If you specify a directory but no file name, the current directory is searched for the db2diag.log file. If found, the file will be archived in the specified directory. If the file is not found, the directory specified by the DIAGPATH configuration parameter is searched for the db2diag.log file. If found, it is archived in the directory specified.

       

      If you do not specify a file or a directory, the current directory is searched for the db2diag.log file. If found, it is archived in the current directory. If the file is not found, the directory specified by the DIAGPATH configuration parameter is searched for the db2diag.log file. If found, it is archived in the directory specified by the DIAGPATH configuration parameter.

       

      Regards,

      Adam Wilson

      SAP development Support

       

  • Re: fast growing db2diag.log (FP4 V9.5)
    Jörg Müller-Herrmann
    Currently Being Moderated

    Hello Adam,

    thanks for the update. The known db2diag -archive is not the best solution, but maybe ok.

    Let's wait until the reply from SAP (the ticket is open since a few days). SAP is starting a performance analyse.

    Kind regards!

Actions