Loading ca_site
The first thing what you need know: VERY Important! Using pdm_load can be destructive so always back up your database before you perform a pdm_load, and use pdm_userload unless instructed to use pdm_load.
Important! Make a backup copy of the database before running pdm_load with this option. After old database records are removed, you must restore the CA SDM database with this backup copy if you want to recover any deleted records, use pdm_extract for this procedure.
1. BACKUP
BACKUP COMMAND |
---|
pdm_extract ca_site > ca_site.txt |
2. Structure table
bop_sinfo -dq site |
---|
Factory site < ca_site > Attributes: id INTEGER UNIQUE producer_id LOCAL STRING(20) persistent_id LOCAL STRING(60) alias STRING(30) last_mod_by last_update_user STRING(64) last_mod_dt last_update_date DATE version_number INTEGER creation_date DATE creation_user STRING(64) name STRING(100) REQUIRED delete_flag inactive SREL -> actbool.enum REQUIRED exclude_registration INTEGER delete_time DATE contact contact_uuid SREL -> cnt.id SERVICE_PROVIDER_ELIGIBLE description STRING(255) |
Structure load: pdm_extract ca_site |
---|
TABLE ca_site alias contact_uuid creation_date creation_user delete_time description exclude_registration id inactive last_update_date last_update_user name tenant version_number { "" ,"" ,"06/15/2016 17:15:53" ,"ServiceDesk" ,"" ,"" ,"" ,"1000001", "0" ,"06/15/2016 17:19:11" ,"ServiceDesk" ,"My own site name" ,"" ,"1" }
|
3. Example
loading_cnt.txt - Content |
---|
TABLE ca_site name {"site.name"} |
pdm_load