That might not be the reason it crashed. That return code may be a
SQL6036N, which is:

SQL6036N START or STOP DATABASE MANAGER command is already in
progress.

Explanation:

A START DATABASE MANAGER or a STOP DATABASE MANAGER command is
already in progress on the system.

User Response:

Wait for the command in progress to complete, then try the
request again.

So, that might just mean that an application process was trying to spawn
an agent while the instance was coming down. Look at the diag.log
messages prior to that one for the reason the instance crashed.

-----Original Message-----
From: JCWoltz
[mailto:db2udbdba-ezmlmshield-x97057706.[Email address protected]
Sent: Wednesday, August 31, 2005 2:46 PM
To: LazyDBA Discussion
Subject: UDB DIA3003E

Our UDB 7.2 ee fp14 db on Solaris crashed with the following diag log
entries.

Any idea what this means?

2005-08-31-13.00.22.969225 Instance:crmp1 Node:000
PID:5098(db2tcpcm 0) Appid:none
common_communication sqlcctcpconnmgr_child Probe:125
DIA3003E Error encountered in "TCPIP" protocol support. Return code from
"sqleGetAgent" was "-6036".


Jim Woltz
Sr Database Administrator
IBM Certified Advanced Database Administrator
[Email address protected]
Phone: 614-564-4277
Cell: 614-323-3467

CheckFree. The Company that Powers Payment on the WebSM.
http://www.checkfree.com/paybillsonline


---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html

DB2 & UDB email list listserv db2-l LazyDBA home page