Import Object Data

You can import a data object using the Command Line interface.
casm173
You can import a data object using the Command Line interface.
Follow these steps:
  1. Log in to the CA SDM target system as an administrator.
  2. Create a backup of the existing database.
    If the import fails, restore the database from the backup location.
  3. Manually copy the exported zip file,
    sdmp_db_data_export_yymmdd_hhmmss.zip,
    from the source system to target system.
  4. Execute the following command to validate the object schema (number of xml files, table names, and column names) in the target system and follow the on-screen instructions.
    db_promote import -v -p <path_to_the_zip_file>
    For example:
    db_promote import -v -p c:/temp/sdmp_db_data_export_151008_102754.zip
  5. The command line options are described as follows:
    -p
    Specifies the import package name.
    -u
    (Optional) Performs the import using the specified user name.
    -h
    (Optional) Denotes the help for a command.
    -v
    (Optional) Validates the schema.
  6. Execute the following command to import the object data:
    db_promote import -p Path_to_the_zip_file
    db_promote import -p Path_to_the_zip_file -u <sdm contact userid>
    For example:
    db_promote import -p c:/temp/sdmp_db_data_export_151008_102754.zip
  7. Verify the import status by accessing Administration, System, Data Export/Import History in the CA SDM User Interface and refer the following report files generated at the
    NX_ROOT/log
    location:
    • dbimport.dryrun.report.<timestamp>
      : The DryRun report validates all the object schema. Schema related issues, if any, are listed here.
    • dbpromote.log
      : This file contains logs for the export/import operation.
    • Failure_Report_<package ID>_<timestamp>
      : This file contains object data failures that were encountered during import.
    • Imported_Object_Report_<package ID>_<timestamp>
      : This file contains the successfully imported object data related information.
    • <export_import_path>/Promotion/Import/DB/Import_report_<package name>_<timestamp>
      : This file contains the consolidated import summary.
The
DBImport.properties
file is available
in the NX_ROOT/pdmconf/
location, which contains all configurable variables for object data import utility (db_promote). Configure this file to customize as per your environment requirements. This property file includes the following:
  • temp.work.area
    Specifies where import extracts the exported package. If it is empty or undefined, it uses the system temp folder provided by jvm.
    For example, temp.work.area=c:\\mywork\\temp
  • domsrvr.default=domsrvr
    Specifies the default dom server used for the data import process. Update the value if there are multiple dom servers.
    For example: domsrvr.default=domsrvr:02
Behavior of Abort in Import
We recommend that you do not abort the import process. The following scenarios explain the impact of Abort during the Import process.
Scenario 1
: When the user closes the Command Line interface or selects the Ctrl+C key during the import process.
The status gets updated as
Aborted
in the database. In this scenario, the data import is partial, which can cause the CA SDM application to be in an inconsistent state.
Scenario 2
: When the user clicks the
Abort
button on the
Administration
,
System
,
Data Export/Import History
page during the import process.
The status gets updated as
Aborted
in the database. The process keeps running on the server until the process is complete.
Using the Abort button from the UI updates
only
the status as Aborted in the database and allows you to execute another process. Typically, you must abort an import process from the user interface when it terminates abruptly.