Migrating to new Database server.

[Anon Anon]

Hello All,

 

Our Database folks are needing to move our current production MDB to a new server.

Is there anything else I should take in to consideration other than running 'pdm_configure' and changing the server host?

 

Thanks in advance.

[Chi Chen]

After move the mdb to new server, you would need to make sure ServiceDesk user is created, and it has sysadmin role, then run the procedure  sp_change_users_login 'AUTO_FIX','ServiceDesk'. Once all these are done,

then for SDM versions before 12.9, you can run pdm_configure from SDM primary side to point to the new mdb server.

For 12.9,   before you run pdm_configure, you would need to follow the steps in tech doc TEC613359. For your conveience,

I copy it here for you:"

Tech Document
Title:  Unable to run pdm_configure after copying an MDB from a Production Environment to Development or Test Environment

Description:

Whether building out a new Service Desk Manager 12.9 Test/Dev system, or refreshing the data on an existing Service Desk Manager 12.9 Test/Dev system by copying the MDB from Prod to Test/Dev, when you try to run pdm_configure after the MDB restore it will fail with an error stating: "Already following servers are using same Database: server-name-of-system-where-mdb-came-from. Make these servers as Inactive to proceed."

Solution:

Using either SQL Management Studio, or SQLPlus (or any other db mangement tool) for Oracle, set the value of the "del" field on all rows in the usp_servers table to have a value of "1".

Then run pdm_configure on the Primary or Background server.
This will add that server (which you ran pdm_configure on) to the usp_servers table.
If you your Test/Dev environment has Secondary servers, or if you are using Advanced Availability, you will now need to log into Service Desk Manager on the Primary or Background server and re-add any Secondary servers, or Standby servers and App servers that you have in your Test/Dev environment.

Next, you will need to edit the configuration that is being used to ensure you have the appropriate daemons configured on each of those servers.

Once you have completed the server configuration, you will then need to run pdm_configure on any Secondary servers, or Standby servers and App servers that you have in your Test/Dev environment.

"

Here Test/Dev simply means from one install to another.

Hope this helps. Thanks _Chi

 

[Ana Katherine Blanco]

Hello, your suggestion can be done from a mdb 14.1 to mdb 17.3??

------------------------------
Ana KBS
------------------------------

[Paul Coccimiglio]

Ana..........

The documentation for moving the MDB database can be located at:

SDM 14.1

https://techdocs.broadcom.com/language-masters/en/ca-enterprise-software/business-management/ca-service-management/14-1/implementing/how-to-move-the-ca-mdb-data-from-the-source-to-the-target-systems.html

SDM 17.3

https://techdocs.broadcom.com/us/en/ca-enterprise-software/business-management/ca-service-management/17-3/administering/moving-the-ca-mdb-data-from-the-source-to-the-target-systems.html

Note that you cannot use a SDM 14.1 MDB with SDM 17.3.  The MDB needs to be upgraded as part of the SDM 17.3 upgrade process.

------------------------------
Paul Coccimiglio
------------------------------