Migrated Essbase 11g Artifacts
The following table describes which global, application-level, and cube-level Essbase artifacts you can migrate from Essbase 11g On-Premise, using the 11g LCM Export Utility. A .zip file, created by the 11g LCM Export Utility, contains the artifacts of the exported application.
Note:
After upgrading EPM applications to Essbase 21.5, you can’t provision members to calculations or filters from EPM Shared Services console. You must use the Essbase Web Interface to assign members. See topics: Assigning Filters in Database Administrator’s Guide for Oracle Essbase, and Access to Calculations in Using Oracle Essbase.| Artifact | Supported for migration | Exceptions/Comments |
|---|---|---|
| Application and cube metadata | yes | Application metadata includes application type and settings. Cube metadata includes cube properties and settings. |
| Calculation scripts | yes | Application- and cube-level calculations are migrated. To see the calculation scripts, you must move application-level scripts to the cube level using the file catalog. If users and groups are already migrated before importing the application, then User/Group - Calc associations would also be imported. |
| Custom-defined functions and custom-defined macros | no | Any Jar files used by Custom-defined functions must be manually migrated. |
| Data | yes | To be migrated, data must be in the cube directory in the file catalog. |
| Disk volumes | no | Disk volume definitions are not applicable. |
| Drill through definitions | yes | - |
| Excel workbooks and files | yes | - |
| Filters | yes | Cube-level filters and user-created filters are migrated. If users and groups are already migrated before importing the application, then User/Group - filter associations would also be imported. |
| Linked Reporting Objects (LROs) | no | - |
| Location aliases | no | Location aliases are migrated with the cube. LCM doesn't support Location alias credentials migration. After you migrate your applications from 11g you must replace your location aliases. See Location Aliases section in Prepare to Migrate From Essbase 11g. |
| Log files | no | - |
| MDX Reports | no |
MDX scripts, triggers, and macros are not supported for migration from 11g Essbase, and therefore are NOT migrated, and not upgraded to Essbase 21c in EPM. |
| Outlines and formulas | yes | - |
| Partitions | yes |
Replicated and transparent partitions are migrated. Only partition definitions from the target cube are exported to the file system. When migrating the partitioned cubes, you must import the source cube before the target cube; otherwise, partition definitions may not be restored. |
| Report scripts | yes | Report scripts are migrated at both application and cube levels. |
| Rule files, text files, .csv files | yes | Application- and cube-level files are migrated. |
| Scenarios | no | LCM export operations and Migration Utility export do not support migration of scenarios for applications. |
| Substitution variables | yes | Application- and cube-level substitution variables are migrated. Server-level substitution variables are migrated if you use the optional –include-server-level option.
|
| Users | no | - |
| User roles | - | User roles are migrated if you use the -exportepmroles option.
|