Resolving Essbase Configuration Issues

In case of Essbase Configuration failure, perform the following steps:

  1. Table 11-3 Check Export Status

    Step Details
    Check if export operation is successful
    1. Navigate to the following path to verify export status
      MWH\EPMsystem11R1\common\utilities\EssbaseLCMUtility\EssbaseUpgradeStatus.xml

    2. Within the <task> tag in EssbaseUpgradeStatus.xml, confirm the message:

      <message>Essbase applications are exported successfully</message>

    1. Table 11-4 If Export has failed

      Step Details
      Possible Reasons
      • OPMN startup issue
      • /tmp space issue
      • Drive space issue
      • Application size greater than 40 GB
      Review Essbase 11.1.2.4 if Essbase has failed due to /opmn issue. Review essbaseupgrade.log 
      [2024-09-03T19:28:57.078+02:00] [essbase] [ERROR] [] [oracle.essbase.lcm.essbaseupgrade] [tid: 1] [ecid: 0000P6svfFbAXNt_kdH7iZ1apoTP000001,0] [SRC_CLASS: oracle.essbase.lcm.essbaseupgrade.UpgradeMessageHandler] [SRC_METHOD: errorMessage] Error: Oracle Home is not valid: C:\Oracle\Middleware\EPMSystem11R1 [2024-09-03T19:28:57.078+02:00] [essbase] [ERROR] [] [oracle.essbase.lcm.essbaseupgrade] [tid: 1] [ecid: 0000P6svfFbAXNt_kdH7iZ1apoTP000001,0] [SRC_CLASS: oracle.essbase.lcm.essbaseupgrade.UpgradeMessageHandler] [SRC_METHOD: errorMessage] Error: Oracle Instance is not valid: C:\Oracle\Middleware\user_projects\epmsystem1

      Workaround:

      Fix the OPMN Startup issue before proceeding with Essbase 21c configuration.

      Review Essbase 11.1.2.4 if Essbase has failed due to the /tmp space issue. Review essbaseupgrade.log
      [2024-02-29T22:50:44.483+00:00] [essbase] [ERROR] [] 
[oracle.essbase.lcm.essbaseupgrade] [tid: 1] [ecid: 0000Orr3Cnm7IB4MRUN6EP1_sG_f000001,0] [SRC_CLASS: oracle.essbase.lcm.essbaseupgrade.UpgradeMessageHandler] [SRC_METHOD: errorMessage] Error [/Databases/MAIN,Data]:Cannot get olap file object. Essbase Error(-1): No space left on device

      Workaround:

      1. Upgrade to Version 11.2.15. See Upgrade to EPM 11.2.15 Essbase Configuration Failed due to ‘temp’ Space Issues’ (Doc ID 3018481.1) for more details.
      2. Increase /tmp size nd drive space. See Impact of Essbase 21c on EPM 11.2.15 for more details.

    2. Table 11-5 Create Database Schema Failure: Analysis

      Step Details
      Verify the Export success Review the file EssbaseUpgardeStatus.xml and check 
      MWH\user_projects\epmsystem1\diagnostics\logs\config\configtool.log
      1. Search for: "Printing all variables".
      2. Scroll down to identify the possible reason for the failure.
      Review: Phase - Create Database Schemas Failure Error in configtool.log file as shown below:
      Name:ADMIN_SERVER_PORT, value:7010
Name:ADMIN_USERNAME, value:epm_admin
Progress is started
Phase Create Database Schemas is in status IN_PROGRESS
Phase Create Database Schemas is in status FAILED
      Action Verify if RCUSchema.properties is updated properly.
      Possible reasons
      1. Sysdbuser does not have the required privileges to create RCU schema for Essbase.
      2. dburlEssbase is not updated correctly in RCUSchema.properties file.
      3. SchemaPrefixEssbase can have a maximum of 12 alphanumeric characters
      4. rcuPassword can only support special characters: $ # _
      5. EPM Admin password must not include characters other than $ # _

  2. Table 11-6 Create Database Domain Failure: Analysis

    Step Details
    Review: Phase - Create Domain failure Error in configtool.log file as shown below:
    Name:ADMIN_SERVER_PORT, value:7010
Name:ADMIN_USERNAME, value:epm_admin
Progress is started
Phase Create Database Schemas is in status IN_PROGRESS
Phase Create Database Schemas is in status PASSED
Phase Create Domain is in status IN_PROGRESS
Phase Create Domain is in status FAILED
    Problem Ensure that Essbase is properly installed and the Essbase OPatch has been successfully applied.
    Action Try reinstalling Version 11.2.15 and follow the below doc before attempting Essbase21C configuration Document 3027269.1
    Possible reason Essbase OPatch has failed.
    .