Server Management - Systems Insight Manager
1833330 Members
3251 Online
110051 Solutions
New Discussion

Migrate SIM MSDE Database to Remote SQL Database

 
DTape85
New Member

Migrate SIM MSDE Database to Remote SQL Database

Currently I have the databse moved from the CMS to the remote SQL server. When I alter the database.props file and restart the SIM service I get the following application error in the event log:

Event Type: Error
Event Source: HP Systems Insight Manager
Event Category: None
Event ID: 3
Date: 1/22/2008
Time: 3:02:27 PM
User: N/A
Computer: GRRSIM01
Description:
com.hp.mx.database.DbVerificationException: Error loading database verification handler 'com.hp.mx.database.MsSqlVerificationHandler'
com.hp.mx.database.DbVerificationException: Error accessing database

In the database.props file here is what I altered:

hp.Database.hostName=SERVERNAME
hp.Database.instance=SERVERNAME\INSTANCE\\

The login is correct and I ran mxpassword -m -x MXDBuserPassword to ensure the correct password was being used. I also tried several variations of strings to point to the hostName and instance with no success. Does anyone know what's going on here?


4 REPLIES 4
Jimmy Rueedi
Frequent Advisor

Re: Migrate SIM MSDE Database to Remote SQL Database

Did you change the ODBC DNS's?

Regards Jimmy
DTape85
New Member

Re: Migrate SIM MSDE Database to Remote SQL Database

I did change the ODBC DSN's. That had no affect on how SIM worked. It still used the local MSDE database until I changed the databse.props file to the remote SQL server. That's when I received the above error.
stefano colombo_1
Super Advisor

Re: Migrate SIM MSDE Database to Remote SQL Database

Hi ,
I'm having the same issue here .
Did you change the database.admin file too ?

Stefano
stefano colombo_1
Super Advisor

Re: Migrate SIM MSDE Database to Remote SQL Database

Hi ,
I found what the problem was in my case.
Since we're migrating to a SQL2005 clustered server with multiple instances , but I think it would be the same with a non clustered env, the port the instance is listening to is dynamic and not , in any case , the standard 1433 .

Changing the port to static , in SQL instance , and set it in the .props files solved the issue

HTH to others people
Stefano