Hi Shashank,
Thanks for the reply. However, to set the diaglevel 4 is not feasible as this will actually dump too many info on the db2diag.log. I have use the db2pdcfg to actually capture the deadlock.
btw, for your simulation, how often you get locktimeout and deadlock? during my simulation, the results that i got was:
a) 1 error code 2, 1 error code 68
b) 2 error code 68
does you guys faced the same ...
eddy82
Last Activity: Dec 30 '10, 08:13 AM
Joined: Oct 17 '08
Location:
-
db2diag.log doesn't capture deadlock
Hi DB2 Gurus,
I just want to clarify, does the db2diag.log capture a deadlock error? SQL911 with code 2 and 68.
I am using db2 V9.1 FP 5 running in RHEL4. I have done a simulation to the deadlock and locktimeout, however, the error didn't report to the db2diag.log. I am using DIAGLEVEL 3.
Is this expected? Or it should be reported in my db2diag.log?
I have enable the stmt and lock, stmt and timestamp monitor... -
eddy82 started a topic DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130 in db2diag.login DB2DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130 in db2diag.log
Hi All,
I have this db2start in my db2diag.log everyday around the same time. But no db2stop in the db2diag.log or in the db2.nfy.
I already check and no corruption or cronjob running during that time. However when i check the db up time, it is different from the one specified in the db2diag.log. So i suspect, the db2start didn't ran, but it still appear in the db2diag.log.
Anyone here got encounter this issue... -
Detected the death of an EDU. Process was 11.
Hi guys.I need some advice as i my db2 instance was kill off suddenly at late night and not sure what has kill it.
2008-10-14-22.47.53.326765 +480 E31715373A878 LEVEL: Severe
PID : 856268 TID : 1 PROC : db2gds 0
INSTANCE: db2egq NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloEDUSIGCHLDH andler, probe:50
DATA #1 : <preformatted >
Detected...
No activity results to display
Leave a comment: