db2diag.log filled with sqleattach_agent function errors

Technote (FAQ)

Problem

This document provides troubleshooting information for when your db2diag.log is filled with errors from the sqleattach_agent function, with RETCODE : ZRC=0x81360012=-2127167470.

Cause

The 0x81360012 message is informational, and can be ignored. It means that a communication failure has occurred when an instance attachment was attempted and the authentication of the user failed. Here are three situations that cause 0x81360012:

1) This type of message can occur if you are using a remote workstation running the DB2® Administration Client and trying to attach to the database via the Control Center. In particular, the message is generated if you attempt the attachment using the
incorrect userid and password combination.

2) These messages can also be caused when the health monitor is started
on any (remote) machine that has the instance cataloged. By default,
the health monitor tries to attach to all nodes in the node directory,
and since it does not supply a userid or password, the server will
reject it.

3) It can also be related to having the db2detaildeadlock event monitor switched on.

In DB2 Universal Database™ (DB2 UDB) Version 8, the event monitor DB2DETAILDEADLOCK is defined by default and set to
AUTOSTART. Thus when the database is started, the event monitor will be started.
If the database is being started (for example via a CONNECT or ATTACH statement) from a remote client, then you need to specify a valid userid and password to avoid adding these messages to the db2diag.log.

Diagnosis Details
An example of the error message is as follows:

2006-02-07-13.46.28.131903-480 I705173A435 LEVEL: Severe

PID : 6664364 TID : 1 PROC : db2agent (instance) 0
INSTANCE: instit01 NODE : 000 DB : CSE1TR01
APPHDL : 0-171 APPID: PE6098D0.FD08.019607214638
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent,
probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR,
SQLT_SQLJC
"External Comm error"

Solution

These messages can be ignored.

If you wish to determine order the IP address of the remote machine which is trying to attach, record the application ID (APPID) specified in the db2diag.log messages and transform it to an IP address using the instructions referenced in the Related Information section, below

1. 제어센터에서 접속을 할때 떨어질 수 있는데 이것은 무시.
2. 이게 가장 의심스러운데요..  health monitor가 메모리를 많이 먹습니다.
    db2 get dbm cfg 를 하셔셔 health monitor가 켜져 있는지 확인
    (HEALTH_MON) = ON이며
    db2 update dbm cfg using HEALTH_MON OFF
    하시고 db2stop/start
3. event monitor를 사용했을때 떨어진다고 했는데..

마라도님이 2007-01-29 09:52에 작성한 댓글입니다.
이 댓글은 2007-01-29 09:53에 마지막으로 수정되었습니다. Edit Ｘ