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

Health monitor causing issues!

P: n/a
Hellos again,
I seem to be having a weird issue. Whenever DB2 Health monitor seems
to run, all connections to the database seem to just lock up. For
example: (and this seems consistent) In list applications, DB2Hmon
will show as "compiling statement", If I issue a "connect to
database"it will hang there until DB2HMON is completed and no longer
showing as a active application. Below is a lock snapshot that occurs
when this is happening. The apps trying to connect do not show as
connected or lock waiting during this time. Any help would be much
appreciated!
Thanks,
Mike

Database Lock Snapshot

Database name = DVDBSE

Database path = F:\DB2\NODE0000\SQL00002\

Input database alias = DVDBSE

Locks held = 4

Applications currently connected = 12

Agents currently waiting on locks = 0

Snapshot timestamp = 10/19/2004
12:24:36.629286

Application handle = 382

Application ID = *LOCAL.DB2.041019172404

Sequence number = 0001

Application name = DB2HMON

Application status = Compiling

Status change time = 10/19/2004
12:23:34.032541

Application code page = 1252

Locks held = 4

Total wait time (ms) = 0

List Of Locks

Lock Name = 0x5359534C48323032B4B76E9441

Lock Attributes = 0x00000000

Release Flags = 0x40000000

Lock Count = 1

Hold Count = 0

Lock Object Name = 0

Object Type = Internal Plan Lock

Mode = S

Lock Name = 0x01000000010000000100180056

Lock Attributes = 0x00000000

Release Flags = 0x40000000

Lock Count = 1

Hold Count = 0

Lock Object Name = 0

Object Type = Internal Variation Lock

Mode = S

Lock Name = 0x5359535348323030DDECEF2841

Lock Attributes = 0x00000000

Release Flags = 0x40000000

Lock Count = 1

Hold Count = 0

Lock Object Name = 0

Object Type = Internal Plan Lock

Mode = S

Lock Name = 0x53514C4445464C5428DD630641

Lock Attributes = 0x00000000

Release Flags = 0x40000000

Lock Count = 1

Hold Count = 0

Lock Object Name = 0

Object Type = Internal Plan Lock

Mode = S
Nov 12 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a

I had bad experience with health monitor ex instance crash I was at FP4
and my perticular problem was fix in Fp5or6 I can't remember. In regard
to your problem make sure you are let say at least at FP6; it seems that
issues with the Health Monitor was fixed in these FP.
t again,
I seem to be having a weird issue. Whenever DB2 Health monitor seems
to run, all connections to the database seem to just lock up. For
example: (and this seems consistent) In list applications, DB2Hmon
will show as "compiling statement", If I issue a "connect to
database"it will hang there until DB2HMON is completed and no longer
showing as a active application. Below is a lock snapshot that occurs
when this is happening. The apps trying to connect do not show as
connected or lock waiting during this time. Any help would be much
appreciated!
Thanks,
Mike

Database Lock Snapshot

Database name = DVDBSE

Database path = F:\DB2\NODE0000\SQL00002\

Input database alias = DVDBSE

Locks held = 4

Applications currently connected = 12

Agents currently waiting on locks = 0

Snapshot timestamp = 10/19/2004
12:24:36.629286

Application handle = 382

Application ID = *LOCAL.DB2.041019172404

Sequence number = 0001

Application name = DB2HMON

Application status = Compiling

Status change time = 10/19/2004
12:23:34.032541

Application code page = 1252

Locks held = 4

Total wait time (ms) = 0

List Of Locks

Lock Name = 0x5359534C48323032B4B76E9441

Lock Attributes = 0x00000000

Release Flags = 0x40000000

Lock Count = 1

Hold Count = 0

Lock Object Name = 0

Object Type = Internal Plan Lock

Mode = S

Lock Name = 0x01000000010000000100180056

Lock Attributes = 0x00000000

Release Flags = 0x40000000

Lock Count = 1

Hold Count = 0

Lock Object Name = 0

Object Type = Internal Variation Lock

Mode = S

Lock Name = 0x5359535348323030DDECEF2841

Lock Attributes = 0x00000000

Release Flags = 0x40000000

Lock Count = 1

Hold Count = 0

Lock Object Name = 0

Object Type = Internal Plan Lock

Mode = S

Lock Name = 0x53514C4445464C5428DD630641

Lock Attributes = 0x00000000

Release Flags = 0x40000000

Lock Count = 1

Hold Count = 0

Lock Object Name = 0

Object Type = Internal Plan Lock

Mode = S

Nov 12 '05 #2

P: n/a
Dany,
Sorry I thought I gave specs..
Db2 8.2 fp 7a
Win2k3

MM
Dany <da******@videotron.ca> wrote in message news:<cl*********@news1.stadia.fi>...
I had bad experience with health monitor ex instance crash I was at FP4
and my perticular problem was fix in Fp5or6 I can't remember. In regard
to your problem make sure you are let say at least at FP6; it seems that
issues with the Health Monitor was fixed in these FP.

Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.