CA Service Management

I have installed a SDM R12.5. I want to migrate my contacts to another system with SDM R14.1. SDM R14.1 is a clean system. I want to migrate my contacts with all datas (access type, dept, organization, location, job_title, VIP, roles, data partition, etc... etc...)

Someone know the order tables for pdm_extract and the load order with pdm_load?

it's the same case https://communities.ca.com/message/241798429#241798429 but with the contacts.

Best Regards.

Hi SoporteCAcma,

It`s necessary to looking for objects, we can do it on Technical Reference Guide,

However particularly I don't think to copy some tables is a good idea like - access type and data partition.

But ok,

How to Plan CA SDM Upgrades - CA Service Management - 14.1 - CA Technologies Documentation

Using the CA SDM Migration Console - CA Service Management - 14.1 - CA Technologies Documentation

However the database don't look for some keys it`s logical and the objects layer will looking for and you need maintain everything consistent.

about these tables (your comment)

1. ca_tenant
2. dept (ca_resource_department)
   • ca_tenant
   • act_bool
3. position (ca_job_title)
   • ca_tenant
   • act_bool
4. loc (ca_location)
   • ca_tenant
   • ca_contact
   • timezone
5. org (ca_organization)
   • tenant
   • act_bol
   • ca_contact
   • ca_company
   • ca_location
   • cost_center
   • svc_contract - service contract
6. cnt (ca_contact)
   • ca_tenant
   • act_bool
   • cost_center
   • ca_location
   • ca_resource_department
   • ca_organization
   • ca_job_title
   • acctyp (access type)
   • cmth (notification)
   • wrkshft
   • ca_company
   • service contract
   • timezone
   • noturg
   • currency_type

CA Service Desk Manager Known Upgrade Issues - CA Service Management - 14.1 - CA Technologies Documentation

CA Service Desk Manager Known Migration Issues - CA Service Management - 14.1 - CA Technologies Documentation

CA Service Desk Manager & Unicenter Service Desk 12.6_12.7 End of Service Announcement

Regards

Hi Macul.

I'm going to explain you my case and why I don't want to execute the migration procedure. My SDM current production environment is an update to R11.2 to r12.5. Too, my current production mdb has installed CA ITCM R12.5 and this product we go to install it in clean installation because is an update to R11.2 to R12.5. For this reason we want to begin with a clean environment in SDM R14.1. Then, we have installed the new environment in R14.1 and now we want to export datas from R12.5 to R14.1. We have to export the KT documents, no problem and now we want to export and import the rest of data (contacts, groups, org, loc, dept, prob_ctg, chgcat, status, macros, event, notification, workflow, etc...). I have never done an export and import manual, for this reason this asking for the order of export and import. There is very little documentation to do this. We don't use the tenant.

Can someone help me to do this?

Best Regards.

Technicaly if you remove all existing data and load the new the order should not be of big difference. pdm_load will not look if id that you are loading is not present on the system. Anyway i would backup everything and give a try

Hi Gutis,

the problem is that there is not documentation indicating what the extract/load order. I think the order is important.

Regards.

I think that order is not important at all, pdm_load will not lookup if reference id exist or not in the system, everything should work if you will load all referenced tables

1. You could also do the following principle...

Run the 'bop_sinfo -dq cnt | find "SREL"' command. Whatever tables that are returned, you need to make sure these are loaded first. Basically make sure all the tables that get referenced by the the cnt object have these records first before you reference them. The pdm_deref is the best for this sort of thing. So when you extract all these reference tables, omit the id's and then load the data onto your the new system, then use the pdm_deref. There are a few examples in the Technical Reference Guide you can use as your queue and take it from there if I'm not mistaken.

2. Word of caution. - There are not short cuts when it comes to this...You need to take into consideration is that there is serious manual labour involved in this. Also remember that if you just do a pdm_extract of the tables and then load them, whatever junk that was in these tables will also be take to your new system. Not sure you want to do this? So look also into an option of an additional step to do some data cleaning and make sure only the records you want on the new system are taken over and loaded. ;-)

That's my two cents...

Regards,

Brian