Re: Profile DB Migration issue BSM9.20.191 (270 Views)
Reply
Frequent Advisor
scorpio131179
Posts: 74
Registered: ‎12-03-2009
Message 1 of 4 (311 Views)

Profile DB Migration issue BSM9.20.191

good day everyone.

i have some questions related to profile DB migration of MS SQL 2008R2 Server.

admins migrated MS SQL DB to another server succssesfuly, but credentials for that DB been changed. 

DB Reconnection tools complete succssesful.

as admins just make full copy of DB , 2 old profile DB appear on new server. then admins make another 2 entries in BSM Admin Profile DB Management ,pointing to new server DB.

no one do nothing with SESSION TABLE on new BD.

now we cant delete old profile DBs without wornings, nor start BSM when OLD SQL Server down.

also i cant edit SESION TABLE because i do not know hash of new password.

can anybody help me to fix this problem and move ALL Profile data to new Server? 

Please use plain text.
HP Expert
PatWest
Posts: 826
Registered: ‎03-06-2008
Message 2 of 4 (290 Views)

Re: Profile DB Migration issue BSM9.20.191

hi,

Did you follow this procedure before you started ?


Title:
BSM 9.x - how to move the database / change the database server without impacting the current configurations/customizations.

Document ID:



http://support.openview.hp.com/selfsolve/document/KM00378713
Please use plain text.
Frequent Advisor
scorpio131179
Posts: 74
Registered: ‎12-03-2009
Message 3 of 4 (285 Views)

Re: Profile DB Migration issue BSM9.20.191

thank you for advice.

migration have ben performed without me, but i belive that step 3 Update the SESSIONS table in the management database to reflect the new database server

never been completed because  of password change for new DB.

can you futher advice how can i update SESION tabe content if Profile DB been moved to another server but login  or\and password been changed to access to new DB?

Please use plain text.
HP Expert
PatWest
Posts: 826
Registered: ‎03-06-2008
Message 4 of 4 (270 Views)

Re: Profile DB Migration issue BSM9.20.191

hi,

 

It seems you have to clean up the mess now.

 

 

Manipulating such an important table via the forum now is too risky. You will need help from R&D via a support case here.

 

You will need to explain clearly what has been done, what is missing and what needs to be done/ is expected.

 

good luck,

PatW

 

 

Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation