You can use the LCM (Lifecycle Management) utility, for Windows or Linux, and the Command-Line Interface (CLI) tool to migrate your source application and elements across Oracle Analytics Cloud - Essbase deployments and releases.
The process flow involves exporting the application to a zip file and then importing the
.zip file to the target deployment or release.
If you are migrating across Oracle Analytics Cloud - Essbase deployments and releases, from v17.3.3 (or earlier), use the scripts for migrating to Essbase, as described in the section, Scripts for Administration Tasks in the Administering Oracle Analytics Cloud document. This also applies to export and import of provisioning of application roles and scripts across these deployments.
In the cloud service, all applications must be in Unicode. Therefore, Essbase on-premises applications must be manually converted to Unicode before exporting them to a
Only transparent partitions are supported by the utility. Federated or linked partitions are not supported.
During LCM/CLI import, if scenarios are present in the exported
.zipfile, but you do not provide scenario database details, then import of scenario management data is bypassed.
Restoring an application or database from a prior backup, after the application or database was re-created using LCM import, is not supported.
For information on downloading the LCM command-line utility and for use cases, see Application Migration and Use Cases.
The required user roles are as follows:
- For exporting: Application manager for the application created. In addition, the following can use the LCM utility and CLI tool: Service administrator for all applications; Power user for all applications created by the Power user.
- For importing: Power user or Service administrator, for creating new applications during import.
Exporting an On-Premises Application from the Source
- Run the LCM utility.
- At the LCM utility command prompt, enter the following command syntax to export the application to a .zip file:
export -server essbasehost:port -user username -password password -application appname -zipFile zipfilename [-nodata] -scenario -dbhost database_hostname -dbport database_port -dbname db_servicename -dbusername bi_platform_dbusername -dbpassword bi_platform_dbuser_password -restUrl http://host:port/essbase
Note:The prior arguments
-zipfile) can be specified in any order. To prompt for a password, do not include the
-password passwordoption. To skip the export of cube data during export, specify
-nodata, which is an optional argument). By default, all cube data is exported. All of the options in the command (from
-scenarioonward, which are the database details) are optional; provide them only if you want to migrate scenarios along with other elements in an application.
Exporting a Cloud Service Application from the Source
- Run the CLI tool to export the cloud service application to a
- Follow the instructions as described in Oracle Analytics Cloud - Essbase Command-Line Interface (CLI)
Importing an On-Premises or Cloud Service Application to the Target
When partitions exist in the source between a source application or database, and a target application or database, only partitions from the target are exported to the file system.
When partitions exist between cubes being migrated, you must import the data source before the data target. Otherwise, partition definitions may not be restored.
- Run the CLI tool to import the Essbase on-premises application from the
.zipfile to the target.
- Follow the instructions as described in Oracle Analytics Cloud - Essbase Command-Line Interface (CLI).
Migrating Applications and Cubes from Financial Consolidation and Close Cloud Service or Planning and Budgeting Cloud Service
- Export from Planning and Budgeting Cloud Service (PBCS) or Financial Consolidation and Close Cloud Service (FCCS) using the PBCS interface, or the EPM Automate Utility command line tool using
exportsnapshot. See EPM Automate Utility Commands in Working with EPM Automate for Oracle Enterprise Performance Management Cloud.
- Run the CLI tool to import the Essbase application and cubes from the PBCS
.zipfile using CLI command
lcmimport, as described in LcmImport: Restoring Cube Files.