topic Migrate SIM MSDE Database to Remote SQL Database in Server Management - Systems Insight Manager

Migrate SIM MSDE Database to Remote SQL Database

DTape85 — Tue, 22 Jan 2008 20:21:18 GMT

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?

Re: Migrate SIM MSDE Database to Remote SQL Database

Jimmy Rueedi — Wed, 23 Jan 2008 11:21:34 GMT

Did you change the ODBC DNS's?

Regards Jimmy

Re: Migrate SIM MSDE Database to Remote SQL Database

DTape85 — Thu, 24 Jan 2008 15:38:14 GMT

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.

Re: Migrate SIM MSDE Database to Remote SQL Database

stefano colombo_1 — Thu, 17 Jul 2008 08:48:46 GMT

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

Stefano

Re: Migrate SIM MSDE Database to Remote SQL Database

stefano colombo_1 — Thu, 17 Jul 2008 09:23:29 GMT

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