Skip to main content

DB2 V9 ZRC=0x81360012 External Comm Error in db2diag.log


Technote (FAQ)


Question

Why does this error occur in the db2diag.log?
ZRC=0x81360012 External Comm error

Cause

If you have diaglevel=4 in the DB2 dbm cfg, DB2 will record all errors, warnings and informational messages

The RETCODE: ZRC=0x81360012 is an informational message, not a severe error and it can be ignored..

This informational message means a communication failure when the authentication of a user has failed

For example:

- a client connection attempt

- a front-end application connection attempt.



Example of db2diag.log entry:

2009-07-17-15.13.02.291238-300 I3888C437 LEVEL: Info
PID : 53390 TID : 1 PROC : db2agent (CSCUIPRD) 0
INSTANCE: cscuiprd NODE : 000 DB : CSCUIPRD
APPHDL : 0-930 APPID: ABC53DB9.P939.090717195707
FUNCTION: DB2 UDB, DRDA Communication Manager, sqljcReceive, probe:30
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"


Answer

Change diaglevel=3


DB2 UPDATE DBM CFG USING DIAGLEVEL 3


Related information

diaglevel - Diagnostic error capture level configuratio

Rate this page:

(0 users)Average rating

Copyright and trademark information

IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Rate this page:


(0 users)Average rating

Add comments

Document information

DB2 for Linux, UNIX and Windows


Software version:
9.1, 9.5, 9.7


Operating system(s):
AIX, HP-UX, Linux, Solaris, Windows


Reference #:
1394844


Modified date:
2009-10-08

Translate my page

Content navigation