Topic
  • 2 replies
  • Latest Post - ‏2006-07-22T06:12:14Z by SystemAdmin
SystemAdmin
SystemAdmin
5837 Posts

Pinned topic External Comms Error in db2diag.log

‏2006-04-28T08:10:43Z |
Hi,

Has anyone seen or have any info on what this error means, it is appearing repeatedly in the db2diag.logs even though I seem to have no issue connecting from the client.

2006-04-28-03.43.36.790827-240 I217743A411 LEVEL: Severe
PID : 4436144 TID : 1 PROC : db2agent (instance) 0
INSTANCE: uspdapl1 NODE : 000
APPHDL : 0-302 APPID: AC1F0203.O80A.00D4C8074334
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"
looking at the the ZRC code it maps to a -902 code, A class 1 communication
error.

We are using db2 v8.2 fp 10 on AIX 5.2. Server authentication.

Any thoughts would be appreciated

thanks

Guy
Updated on 2006-07-22T06:12:14Z at 2006-07-22T06:12:14Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    5837 Posts

    Re: External Comms Error in db2diag.log

    ‏2006-05-03T18:42:06Z  
    Hi,
    I am also facing these errors in the Logs. using DB2 UDB 8.1 fp9 on AIX.
    We are facing serious performance problems with the database and lots of lock time outs and lock escalations. Is this error in anyway related to lock escalations or time outs?

    If anyone can provide any info on this issue it would be great.

    Thanks ,
    Arun
    > Hi,
    >
    > Has anyone seen or have any info on what this error
    > means, it is appearing repeatedly in the db2diag.logs
    > even though I seem to have no issue connecting from
    > the client.
    >
    > 2006-04-28-03.43.36.790827-240 I217743A411
    > LEVEL: Severe
    > PID : 4436144 TID : 1
    > PROC : db2agent (instance) 0
    > INSTANCE: uspdapl1 NODE : 000
    > APPHDL : 0-302 APPID:
    > AC1F0203.O80A.00D4C8074334
    > FUNCTION: DB2 UDB, base sys utilities,
    > sqleattach_agent, probe:60
    > RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR,
    > SQLT_SQLJC
    > "External Comm error"
    >
    >
    > looking at the the ZRC code it maps to a -902 code, A
    > class 1 communication
    > error.
    >
    > We are using db2 v8.2 fp 10 on AIX 5.2. Server
    > authentication.
    >
    > Any thoughts would be appreciated
    >
    > thanks
    >
    > Guy
  • SystemAdmin
    SystemAdmin
    5837 Posts

    Re: External Comms Error in db2diag.log

    ‏2006-07-22T06:12:14Z  
    Hi,
    I am also facing these errors in the Logs. using DB2 UDB 8.1 fp9 on AIX.
    We are facing serious performance problems with the database and lots of lock time outs and lock escalations. Is this error in anyway related to lock escalations or time outs?

    If anyone can provide any info on this issue it would be great.

    Thanks ,
    Arun
    > Hi,
    >
    > Has anyone seen or have any info on what this error
    > means, it is appearing repeatedly in the db2diag.logs
    > even though I seem to have no issue connecting from
    > the client.
    >
    > 2006-04-28-03.43.36.790827-240 I217743A411
    > LEVEL: Severe
    > PID : 4436144 TID : 1
    > PROC : db2agent (instance) 0
    > INSTANCE: uspdapl1 NODE : 000
    > APPHDL : 0-302 APPID:
    > AC1F0203.O80A.00D4C8074334
    > FUNCTION: DB2 UDB, base sys utilities,
    > sqleattach_agent, probe:60
    > RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR,
    > SQLT_SQLJC
    > "External Comm error"
    >
    >
    > looking at the the ZRC code it maps to a -902 code, A
    > class 1 communication
    > error.
    >
    > We are using db2 v8.2 fp 10 on AIX 5.2. Server
    > authentication.
    >
    > Any thoughts would be appreciated
    >
    > thanks
    >
    > Guy
    This error has certainly nothing to do with lock escalations or lock timeout. Lock escalations could be addressed by tuning Locklist, maxlocks parameters.