What tables would need to be backed up when use swing box method Service Management upgrade

Products

• CA Service Management - Service Desk Manager

Issue/Introduction

When upgrade Service Management applications use swing box method, one step before restore mdb database from source is to back up some mdb tables and this tech doc gives a list of tables to be backed up.

Environment

Release : 17.3

Component : SERVICE DESK MANAGER

Resolution

Common tables:

al_cdb_comp_installstate_bkup
al_cdb_componentinstallstate
al_cdb_config_params_backup
al_cdb_configurationparameters
al_cdb_files
ca_application_registration

Service Desk tables:

options
usp_servers
sapolicy
ci_mdr_provider
usp_domsrvr
usp_configuration
usp_webeng_alias
usp_webeng_domsrvr
usp_webengine
object_promotion (applicable only if CA Service Management 14.1.02 is installed)
promo_hist (applicable only if CA Service Management 14.1.02 is installed)

Service Catalog tables:

usm_configuration

CA APM tables:
al_meta_binary_store
al_process_account
the following CA APM tables, if you have CA Service Management14.1.02 installed in your system:
al_apmp_def
al_apmp_operation
al_apmp_content_types
al_apmp_progress_status
al_apmp_record_filter
al_apmp_run_stage

CA xFlow Interface tables:
l1admin_general_config

CA  Search Server tables:
usp_es_servers