HP Systems Insight Manager Running Slow or down completely

[Scott Sievers]

SIM will often not display the logon in screen when I try to access it. Occasionally it will let me log in, but once I get in I get Java errors. One error said (Http Status 503 – Servlet jsp is currently unavailable) and another error said (the server encountered and internal error that prevented it from fulfilling this request). Sometimes when I get into the site, I’ll get kicked out with an error that says (Communication with the HP SIM server has been lost…).

I’m running it on a DL360 G5 with a dual core 1.6 GHz and 4 GB of RAM.

The data base uses Microsoft SQL Server 2005 with a dual core 1.6 GHz processor and 8 GB of RAM.

[Scott Sievers]

The problem was in the Notices Table. This table had over 5 million entries. SIM was trying to run a query against this table over and over again. The query never finished.
There are two main reasons this table got too big. First, the scheduled task set up to delete events older than 90 days never ran. (I am not sure why yet). Second, Insight Manager was getting too many Informational tasks. Most of these Informational tasks were from various systems that kept flooding SIM with Authentication failure traps. After reading some forum posts on resolving authentication failure traps, I was able to eliminate most of these. I ultimately decided to go into the Event Filter Settings and turn off (Accept Registered Events with Severity: Informational). This should make things easier for me to manage in the future.

I was not able to use the GUI to delete the old events. I had my DBA delete all of the Informational events (100=Informational) in the Notices Table. This immediately made my system run faster. In fact, I would say it is as fast now as when I first installed it. I donâ t see any signs of the data base being corrupted because of not using the interface to delete the events.

Is there a command that would verify the integrity of the database for me?

[VRC · Accepted solution]

Data base integrity is checked automatically every time HPSIM starts. You can see from the log file mxdomainmgr.0.log located in logs directory of HPSIM install folder. If integrity fails, you will get a windows system failure event.