Results 1 to 7 of 7
  1. #1
    Join Date
    Feb 2004
    Posts
    37

    Unanswered: db2diag.log messages ...

    hi all,

    i get these messages in db2diag.log ( diag-level 4, db2 8.1 on Linux )

    can anybody tell me what this means?

    thanks

    bab



    2004-03-19-10.24.37.241184 Instance:db2inst1 Node:000
    PID:16045(db2agent (BAISJDB)) TID:16384 Appid:AC10007F.G6EF.00FB623DF70E
    DRDA Communication Manager sqljcReceive Probe:30 Database:BAISJDB

    CCI Error:
    0xBFFF8380 : 0x00000036 6...

    2004-03-19-10.24.40.344244 Instance:db2inst1 Node:000
    PID:16045(db2agent (BAISJDB)) TID:16384 Appid:AC10007F.G6EF.00FB623DF70E
    DRDA Communication Manager sqljcReceive Probe:30 Database:BAISJDB

    DIA0001E An internal error occurred. Report the following error code :
    "ZRC=0x81360012".

  2. #2
    Join Date
    Aug 2003
    Posts
    68
    those are very generic messages - common when the diagnostic level is set to 4.

    I usually set the diagnostic level to 3 to rid myself of these messages.

  3. #3
    Join Date
    Apr 2007
    Posts
    3

    diglevel 3

    hi my diag level is at 3 but still i get these messages, my paltform is AIX 5.2

    2007-04-25-22.01.22.776387-300 I24307C260 LEVEL: Error
    PID : 26508 TID : 1
    FUNCTION: DB2 Common, Generic Control Facility, GcfCaller::getState, probe:40 MESSAGE : ECF=0x9000028C Timeout occured while calling a GCF interface function

    2007-04-25-01.08.04.209068-300 I12660C351 LEVEL: Severe
    PID : 38574 TID : 1 PROC : DB2_UDB
    INSTANCE: db2d01 NODE : 000
    FUNCTION: DB2 UDB, DRDA Communication Manager, sqljcReceive, probe:30 MESSAGE : CCI Error:
    DATA #1 : Hexdump, 4 bytes
    0x2FF1FE48 : 0000 003C

  4. #4
    Join Date
    Jan 2007
    Location
    Jena, Germany
    Posts
    2,721
    These are error and severe messages. They must show up on DIAGLEVEL 3, of course.

    What we don't know is if the two messages are related to the ones you posted initially. So this may be a completely different issue here.
    Knut Stolze
    IBM DB2 Analytics Accelerator
    IBM Germany Research & Development

  5. #5
    Join Date
    Apr 2007
    Posts
    3
    they are not related messages but i dont know how to solve these 2 errors.

    regarding the GCF time out error i increased the STATUS_TIMEOUT interval from 20 secs to 120 secs still i get the error.

    And regarding the DRDA communication error u say that is fine with diglevel =3 and if dialevel parameter is updated to 2 it may be eliminated.

  6. #6
    Join Date
    Jan 2007
    Location
    Jena, Germany
    Posts
    2,721
    DIAGLEVEL 1 shows only severe messages; DIAGLEVEL 2 severe + error messages; DIAGLEVEL 3 severe + error + warning messages. Changing the DIAGLEVEL is usually a bad idea (except to set it to 4 to get additional "informational" messages for debugging purposes). Suppressing severe/error/warning messages does not help you at all to resolve your problem - which is what you really should try to do.

    As for the second problem, if I read the error code (3C) correctly, then it indicates an out-of-memory condition in the DB2-internal communication layer. So you should verify that your heaps are properly configured and large enough.

    I haven't looked into the first error any close. Maybe both are related; maybe not.
    Knut Stolze
    IBM DB2 Analytics Accelerator
    IBM Germany Research & Development

  7. #7
    Join Date
    Oct 2009
    Location
    Calgary, AB Canada
    Posts
    38
    Quote Originally Posted by stolze View Post
    Changing the DIAGLEVEL is usually a bad idea (except to set it to 4 to get additional "informational" messages for debugging purposes).
    What other 'additional' information would we get if we set DIAGLEVEL to 4?

Posting Permissions

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