Results 1 to 3 of 3
  1. #1
    Join Date
    Sep 2003
    Posts
    2

    Unhappy Unanswered: DRDA Communication Manager Error

    Hi,

    The following error message is being logged frequently into my db2diag.log file.

    DRDA Communication Manager sqljcReceive Probe:30

    CCI Error: 0000 0047 ...G

    2003-09-03-13.02.44.206830 Instance:db2inst1 Node:000
    PID:45678(db2sysc) TID:1 Appid:none
    DRDA Communication Manager sqljcReceive Probe:30

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

    Any pointers on how to solve this. The database is DB2 UDB V 8.1 on AIX 5.1.

    Thanks....

    Regards,

    Sathish

  2. #2
    Join Date
    Mar 2004
    Location
    Toronto, ON, Canada
    Posts
    513
    Quote Originally Posted by sathishp
    Hi,

    The following error message is being logged frequently into my db2diag.log file.

    DRDA Communication Manager sqljcReceive Probe:30

    CCI Error: 0000 0047 ...G

    2003-09-03-13.02.44.206830 Instance:db2inst1 Node:000
    PID:45678(db2sysc) TID:1 Appid:none
    DRDA Communication Manager sqljcReceive Probe:30

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

    Any pointers on how to solve this. The database is DB2 UDB V 8.1 on AIX 5.1.

    Thanks....

    Regards,

    Sathish
    I'm seeing the same message...

    >>>>>>>>>>>>>>>>>>>>
    2004-06-02-09.35.07.031991 Instance:db2inst1 Node:000
    PID:16039(db2bp) TID:8192 Appid:none
    DRDA Communication Manager sqljcReceive Probe:30

    CCI Error:
    0xBFFEC438 : 0x00000047 G...

    2004-06-02-09.35.07.037458 Instance:db2inst1 Node:000
    PID:16039(db2bp) TID:8192 Appid:none
    DRDA Communication Manager sqljcReceive Probe:30

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

    Mine is on a db2 udb v8.1 fp4 / redhat linux as 2.1

    I haven't noticed any external effects so far, and it's only at DIAGLEVEL 4, so it's probably safe to ignore...
    --
    Jonathan Petruk
    DB2 Database Consultant

  3. #3
    Join Date
    Mar 2004
    Location
    Toronto, ON, Canada
    Posts
    513
    I figured out what is trigger it in our environment, and can re-create at will...

    We have a perl script that does :
    $RC = system("db2 list applications show detail");

    As soon as the perl script ends (or is killed), we get that stuff in the db2diag.log:

    2004-06-02-09.56.41.299599 Instance:db2inst1 Node:000
    PID:17929(db2bp) TID:8192 Appid:none
    DRDA Communication Manager sqljcReceive Probe:30

    CCI Error:
    0xBFFECF68 : 0x00000047 G...

    2004-06-02-09.56.41.305960 Instance:db2inst1 Node:000
    PID:17929(db2bp) TID:8192 Appid:none
    DRDA Communication Manager sqljcReceive Probe:30

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

    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

    Must just be the db2bp detecting that the PERL script has gone away. If I add a db2 terminate, I get a similar error with a bunch of semop() errors, saying that a semaphore no longer exists.

    Morale of the story - use DIAGLEVEL 3 and don't worry about the junk that gets spit out when you go to DIAGLEVEL 4, unless you see an external issue!
    --
    Jonathan Petruk
    DB2 Database Consultant

Posting Permissions

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