2008-03-06-01.10.23.178496-300 E57434627C785 LEVEL: Error (OS)
PID : 26060 TID : 772 PROC : db2hmon
INSTANCE: inst1 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloPdbConnectSocket, probe:20
MESSAGE : ZRC=0x810F0012=-2129723374=SQLO_COMM_ERR "Communication error"
CALLED : OS, -, connect
OSERR : ENOENT (2) "No such file or directory"
DATA #1 : String, 32 bytes
Unable to connect socket on path
DATA #2 : socket, 4 bytes
7
DATA #3 : sockaddr, 37 bytes
0x30385F38 : 0001 2F68 6F6D 652F 696E 7374 3161 646D ../home/inst1adm
0x30385F48 : 2F64 6173 2F74 6D70 2F64 6173 6E61 6D65 /das/tmp/dasname
0x30385F58 : 6470 6970 65 dpipe
DATA #4 : File name, 35 bytes
/home/inst1adm/das/tmp/dasnamedpipe
2008-03-06-02.05.23.990797-300 E57435413C785 LEVEL: Error (OS)
PID : 26060 TID : 772 PROC : db2hmon
INSTANCE: inst1 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloPdbConnectSocket, probe:20
MESSAGE : ZRC=0x810F0012=-2129723374=SQLO_COMM_ERR "Communication error"
CALLED : OS, -, connect
OSERR : ENOENT (2) "No such file or directory"
DATA #1 : String, 32 bytes
Unable to connect socket on path
DATA #2 : socket, 4 bytes
************************
db2level
DB21085I Instance "inst1" uses "32" bits and DB2 code release "SQL08026" with
level identifier "03070106".
Informational tokens are "DB2 v8.1.1.120", "s060801", "U808888", and FixPak
"13".
Product is installed at "/usr/opt/db2_08_01".
The above error message was found in db2diag.log.
The only problem we whave when reboot theserver this weeknd . so many thousend of mails sent to mail boxes
email is like this
db2fmd
The state of instance 'inst1adm' gcf module '/home/inst1adm/das/lib/libdb2dasgcf.a' is OPERABLE (OFFLINE).