By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,004 Members | 1,296 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,004 IT Pros & Developers. It's quick & easy.

Health Monitor restarted - every 14 minutes.

P: n/a
DB2Connect Informational tokens are "DB2 v8.1.0.96", "s050811",
"U803921", FixPak "10".

I am getting txxxxxx.0000 files approximately every 14 minutes that
look like:
<Trap>
<Header>
DB2 build information: DB2 v8.1.0.96 s050811 SQL08023
timestamp: 2007-02-15-01.37.12.101223
instance name: db2inst1.000
EDU name : db2hmon
Signal #11
uname: S:SunOS R:5.10 V:Generic_118833-18 M:sun4u N:plss2100
process id: 9814
thread id : 1 (0x1)
</Header>
<SignalDetails>
<Siginfo_t length="128">
0000000B 00000002 00000000 FDCD9048
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
</Siginfo_t>
Signal #11 (SIGSEGV): si_addr is 0xFDCD9048, si_code is 0x00000002
(SEGV_ACCERR:Invalid permissions for mapped object.)
</SignalDetails>
<ResourceLimits>
Data seg top [sbrk(0)] = 0x0009D3E0
Cur data size (bytes) = 0xFFFFFFFFFFFFFFFD
Cur stack size (bytes) = 0x0000000000800000
Cur core size (bytes) = 0x0000000077359400
</ResourceLimits>
<Registers>
UCONTEXT: addr=ffbfe658 flags=0000002f
next=00000000 stack=ff400000
regset: psr= fe801004 pc= fd841030
npc= fd84d5ec gwins=00000000
g: 00000000 00000400 0004adb0 fd92db08
0131f000 0131f31b 00000000 fdbc2000
o: fdcd9048 0003012c fd84d5e4 fd87113c
00000624 fd8740a0 ffbfe990 fd84d5e4
l: fd8751b8 fd875178 fd875198 fd875184
fd8750d0 00000028 fd8750d8 fdbec94c
i: fdcd9040 00023b70 fe1ecbc0 00000400
fd87113c 000004e8 ffbfe9f0 fd842bc8
SP==o6 FP==i6 SavePC=i7
PC location: __1cKunsafe_ios2t5B6M_v_ + 0x28
Object file: /opt/IBM/db2/V8.1/lib/libdb2cmncoll.so.1 (offset 0x31030)
</Registers>
<StackTrace>
##### Object: /opt/IBM/db2/V8.1/lib/libdb2cmncoll.so.1
__1cKunsafe_ios2t5B6M_v_(0xfdcd9040,0x23b70,0xfe1e cbc0,0x400,0xfd87113c,
0x4e8) + 0x28
__1cSostream_withassign2t6M_v_(0xfdcd9040,0x23b70, 0xfe1ecbc0,0x400,0xfd87113c,
0x4e8) + 0x1c
__1cNIostream_init2t6M_v_(0xfd875280,0x608,0x628,0 x2e690,0xfd874138,0x400)
+ 0x120
Stack traceback unavailable.
Signal 11 caught in traceback attempt.
In the .log file:
2007-02-15-06.23.09.604728-360 I63081C434 LEVEL: Severe
PID : 17156 TID : 1 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleChildCrashHandler, probe:15
MESSAGE : DiagData
DATA #1 : Hexdump, 31 bytes
0x01BEB4AC : 4865 616C 7468 204D 6F6E 6974 6F72 2050 Health Monitor
P
0x01BEB4BC : 726F 6365 7373 2063 7261 7368 6564 2E rocess
crashed.
I cannot find any of these related error messages and am at a loss as
to why this started. The last change was: db2set
DB2_FMP_COMM_HEAPSZ=10240 then stop/restarted the instance. The
change was made a midnight - and we have been receiving these messages
at a very steady 14-minute interval.

Any help would be appreciated.

Michael.

Feb 15 '07 #1
Share this Question
Share on Google+
4 Replies


P: n/a
On Feb 15, 7:23 pm, "onedbguru" <onedbg...@yahoo.comwrote:
DB2Connect Informational tokens are "DB2 v8.1.0.96", "s050811",
"U803921", FixPak "10".

I am getting txxxxxx.0000 files approximately every 14 minutes that
look like:
<Trap>
<Header>
DB2 build information: DB2 v8.1.0.96 s050811 SQL08023
timestamp: 2007-02-15-01.37.12.101223
instance name: db2inst1.000
EDU name : db2hmon
Signal #11
uname: S:SunOS R:5.10 V:Generic_118833-18 M:sun4u N:plss2100
process id: 9814
thread id : 1 (0x1)
</Header>
<SignalDetails>
<Siginfo_t length="128">
0000000B 00000002 00000000 FDCD9048
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
</Siginfo_t>
Signal #11 (SIGSEGV): si_addr is 0xFDCD9048, si_code is 0x00000002
(SEGV_ACCERR:Invalid permissions for mapped object.)
</SignalDetails>
<ResourceLimits>
Data seg top [sbrk(0)] = 0x0009D3E0
Cur data size (bytes) = 0xFFFFFFFFFFFFFFFD
Cur stack size (bytes) = 0x0000000000800000
Cur core size (bytes) = 0x0000000077359400
</ResourceLimits>
<Registers>
UCONTEXT: addr=ffbfe658 flags=0000002f
next=00000000 stack=ff400000
regset: psr= fe801004 pc= fd841030
npc= fd84d5ec gwins=00000000
g: 00000000 00000400 0004adb0 fd92db08
0131f000 0131f31b 00000000 fdbc2000
o: fdcd9048 0003012c fd84d5e4 fd87113c
00000624 fd8740a0 ffbfe990 fd84d5e4
l: fd8751b8 fd875178 fd875198 fd875184
fd8750d0 00000028 fd8750d8 fdbec94c
i: fdcd9040 00023b70 fe1ecbc0 00000400
fd87113c 000004e8 ffbfe9f0 fd842bc8
SP==o6 FP==i6 SavePC=i7
PC location: __1cKunsafe_ios2t5B6M_v_ + 0x28
Object file: /opt/IBM/db2/V8.1/lib/libdb2cmncoll.so.1 (offset 0x31030)
</Registers>
<StackTrace>
##### Object: /opt/IBM/db2/V8.1/lib/libdb2cmncoll.so.1
__1cKunsafe_ios2t5B6M_v_(0xfdcd9040,0x23b70,0xfe1e cbc0,0x400,0xfd87113c,
0x4e8) + 0x28
__1cSostream_withassign2t6M_v_(0xfdcd9040,0x23b70, 0xfe1ecbc0,0x400,0xfd8711*3c,
0x4e8) + 0x1c
__1cNIostream_init2t6M_v_(0xfd875280,0x608,0x628,0 x2e690,0xfd874138,0x400)
+ 0x120

Stack traceback unavailable.
Signal 11 caught in traceback attempt.

In the .log file:
2007-02-15-06.23.09.604728-360 I63081C434 LEVEL: Severe
PID : 17156 TID : 1 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleChildCrashHandler, probe:15
MESSAGE : DiagData
DATA #1 : Hexdump, 31 bytes
0x01BEB4AC : 4865 616C 7468 204D 6F6E 6974 6F72 2050 Health Monitor
P
0x01BEB4BC : 726F 6365 7373 2063 7261 7368 6564 2E rocess
crashed.

I cannot find any of these related error messages and am at a loss as
to why this started. The last change was: db2set
DB2_FMP_COMM_HEAPSZ=10240 then stop/restarted the instance. The
change was made a midnight - and we have been receiving these messages
at a very steady 14-minute interval.

Any help would be appreciated.

Michael.
These are trap files are generated when any of the DB2 processes is
terminated, these trap files are generated more: when DB2 processes
are killed/terminated..this is may happen due to memory issues or OS
services..resulting in instance stop..

Feb 15 '07 #2

P: n/a
On Feb 15, 9:10 am, vijay...@gmail.com wrote:
On Feb 15, 7:23 pm, "onedbguru" <onedbg...@yahoo.comwrote:


DB2Connect Informational tokens are "DB2 v8.1.0.96", "s050811",
"U803921", FixPak "10".
I am getting txxxxxx.0000 files approximately every 14 minutes that
look like:
<Trap>
<Header>
DB2 build information: DB2 v8.1.0.96 s050811 SQL08023
timestamp: 2007-02-15-01.37.12.101223
instance name: db2inst1.000
EDU name : db2hmon
Signal #11
uname: S:SunOS R:5.10 V:Generic_118833-18 M:sun4u N:plss2100
process id: 9814
thread id : 1 (0x1)
</Header>
<SignalDetails>
<Siginfo_t length="128">
0000000B 00000002 00000000 FDCD9048
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
</Siginfo_t>
Signal #11 (SIGSEGV): si_addr is 0xFDCD9048, si_code is 0x00000002
(SEGV_ACCERR:Invalid permissions for mapped object.)
</SignalDetails>
<ResourceLimits>
Data seg top [sbrk(0)] = 0x0009D3E0
Cur data size (bytes) = 0xFFFFFFFFFFFFFFFD
Cur stack size (bytes) = 0x0000000000800000
Cur core size (bytes) = 0x0000000077359400
</ResourceLimits>
<Registers>
UCONTEXT: addr=ffbfe658 flags=0000002f
next=00000000 stack=ff400000
regset: psr= fe801004 pc= fd841030
npc= fd84d5ec gwins=00000000
g: 00000000 00000400 0004adb0 fd92db08
0131f000 0131f31b 00000000 fdbc2000
o: fdcd9048 0003012c fd84d5e4 fd87113c
00000624 fd8740a0 ffbfe990 fd84d5e4
l: fd8751b8 fd875178 fd875198 fd875184
fd8750d0 00000028 fd8750d8 fdbec94c
i: fdcd9040 00023b70 fe1ecbc0 00000400
fd87113c 000004e8 ffbfe9f0 fd842bc8
SP==o6 FP==i6 SavePC=i7
PC location: __1cKunsafe_ios2t5B6M_v_ + 0x28
Object file: /opt/IBM/db2/V8.1/lib/libdb2cmncoll.so.1 (offset 0x31030)
</Registers>
<StackTrace>
##### Object: /opt/IBM/db2/V8.1/lib/libdb2cmncoll.so.1
__1cKunsafe_ios2t5B6M_v_(0xfdcd9040,0x23b70,0xfe1e cbc0,0x400,0xfd87113c,
0x4e8) + 0x28
__1cSostream_withassign2t6M_v_(0xfdcd9040,0x23b70, 0xfe1ecbc0,0x400,0xfd8711**3c,
0x4e8) + 0x1c
__1cNIostream_init2t6M_v_(0xfd875280,0x608,0x628,0 x2e690,0xfd874138,0x400)
+ 0x120
Stack traceback unavailable.
Signal 11 caught in traceback attempt.
In the .log file:
2007-02-15-06.23.09.604728-360 I63081C434 LEVEL: Severe
PID : 17156 TID : 1 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleChildCrashHandler, probe:15
MESSAGE : DiagData
DATA #1 : Hexdump, 31 bytes
0x01BEB4AC : 4865 616C 7468 204D 6F6E 6974 6F72 2050 Health Monitor
P
0x01BEB4BC : 726F 6365 7373 2063 7261 7368 6564 2E rocess
crashed.
I cannot find any of these related error messages and am at a loss as
to why this started. The last change was: db2set
DB2_FMP_COMM_HEAPSZ=10240 then stop/restarted the instance. The
change was made a midnight - and we have been receiving these messages
at a very steady 14-minute interval.
Any help would be appreciated.
Michael.

These are trap files are generated when any of the DB2 processes is
terminated, these trap files are generated more: when DB2 processes
are killed/terminated..this is may happen due to memory issues or OS
services..resulting in instance stop..- Hide quoted text -

- Show quoted text -
Other relevant information - Solaris 2.10.

Thank you, but what I need to know is how to troubleshoot why the
monitor is dying and correct the problem.

Feb 15 '07 #3

P: n/a
Are you _using_ the health monitor? If not the obvious "quick fix" is to
switch it off altogether.

Otherwise: PMR

Cheers
Serge

--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
Feb 15 '07 #4

P: n/a
.... I often suggest my customers to turn off the health monitor and
the auto maintainence features. For reasons like access plan
stability, perf. impact, etc.

On Feb 15, 8:23 am, "onedbguru" <onedbg...@yahoo.comwrote:
DB2Connect Informational tokens are "DB2 v8.1.0.96", "s050811",
"U803921", FixPak "10".

I am getting txxxxxx.0000 files approximately every 14 minutes that
look like:,
<Trap>
<Header>
DB2 build information: DB2 v8.1.0.96 s050811 SQL08023
timestamp: 2007-02-15-01.37.12.101223
instance name: db2inst1.000
EDU name : db2hmon
Signal #11
uname: S:SunOS R:5.10 V:Generic_118833-18 M:sun4u N:plss2100
process id: 9814
thread id : 1 (0x1)
</Header>
<SignalDetails>
<Siginfo_t length="128">
0000000B 00000002 00000000 FDCD9048
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
</Siginfo_t>
Signal #11 (SIGSEGV): si_addr is 0xFDCD9048, si_code is 0x00000002
(SEGV_ACCERR:Invalid permissions for mapped object.)
</SignalDetails>
<ResourceLimits>
Data seg top [sbrk(0)] = 0x0009D3E0
Cur data size (bytes) = 0xFFFFFFFFFFFFFFFD
Cur stack size (bytes) = 0x0000000000800000
Cur core size (bytes) = 0x0000000077359400
</ResourceLimits>
<Registers>
UCONTEXT: addr=ffbfe658 flags=0000002f
next=00000000 stack=ff400000
regset: psr= fe801004 pc= fd841030
npc= fd84d5ec gwins=00000000
g: 00000000 00000400 0004adb0 fd92db08
0131f000 0131f31b 00000000 fdbc2000
o: fdcd9048 0003012c fd84d5e4 fd87113c
00000624 fd8740a0 ffbfe990 fd84d5e4
l: fd8751b8 fd875178 fd875198 fd875184
fd8750d0 00000028 fd8750d8 fdbec94c
i: fdcd9040 00023b70 fe1ecbc0 00000400
fd87113c 000004e8 ffbfe9f0 fd842bc8
SP==o6 FP==i6 SavePC=i7
PC location: __1cKunsafe_ios2t5B6M_v_ + 0x28
Object file: /opt/IBM/db2/V8.1/lib/libdb2cmncoll.so.1 (offset 0x31030)
</Registers>
<StackTrace>
##### Object: /opt/IBM/db2/V8.1/lib/libdb2cmncoll.so.1
__1cKunsafe_ios2t5B6M_v_(0xfdcd9040,0x23b70,0xfe1e cbc0,0x400,0xfd87113c,
0x4e8) + 0x28
__1cSostream_withassign2t6M_v_(0xfdcd9040,0x23b70, 0xfe1ecbc0,0x400,0xfd87113c,
0x4e8) + 0x1c
__1cNIostream_init2t6M_v_(0xfd875280,0x608,0x628,0 x2e690,0xfd874138,0x400)
+ 0x120

Stack traceback unavailable.
Signal 11 caught in traceback attempt.

In the .log file:
2007-02-15-06.23.09.604728-360 I63081C434 LEVEL: Severe
PID : 17156 TID : 1 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleChildCrashHandler, probe:15
MESSAGE : DiagData
DATA #1 : Hexdump, 31 bytes
0x01BEB4AC : 4865 616C 7468 204D 6F6E 6974 6F72 2050 Health Monitor
P
0x01BEB4BC : 726F 6365 7373 2063 7261 7368 6564 2E rocess
crashed.

I cannot find any of these related error messages and am at a loss as
to why this started. The last change was: db2set
DB2_FMP_COMM_HEAPSZ=10240 then stop/restarted the instance. The
change was made a midnight - and we have been receiving these messages
at a very steady 14-minute interval.

Any help would be appreciated.

Michael.

Feb 15 '07 #5

This discussion thread is closed

Replies have been disabled for this discussion.