Health monitor causing issues!

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Mike
    #1

    Health monitor causing issues!

    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.0410 19172404

    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 = 0x5359534C48323 032B4B76E9441

    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 = 0x0100000001000 0000100180056

    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 = 0x5359535348323 030DDECEF2841

    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 = 0x53514C4445464 C5428DD630641

    Lock Attributes = 0x00000000

    Release Flags = 0x40000000

    Lock Count = 1

    Hold Count = 0

    Lock Object Name = 0

    Object Type = Internal Plan Lock

    Mode = S
    Tags: None
    • Dany
      #2
      Re: Health monitor causing issues!


      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,[color=blue]
      > 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.0410 19172404
      >
      > 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 = 0x5359534C48323 032B4B76E9441
      >
      > 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 = 0x0100000001000 0000100180056
      >
      > 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 = 0x5359535348323 030DDECEF2841
      >
      > 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 = 0x53514C4445464 C5428DD630641
      >
      > Lock Attributes = 0x00000000
      >
      > Release Flags = 0x40000000
      >
      > Lock Count = 1
      >
      > Hold Count = 0
      >
      > Lock Object Name = 0
      >
      > Object Type = Internal Plan Lock
      >
      > Mode = S[/color]

        Comment

        • Mike
          #3
          Re: Health monitor causing issues!

          Dany,
          Sorry I thought I gave specs..
          Db2 8.2 fp 7a
          Win2k3

          MM
          Dany <danyboy_@video tron.ca> wrote in message news:<clg7u0$b1 11@news1.stadia .fi>...[color=blue]
          > 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.
          >
          >[/color]

            Comment

            Previous template Next
            Working...