Occasionally we see these messages in the db2diag.log file. Can someone
tell me what they mean and are they anything to worry about?
2005-03-03-10.42.04.286220 Instance:db2inst1 Node:000
PID:64936(db2sysc 0) TID:1 Appid:none
base sys utilities sqleChildCrashHandler Probe:15
DiagData
0x10008A70 : 4120 6E6F 6E2D 4544 5520 6368 696C 6420 A non-EDU child
0x10008A80 : 6372 6173 6865 642E crashed.
2005-03-03-10.42.04.649795 Instance:db2inst1 Node:000
PID:64936(db2sysc 0) TID:1 Appid:none
base sys utilities sqleChildCrashHandler Probe:16
DiagData
0x2FF21274 : 0x000092E4 ...?
2005-03-03-10.42.04.733282 Instance:db2inst1 Node:000
PID:64936(db2sysc 0) TID:1 Appid:none
base sys utilities sqleChildCrashHandler Probe:17
DiagData
0x2FF21278 : 0x00000102 ....
2005-03-03-10.42.04.816578 Instance:db2inst1 Node:000
PID:64936(db2sysc 0) TID:1 Appid:none
base sys utilities sqleChildCrashHandler Probe:18
DiagData
0x2FF2127C : 0xFFFFFFFF ????
Larry - 04 Mar 2005 17:32 GMT
This is something you really need to open a PMR for with IBM support ...
Larry Edelstein
> Occasionally we see these messages in the db2diag.log file. Can someone
> tell me what they mean and are they anything to worry about?
[quoted text clipped - 27 lines]
> DiagData
> 0x2FF2127C : 0xFFFFFFFF ÿÿÿÿ
Sean McKeough - 08 Mar 2005 14:36 GMT
It means a fenced stored proc or udf crashed...you should have a
callstack that'll tell you which of your fenced routines abended.
> Occasionally we see these messages in the db2diag.log file. Can someone
> tell me what they mean and are they anything to worry about?
[quoted text clipped - 27 lines]
> DiagData
> 0x2FF2127C : 0xFFFFFFFF ÿÿÿÿ