Automatic Event Handling - Notification Flood

[Dan Lynch]

Last night HPSIM sent out 120 email notifications - all duplicates of the previous week or so. This was happening occasionally with CIM7.2 which led us to upgrade to HPSIM 4.0. We only use two notification tasks -
1. Events of severity critical and major for all systems.
2. Where event category is system insight manager events - name system is reachable.

I cannot fathom why it did this - one thing I did notice is that the events immediately before the two automatic event handling events where triggered were Initial Data Collection and Initial Hardware Status Polling - at the same time. Has anyone experienced anything like this? HPSIM has worked so wonderfully until now...

[John J. Russell]

I've had that same thing happen several times. Twice we received thousands of notifications of past events. My hope is this is addressed in 4.1

[Dan Lynch]

Can you correlate the notification flood to the 'Initial Data Collection' task?

[Dan Lynch]

It turns out that the initial data collection task must not trigger it. I do get the following messages in the SQL error log. (SQL2000 SP3)

2004-05-28 01:44:51.97 spid10 WARNING: EC 56df23c0, 0 waited 300 sec. on latch 4e1b5db0. Not a BUF latch.
2004-05-28 01:44:51.97 spid10 Waiting for type 0x4, current count 0xa, current owning EC 0x271FD538.
2004-05-28 01:45:00.26 spid82 Time out occurred while waiting for buffer latch type 2,bp 0x170ac80, page 1:7748), stat 0xb, object ID 17:2:0, EC 0x62BAB538 : 0, waittime 300. Not continuing to wait.
2004-05-28 01:45:00.26 spid82 Waiting for type 0x2, current count 0x80002a, current owning EC 0x56DF23C0.

The microsoft help on this error did not address our environment, really...

[Debra Anderson_1]

Hi.

We are currently experiencing the same issue (running CIM7) of being flooded by what appears to be all past alerts in the database. This problem started yesterday (June 1)and we are receiving thousands of alerts. Did anyone figure out what was going on here and how to stop it?...we thought that if we purged the database that would solve the problem but cannot figure out how to do this....HELP!!!