LcmImport: Restore Cube Files
This CLI command restores cube artifacts from a Lifecycle Management (LCM) .zip
file. To do this, you must be the power user who created the application, or a service administrator.
Syntax
lcmImport [-verbose] -zipfilename filename [-overwrite] [-targetappName targetApplicationName] [-artifactlist artifactList]
Option | Abbreviation | Description |
---|---|---|
-verbose | -v | Optional. Show extended descriptions |
-zipfilename | -z | Name of compressed file containing backup files |
-overwrite | -o | Optional. Recreate the target application. |
-targetappName | -ta | Optional. Target application name, if you want it to be different from the source name. |
-artifactlist | -al | Optional. Name of the file containing the list of artifacts to import. This file can be generated from lcmexport.
To skip artifacts, comment out or delete entries from the list. For example, to skip importing audit records, comment out that line, as shown:
To control import order, rearrange the If –overwrite is used, the import operation deletes and recreates the entire application, importing only the artifacts present in the list. If –overwrite is not used, the import operation includes the artifacts specified in the list, without impacting any other artifacts already present in the target application. |
Notes
-
This command, like other CLI commands, can be used from outside the Essbase machine, whereas the LCM utility must be run within the Essbase machine.
-
When partitions exist between cubes being migrated, you must import the data source before the data target. Otherwise, partition definitions may not be restored.
Example
esscs lcmImport -z C:/Sample/Sample.zip -o -al C:/Sample/Sample.txt