Loading data with the pdm_load utility into an object that is linked to more than 1 table creates UUID conflicts.
book
Article ID: 53016
calendar_today
Updated On:
Products
CA IT Asset ManagerCA Software Asset Manager (CA SAM)ASSET PORTFOLIO MGMT- SERVERSUPPORT AUTOMATION- SERVERCA Service Desk Manager - Unified Self ServiceKNOWLEDGE TOOLSCA Service Management - Asset Portfolio ManagementCA Service Management - Service Desk Manager
Issue/Introduction
Description:
Loading data through pdm_load into the ca_contact and the usp_contact.
Solution:
Example with ca_contact and usp_contact:
Create a load file for ca_contact with the relevant user. E.g. file1.txt TABLE ca_contact { "" ,"" ,"" ,"" ,"sonia.pires" ,"" ,"" ,"","pires" ,"0" }
Load this user... pdm_load -v -i -f file1.txt
Extract the uuid from ca_contact table and divert the output into a file. pdm_extract -f "select id from ca_contact where last_name='pires'" >p.txt
Edit the p.txt file... TABLE ca_contact id { "BBAE5BC462180E469FE39E6B2B1B66A8" }
Modify the text and add the extra fields you want to include into the usp_contact table and change the ca_contact to usp_contact TABLE usp_contact id c_acctyp_id { "BBAE5BC462180E469FE39E6B2B1B66A8" , "2405" }
Save the above.
Load the newly modified p.txt file.. pdm_load -v -f p.txt NOTE1: do not use the -i option in here.
NOTE2: Running pdm_cache_refresh during normal production hours isn't advisable.
Refresh the table data so that the domsrvr picks up the changes.. pdm_cache_refresh -t ca_contact No need to run pdm_cache_refresh against the usp_contact table