Is it possible to extract and load CA Service Desk (CA SDM) Group information from one environment to another?


Article ID: 17473


Updated On:


CA IT Asset Manager CA Software Asset Manager (CA SAM) ASSET PORTFOLIO MGMT- SERVER SUPPORT AUTOMATION- SERVER CA Service Desk Manager - Unified Self Service KNOWLEDGE TOOLS CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager



There may be a requirement for a given set of group contacts to be brought over from one server to another.  This document discusses how to perform such an action.


To extract and load CA SDM Group information between CA SDM environments, will need to extract the CA_CONTACT table and the USP_CONTACT table.

CA _CONTACT is the main contact table which is shared among other CA solutions, whereas USP_CONTACT is within CA SDM.

Furthermore, since you only want to extract Groups, will need to filter the PDM_EXTRACT statement based on the field 'ca_contact_type'. The group ID for this field OOTB is 2308 (name: GROUP).


pdm_extract -f "select * from ca_contact where contact_type = '2308'" > ca_contact_groups.txt

Sample of contact of CA_CONTACT_GROUPS.TXT

TABLE ca_contact  admin_organization_uuid alias alt_phone_number alternate_identifier comment company_uuid contact_type cost_center creation_date creation_user delete_time
department email_address exclude_registration fax_number first_name floor_location  id inactive job_function job_title last_name last_update_date last_update_user location_uuid mail_stop middle_name mobile_phone_number organization_uuid pager_email_address pager_number pri_phone_number room_location supervisor_contact_uuid tenant tenant_group userid version_number
{ "" ,"" ,"" ,"" ,"" ,"" ,"2308" ,"" ,"09/07/2014 12:21:19", "ServiceDesk" ,"" ,"" ,"" ,"" ,"" ,"" ,"", "D978897598C70441A1711F0851BD6D0E" ,"0" ,"" ,"" ,"AppGroup", "09/07/2014 12:21:42" ,"ServiceDesk" ,"" ,"" ,"" ,"" ,"" ,"" ,"" ,"" ,"","", "" ,"" ,"" ,"1" }


Sample of content of USP_CONTACT_GROUP.TXT

TABLE usp_contact  c_acctyp_id c_available c_cm_id1 c_cm_id2 c_cm_id3 c_cm_id4 c_domain c_email_service c_nx_ref_1 c_nx_ref_2 c_nx_ref_3 c_nx_string1 c_nx_string2 c_nx_string3 c_nx_string4 c_nx_string5 c_nx_string6 c_parent c_schedule c_service_type c_timezone c_val_req c_vendor c_ws_id1 c_ws_id2 c_ws_id3 c_ws_id4 confirm_save id integration_cnt ldap_dn sap_personID
{ "" ,"" ,"" ,"" ,"" ,"" ,"" ,"" ,"" ,"" ,"" ,"" ,"" ,"" ,"" ,"" ,"" ,"", "" ,"" ,"" ,"" ,"" ,"" ,"" ,"" ,"" ,"0","D978897598C70441A1711F0851BD6D0E", "0" ,"" ,"" }

Now that both the CA_CONTACT and USP_CONTACT table information has been extracted for the group, the files generated (CA_CONTACT_GROUPS.TXT and USP_CONTACT_GROUP.TXT in the example above) can be loaded via the PDM_LOAD command(i.e. pdm_load -f CA_CONTACT_GROUPS.TXT and pdm_load -f USP_CONTACT_GROUP.TXT)

Additional Information:

See also:

pdm_load errors out with a valid load file, and SQL error "FOREIGN KEY SAME TABLE constraint" in stdlogs.


Release: SDMU0M99000-14.1-Service Desk Manager-Full License