New to 11.1.2.2 (103 Patch), and a replacement for some of the previous options in 11.1.2.1 and older, there are options for LCM migrations. These options, while documented in the LCM Guide from Oracle, are often overlooked. However, not setting these options can have significant impact to your migration processes, often without you even knowing.
To access these options, open the Shared Services portal (or tab). Select Administration > Migration Options:
(click to enlarge)
In the new tab, you will see similar options to those below, depending on which products you have installed:
These are global options that can be set at any time, and do not require a restart or reconfiguration of Hyperion. Most of the options are self-explanatory. For this session, I will be focus on one of the options related to migrating Essbase artifacts.
Essbase Application – Overwrite Artifacts
This option controls whether the imported objects (Essbase outlines, load rules, calc scripts, etc.) are overwritten, or, if they already exist, left in their current state. If this option is set to ‘No’ then the objects will be only be imported if they are new to the target environment, and there will be no easy way to tell this occurred without testing/verification, or reviewing log files. The LCM import will still complete successfully.
In the following examples I am using the Essbase sample application ‘Demo’ and the cube ‘Basic’ on a Windows server using EPM 11.1.2.4.
Below is a log entry showing the execution:
[2016-06-22T11:43:27.070-05:00] [FoundationServices0] [NOTIFICATION] [ESBLCM-30074] [oracle.EPMLCM.ESB] [tid: 43] [userId: <anonymous>] [ecid: 00i_7QagIlJFw0zkbz0BNz417_i1zdIyR0001IS000MSj, 0:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1 :1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1: 1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1 :1] [APP: SHAREDSERVICES#11.1.2.0] [SRC_CLASS: com.hyperion.essbase.lcm.migration.EssbaseImportExportEngine] [SRC_METHOD: importFileObject] 0_11 Object Demo : Basic : Basic (type= 1 , Outline ) already exists on server.
[2016-06-22T11:43:27.071-05:00] [FoundationServices0] [NOTIFICATION] [ESBLCM-30094] [oracle.EPMLCM.ESB] [tid: 43] [userId: <anonymous>] [ecid: 00i_7QagIlJFw0zkbz0BNz417_i1zdIyR0001IS000MSj, 0:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1 :1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1: 1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1:1 :1] [APP: SHAREDSERVICES#11.1.2.0] [SRC_CLASS: com.hyperion.essbase.lcm.migration.EssbaseImportExportEngine] [SRC_METHOD: importFileObject] 0_11 Object in application Demo : Cube Basic : Basic (type= 1 , Outline )is present at target and is not overwritten
The log containing these entries can be found on your foundation server, in EPM_ORACLE_INSTANCE\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\essbase\lcm\essbaseplugin.log
So, without manually verifying the objects migrated are updated from the source environment, or reviewing the above log, there isn’t any indication the import action did not import these Essbase objects. There are scenarios where having “Essbase Application – Overwrite Artifacts” set to ‘No’ would make sense though. One such scenario would be promoting an Essbase application from Development to Production. In this scenario, you may want to have only new objects imported, while maintaining the existing objects. Particularly if you have updates that occur directly in production, such as routine outline updates.
Unless you have a scenario where you want to keep existing objects in their preserved state, I would recommend changing the “Essbase Application – Overwrite Artifacts” to ‘Yes.’
LCM import script option
You have one other way to set this option if you are scripting your LCM imports. Modify your import XML definition file (default is Import.xml), adding the below entry:
<Options option=”overWriteArtifact” Value=”false”/>
So, for the Essbase application Demo Basic cube, the definition would look like below:
The full LCM import script would look like the following:
C:\Oracle\Middleware\user_projects\epmsystem1\bin\Utility.bat C:\Oracle\Middleware\user_projects\epmsystem1\import_export\DEMO\ESB-Demo\Import.xml
If you are not using LCM scripting for imports, or/and wish to always have the objects over write, I recommend setting the “Essbase Application – Overwrite Artifacts” to ‘Yes.
Free eBook Download
In the eBook “Having a Conversation with Data”, learn what the current BI infrastructure has been and associated challenges with the traditional approach. How important the user experience is in order to best maximize data’s value (think visualizations!!) to your organization and how to gain a competitive advantage with modern analytics platforms.
