Results 1 to 7 of 7
  1. #1
    Join Date
    May 2010
    Location
    Mumbai, India
    Posts
    4

    Unanswered: continuous Hex dump on db2diag.log

    I am getting Hex dump in db2diag.log continuously. Please help. db2level for your information

    DB21085I Instance "txn" uses "64" bits and DB2 code release "SQL08023" with
    level identifier "03040106".
    Informational tokens are "DB2 v8.1.1.96", "s050811", "U803920", and FixPak
    "10".

    --------db2diag.log-----------

    2010-05-22-14.56.19.826493-330 I295367A1073 LEVEL: Error
    PID : 156024 TID : 1 PROC : db2agent (XXX) 0
    INSTANCE: txn NODE : 000 DB : XXX
    APPHDL : 0-70 APPID: YY
    FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
    DATA #1 : Hexdump, 136 bytes
    0x00000001117C0268 : 5351 4C43 4120 2020 0000 0088 FFFF FED3 SQLCA ........
    0x00000001117C0278 : 0002 3130 2020 2020 2020 2020 2020 2020 ..10
    0x00000001117C0288 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x00000001117C0298 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x00000001117C02A8 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x00000001117C02B8 : 2020 2020 2020 2020 5351 4C52 4931 4543 SQLRI1EC
    0x00000001117C02C8 : 801A 006D 0000 0000 0000 0000 0000 0000 ...m............
    0x00000001117C02D8 : FFFF FFB0 0000 0000 2020 2020 2020 2020 ........
    0x00000001117C02E8 : 2020 2030 3730 3036 07006

    2010-05-22-14.56.20.421666-330 I296441A1073 LEVEL: Error
    PID : 524532 TID : 1 PROC : db2agent (XXX) 0
    INSTANCE: txn NODE : 000 DB : XXX
    APPHDL : 0-38 APPID: YY
    FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
    DATA #1 : Hexdump, 136 bytes
    0x00000001117C0268 : 5351 4C43 4120 2020 0000 0088 FFFF FED3 SQLCA ........
    0x00000001117C0278 : 0001 3620 2020 2020 2020 2020 2020 2020 ..6
    0x00000001117C0288 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x00000001117C0298 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x00000001117C02A8 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x00000001117C02B8 : 2020 2020 2020 2020 5351 4C52 4931 4543 SQLRI1EC
    0x00000001117C02C8 : 801A 006D 0000 0000 0000 0000 0000 0000 ...m............
    0x00000001117C02D8 : FFFF FF9C 0000 0000 2020 2020 2020 2020 ........
    0x00000001117C02E8 : 2020 2030 3730 3036 07006

    2010-05-22-14.56.24.585023-330 I297515A1073 LEVEL: Error
    PID : 753848 TID : 1 PROC : db2agent (XXX) 0
    INSTANCE: txn NODE : 000 DB : XXX
    APPHDL : 0-77 APPID: YY
    FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
    DATA #1 : Hexdump, 136 bytes
    0x00000001117C0268 : 5351 4C43 4120 2020 0000 0088 FFFF FED3 SQLCA ........
    0x00000001117C0278 : 0002 3233 2020 2020 2020 2020 2020 2020 ..23
    0x00000001117C0288 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x00000001117C0298 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x00000001117C02A8 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x00000001117C02B8 : 2020 2020 2020 2020 5351 4C52 4931 4543 SQLRI1EC
    0x00000001117C02C8 : 801A 006D 0000 0000 0000 0000 0000 0000 ...m............
    0x00000001117C02D8 : FFFF FF9C 0000 0000 2020 2020 2020 2020 ........
    0x00000001117C02E8 : 2020 2030 3730 3036 07006

    2010-05-22-14.56.25.445372-330 I298589A1073 LEVEL: Error
    PID : 524532 TID : 1 PROC : db2agent (XXX) 0
    INSTANCE: txn NODE : 000 DB : XXX
    APPHDL : 0-38 APPID: YY
    FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
    DATA #1 : Hexdump, 136 bytes
    0x00000001117C0268 : 5351 4C43 4120 2020 0000 0088 FFFF FED3 SQLCA ........
    0x00000001117C0278 : 0002 3435 2020 2020 2020 2020 2020 2020 ..45
    0x00000001117C0288 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x00000001117C0298 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x00000001117C02A8 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x00000001117C02B8 : 2020 2020 2020 2020 5351 4C52 4931 4543 SQLRI1EC
    0x00000001117C02C8 : 801A 006D 0000 0000 0000 0000 0000 0000 ...m............
    0x00000001117C02D8 : FFFF FFB0 0000 0000 2020 2020 2020 2020 ........
    0x00000001117C02E8 : 2020 2030 3730 3036 07006

    2010-05-22-14.56.25.454839-330 I299663A1073 LEVEL: Error
    PID : 524532 TID : 1 PROC : db2agent (XXX) 0
    INSTANCE: txn NODE : 000 DB : XXX
    APPHDL : 0-38 APPID: YY
    FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
    DATA #1 : Hexdump, 136 bytes
    0x00000001117C0268 : 5351 4C43 4120 2020 0000 0088 FFFF FED3 SQLCA ........
    0x00000001117C0278 : 0002 3332 2020 2020 2020 2020 2020 2020 ..32
    0x00000001117C0288 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x00000001117C0298 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x00000001117C02A8 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x00000001117C02B8 : 2020 2020 2020 2020 5351 4C52 4931 4543 SQLRI1EC
    0x00000001117C02C8 : 801A 006D 0000 0000 0000 0000 0000 0000 ...m............
    0x00000001117C02D8 : FFFF FF9C 0000 0000 2020 2020 2020 2020 ........
    0x00000001117C02E8 : 2020 2030 3730 3036 07006

    2010-05-22-14.56.27.814025-330 I300737A1073 LEVEL: Error
    PID : 508254 TID : 1 PROC : db2agent (XXX) 0
    INSTANCE: txn NODE : 000 DB : XXX
    APPHDL : 0-76 APPID: YY
    FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
    DATA #1 : Hexdump, 136 bytes
    0x000000011171F268 : 5351 4C43 4120 2020 0000 0088 FFFF FED3 SQLCA ........
    0x000000011171F278 : 0002 3130 2020 2020 2020 2020 2020 2020 ..10
    0x000000011171F288 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x000000011171F298 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x000000011171F2A8 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x000000011171F2B8 : 2020 2020 2020 2020 5351 4C52 4931 4543 SQLRI1EC
    0x000000011171F2C8 : 801A 006D 0000 0000 0000 0000 0000 0000 ...m............
    0x000000011171F2D8 : FFFF FFB0 0000 0000 2020 2020 2020 2020 ........
    0x000000011171F2E8 : 2020 2030 3730 3036 07006



    Please help to resolve this issue.
    Last edited by arunmurugan; 05-22-10 at 07:00.

  2. #2
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,369
    FFFF FED3 -> sql0301n

    SQL0301N The value of input host variable or parameter number
    "<number>" cannot be used because of its data type.


    Check what the diaglevel is set to. If 4, reduce it to 3.

  3. #3
    Join Date
    May 2010
    Location
    Mumbai, India
    Posts
    4
    Thanks for the reply bella.
    I was getting the below warning two days back.
    Flushed the even monitor buffer using "db2 flush event monitor DB2DETAILDEADLOCK". Also did a update in dbm cfg for diaglevel to 4.
    As the logs generation was heavy, i rollbacked the diaglevel to 3. Those logs which i mentioned earlier are the lastest ones with the diaglevel 3.


    ----db2diag.log warning-------

    2010-05-20-16.38.11.182610-330 I417436069A623 LEVEL: Warning

    PID : 774566 TID : 1 PROC : db2agent (xxx) 0

    INSTANCE: txn NODE : 000 DB : xxx

    APPHDL : 0-45 APPID: yyy

    FUNCTION: DB2 UDB, database monitor, sqm___log_event, probe:41

    DATA #1 : String, 266 bytes

    Dlconn for event monitor DB2DETAILDEADLOCK truncated by 8001895 bytes!

    Deadlock ID: 1 Participant:2 Original locks in list: 32176.

    Redefine the event monitor, increasing the BUFFERSIZE by 1954 pages.

    Increase DIAGLEVEL to 4 to see the truncated Locks in this log.
    Last edited by arunmurugan; 05-22-10 at 13:46.

  4. #4
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,369
    Don't use diaglevel 4. Just drop this event monitor (extract existing info using db2evmon if needed) and create a new deadlock event monitor and specify a larger buffersize. If those FFFFFED3 messages continue, stop the instance, clean-up any remaining processes / ipc resources owned by the instance id and restart the instance. They should not really be logged with diaglevel 3, even though it says Error.

  5. #5
    Join Date
    May 2010
    Location
    Mumbai, India
    Posts
    4
    You are right Bella.

    After restart, there are no FFFFFED3 messages now. But iam getting those event monitor warning messages again.
    Dropping event monitor, you mean to say to make it inactive or completely remove?
    I am not able to see the event monitor thro' db2 control center. But i can see a row in SYSCAT.EVENTMONITORS.
    Please guide to proceed futher.

  6. #6
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,369
    I'm not sure why you don't see it in the CC. What you need to do is to drop db2detaildeadlock event monitor (extract info first if needed) and then create a new one (specify a larger buffer size). Take a look at this technote for some additional info:
    IBM - Default deadlock event monitor

  7. #7
    Join Date
    May 2010
    Location
    Mumbai, India
    Posts
    4
    Thanks a lot Bella. It worked.

Tags for this Thread

Posting Permissions

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