Results 1 to 2 of 2
  1. #1
    Join Date
    Dec 2010
    Posts
    123

    Unanswered: db2 server become slow

    Dear all,
    i am using db2 9.1.3 ESE on linux redhat 5.2

    It is taking so much time to connect to db2inst1 user , db2start, to connect to database......

    after connecting to db2inst1 , it displaying some messages like

    setittimer:db2sysc(pid=5580) provided invalid timeval it_value : tv_sec=0 to tv_usec 10000000

    pls find the diaglog


    2011-12-05-15.38.42.414835+330 I6642564G1505 LEVEL: Event
    PID : 5547 TID : 3086842528 PROC : db2start
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130
    DATA #1 : String, 34 bytes
    /home/db2inst1/sqllib/adm/db2star2
    DATA #2 : Hexdump, 256 bytes
    0xBFE5A0F0 : 2F68 6F6D 652F 6462 3269 6E73 7431 2F73 /home/db2inst1/s
    0xBFE5A100 : 716C 6C69 622F 6164 6D2F 6462 3273 7461 qllib/adm/db2sta
    0xBFE5A110 : 7232 004E 4F4D 5347 0000 0000 0000 0000 r2.NOMSG........
    0xBFE5A120 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0xBFE5A130 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0xBFE5A140 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0xBFE5A150 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0xBFE5A160 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0xBFE5A170 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0xBFE5A180 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0xBFE5A190 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0xBFE5A1A0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0xBFE5A1B0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0xBFE5A1C0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0xBFE5A1D0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0xBFE5A1E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

    2011-12-05-15.41.07.136692+330 E6644070G368 LEVEL: Warning
    PID : 5571 TID : 3086646112 PROC : db2syscr
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, DB2main, probe:0
    MESSAGE : ADM0506I DB2 has automatically updated the "kernel.sem" kernel
    parameter from "128" to the recommended value "1024".

    2011-12-05-15.41.07.192686+330 E6644439G370 LEVEL: Warning
    PID : 5571 TID : 3086646112 PROC : db2syscr
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, DB2main, probe:0
    MESSAGE : ADM0506I DB2 has automatically updated the "kernel.msgmni" kernel
    parameter from "16" to the recommended value "1024".

    2011-12-05-15.41.10.523299+330 E6644810G1199 LEVEL: Event
    PID : 5553 TID : 3086621344 PROC : db2star2
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911
    MESSAGE : ADM7513W Database manager has started.
    START : DB2 DBM
    DATA #1 : Build Level, 128 bytes
    Instance "db2inst1" uses "32" bits and DB2 code release "SQL09013"
    with level identifier "01040107".
    Informational tokens are "DB2 v9.1.0.3", "s070719", "MI00202", Fix Pack "3".
    DATA #2 : System Info, 436 bytes
    System: Linux DLF13p2.vspl.in 6 2 i686
    CPU: total:2 online:2 Cores per socket:2 Threading degree per core:1
    Physical Memory(MB): total:3033 free:2717
    Virtual Memory(MB): total:11035 free:10719
    Swap Memory(MB): total:8002 free:8002
    Kernel Params: msgMaxMessageSize:65536 msgMsgMap:65536 msgMaxQueueIDs:1024
    msgNumberOfHeaders:65536 msgMaxQueueSize:65536
    msgMaxSegmentSize:16 shmMax:4294967295 shmMin:1 shmIDs:4096
    shmSegments:4096 semMap:32000 semIDs:1024 semNum:32000
    semUndo:32000 semNumPerID:250 semOps:32 semUndoSize:20
    semMaxVal:32767 semAdjustOnExit:32767

    2011-12-05-15.45.11.514472+330 E6646010G410 LEVEL: Event
    PID : 5607 TID : 3086386880 PROC : db2stmm (DLF12) 0
    INSTANCE: db2inst1 NODE : 000 DB : DLF12
    APPHDL : 0-8 APPID: *LOCAL.DB2.111205101511
    AUTHID : DB2INST1
    FUNCTION: DB2 UDB, Self tuning memory manager, stmmLog, probe:1009
    DATA #1 : <preformatted>
    Starting STMM log from file number 2

    2011-12-05-15.50.39.414185+330 I6646421G434 LEVEL: Event
    PID : 5626 TID : 3086386880 PROC : db2stmm (DLF12) 0
    INSTANCE: db2inst1 NODE : 000 DB : DLF12
    APPHDL : 0-15 APPID: *LOCAL.DB2.111205101739
    AUTHID : DB2INST1
    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20
    CHANGE : STMM CFG DB DLF12: "Sortheap" From: "386" <automatic> To: "387" <automatic>

    2011-12-05-16.07.19.743447+330 I6646856G1505 LEVEL: Event
    PID : 5554 TID : 3085929120 PROC : db2start
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130
    DATA #1 : String, 34 bytes
    /home/db2inst1/sqllib/adm/db2star2
    DATA #2 : Hexdump, 256 bytes
    0xBFC5B7B0 : 2F68 6F6D 652F 6462 3269 6E73 7431 2F73 /home/db2inst1/s
    0xBFC5B7C0 : 716C 6C69 622F 6164 6D2F 6462 3273 7461 qllib/adm/db2sta
    0xBFC5B7D0 : 7232 004E 4F4D 5347 0000 0000 0000 0000 r2.NOMSG........
    0xBFC5B7E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0xBFC5B7F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0xBFC5B800 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0xBFC5B810 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0xBFC5B820 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0xBFC5B830 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0xBFC5B840 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0xBFC5B850 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0xBFC5B860 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0xBFC5B870 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0xBFC5B880 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0xBFC5B890 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0xBFC5B8A0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

    2011-12-05-16.09.46.415592+330 E6648362G368 LEVEL: Warning
    PID : 5579 TID : 3086080864 PROC : db2syscr
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, DB2main, probe:0
    MESSAGE : ADM0506I DB2 has automatically updated the "kernel.sem" kernel
    parameter from "128" to the recommended value "1024".

    2011-12-05-16.09.46.473803+330 E6648731G370 LEVEL: Warning
    PID : 5579 TID : 3086080864 PROC : db2syscr
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, DB2main, probe:0
    MESSAGE : ADM0506I DB2 has automatically updated the "kernel.msgmni" kernel
    parameter from "16" to the recommended value "1024".

    2011-12-05-16.09.49.811974+330 E6649102G1199 LEVEL: Event
    PID : 5561 TID : 3086912160 PROC : db2star2
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911
    MESSAGE : ADM7513W Database manager has started.
    START : DB2 DBM
    DATA #1 : Build Level, 128 bytes
    Instance "db2inst1" uses "32" bits and DB2 code release "SQL09013"
    with level identifier "01040107".
    Informational tokens are "DB2 v9.1.0.3", "s070719", "MI00202", Fix Pack "3".
    DATA #2 : System Info, 436 bytes
    System: Linux DLF13p2.vspl.in 6 2 i686
    CPU: total:2 online:2 Cores per socket:2 Threading degree per core:1
    Physical Memory(MB): total:3033 free:2716
    Virtual Memory(MB): total:11035 free:10718
    Swap Memory(MB): total:8002 free:8002
    Kernel Params: msgMaxMessageSize:65536 msgMsgMap:65536 msgMaxQueueIDs:1024
    msgNumberOfHeaders:65536 msgMaxQueueSize:65536
    msgMaxSegmentSize:16 shmMax:4294967295 shmMin:1 shmIDs:4096
    shmSegments:4096 semMap:32000 semIDs:1024 semNum:32000
    semUndo:32000 semNumPerID:250 semOps:32 semUndoSize:20
    semMaxVal:32767 semAdjustOnExit:32767

    2011-12-05-16.17.13.584014+330 E6650302G412 LEVEL: Event
    PID : 5629 TID : 3086481088 PROC : db2stmm (DLF13) 0
    INSTANCE: db2inst1 NODE : 000 DB : DLF13
    APPHDL : 0-9 APPID: *LOCAL.DB2.111205104713
    AUTHID : DB2INST1
    FUNCTION: DB2 UDB, Self tuning memory manager, stmmLog, probe:1009
    DATA #1 : <preformatted>
    Starting STMM log from file number 2

  2. #2
    Join Date
    Jan 2003
    Posts
    4,292
    Provided Answers: 5
    Is this the first connection to the database that is slow or are all connections slow? Where are the connections coming from?

    Where does this error come from?
    Quote Originally Posted by ravichandrapratap View Post

    setittimer:db2sysc(pid=5580) provided invalid timeval it_value : tv_sec=0 to tv_usec 10000000
    Your db2diag.log excerpt is just normal DB2 start and STMM info.

    Andy

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •