Application Elements - Supported or Unsupported

The following elements are supported or not supported for migration using the LCM utility.

Application Level

Migrated elements that are supported at the application level:

  • Application definition metadata (such as application type)

  • Calculation scripts

  • Excel worksheets

  • Macro-enabled Excel files*

  • Open XML Excel files*

  • Platform connections and datasources

  • Report scripts

  • Rules files

  • Shadow configuration for JAR (Java ARchive) files*

  • Substitution variables

  • Text files

* The asterisked application elements are supported only for Jagent-based deployments (11.1.2.4.5nn, 12.2.1 and later).

Database Level

Migrated elements that are supported at the database level:

  • Calculation scripts

  • Cube metadata (cube properties are required to create the cube)

  • Data (data is required to be moved to the correct location at the cube level for the cloud service)

  • Database transaction ID*

  • Drill-through definitions

  • Excel files

  • Filter definitions

  • Location aliases

  • Macro-enabled Excel files*

  • Open XML Excel files*

  • Outline

  • Transparent partitions

    Note:

    When partitions exist in the source between a source application and database, and a target application and 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.

  • Replciated partitions

  • Report scripts

  • Rules files

  • Scenario management

  • Substitution variables

  • Text files

* The asterisked database elements are supported only for Jagent-based deployments (11.1.2.4.5nn, 12.2.1 and later).

Server Level

Migrated elements that are supported at the server level:

  • Connections and datasource

    Note:

    You can migrate global or server-level connections and datasources by adding the optional argument: –include-server—level (or –isl) to LCM import or export operations.

Security

Users must be exported and imported separately before security elements are imported. See Migrating Cloud Service Applications.

The following security elements are exported and imported as part of the LCM utility.

  • User calculation scripts

  • User filter definitions

  • User roles (supported only for migration across Oracle Analytics Cloud - Essbase deployments and releases)

Unsupported Elements

The following elements are not supported for migration:

  • @XREF function formulas

  • Application logs

  • Catalog server

  • Disk volume definitions

  • Linked reporting objects

  • Linked and federated partitions

  • Server-level custom-defined functions and custom-defined macros

  • Server-level essbase.cfg file

  • Server-level substitution variables

  • Tablespaces

  • XML files