Tag Archives: hpsim

Moving HP SIM to a new database

One would think that a product like HP SIM would be quite comprehensive and well documented when you want to move its database to another server. However, it had been quite a frustrating affair trying to search for solutions on the Internet, from the help manual of HP SIM and from the HP forum itself. I, however, managed to find a related help document that details changes the HP SIM name and guessed from there what needs to be changed to move the HP SIM database to another server.

Okay, this happened because our DBA has migrated all SQL Server 2000 databases to the 2005 version. I thought that it would be a simple change of the 2 ODBC system DSN: Insight_v50_0 and PMP_V3_0 (I only used these 2 database, you could have more than that). So I quickly launch ODBC and made the changes to the system DSN, restarted HP SIM and trying logging on. Logon was successful and everything looks okay, until I checked with my DBA who told me that I am still hitting the old SQL server.

Searches in the HP forum found a possible solution in the thread: Move HP SIM Database to new SQL Server

One of the links pointed to files you need to modify to change system name. Took a quick look and decided to search the HP program files folder for text containing my old server name. Made the changes and finally got it move to the new SQL server.

Here is what I did… you need to change the database instance values in the following files in C:\Program Files\HP\Systems Insight Manager\config:

  • database.admin
  • database.props
  • databaseadminupd.tpl

As with all changes, make a BACKUP copy before amending the files.


Posted by on August 4, 2007 in Windows



HP SIM Server showing blank server list

This morning our HP SIM server decided to stop working… The problem is that no servers appeared in the system list this morning although we have at least 1,000 server listed last night!

So my first thought was that someone deleted all my servers accidentally last night. No problems, the host file is still intact and running the “Add Systems” should fix this.. or so I thought. No such luck after 30 mins, no server appeared.

So now my attention turned to security, could there be a permissioning error? We are using domain groups for permissioning (something new in this version) instead of individual users. So I thought maybe the system account which I am using or the HP SIM service could not resolve the group properly. So I added my own account and gave full permissions, logged out, logged in, no such luck, no servers in sight. I even tried logging on using the default system account without any sucess.

Of course, one of the first thing that you would check is the event logs. But its very quiet, not a single complain about anything!

Now my attention moves to the database. As the database is managed by a DBA team, I suspected something could have changed to have cause the service not to query the database properly. However, I expected such errors to turn up on HP SIM, but there weren’t. So I ran ODBC from my HP SIM with the db account I have to connect to the database and it return error. Finally, some complains!

I loggged on to the db server and checked its event logs. Ah ha! Its full of errors generated by the HP SIM account:

Error: 9002, Severity: 17, State: 6
The log file for database ‘tempdb’ is full. Back up the transaction log for the database to free up some log space.

An email to the DBA team and they fixed it. Now my servers are back in HP SIM.

Its strange that HP SIM never complained about this in the eventlogs and I had to spend like 1 hour troubleshooting on this issue. Anyway, lesson learned, no events doesn’t mean everything is fine and good

Leave a comment

Posted by on August 17, 2006 in Windows



Problem with HP System Insight Manger

[Update 03 Aug 2006]: The server have not been acting up since…

Recently, I upgrade the HP SIM from 4.2 to 5.0 SP5. Almost immediately, I could see mxdomainmgr.exe sucking up like 400 MB of memory and climbing. Didn’t think about it much as I thought the latest versions should be more efficient or better.

Turns out that the next morning, the HP SIM died on me… had to force a reboot of the HP SIM server. After reboot, I could see mxdomainmgr hogging both memory and CPU cycles. CPU is at almost 90% most of the time and the memory starts climbing again to about 600 MB and more!

A quick search in the HP forum seems to tell me that its something that has existed for at least 1 year. The one year old thread is still alive: mxdomainmgr.exe CPU Utilization @ 98%. Incredibly, people are still complaining about the same things after 1 year.

I think that its a PR disaster that many tech companies, including HP, sets up forums in their own servers, but you never really see real HP engineers replying to your problems. How uncaring can that be?

Anyway, a few suggestions were available and 2 worked for me… at least for now

– uncheck “Send Authentication Traps” in SNMP services in the server
– Lower the DataCollectionThreadCount parameter in the globalsettings.props file. I am setting it to 1.

Other suggestions, which I think is a must in the first place:
– run the database (SQL) on another server
– get a good spec for your server

Updated: 28/07
Server had a java memory error today and the SIM won’t start:

java.lang.OutOfMemoryError: Java heap space

Found one of the solution in HP Forum and hopefully it works:

Incase anyone is using VMM for managment of their virtual machine, there is one more workaround that can be tried out for mxdomainmgr hogging issue

1. Stop the HP VMM service , .HP Virtual Machine Management Service, from the Service Console (Programs->Administrative tools ->Services)

2. Open the \HP Virtualization Management Software\bin \hpvmm.conf file and add this property definition:
SimQueryDelaySec = 300

3. Start the VMM service service , HP Virtual Machine Management Service from the Service Console (Programs->Administrative tools ->Services)


This “NEW” SIM upgrade seems more like 10 step backwards as days go by… 😦

I even set the server to reboot daily!


Posted by on July 27, 2006 in Windows