1. Installation and Configuration Troubleshooting Guide
  2. Essbase 21c
  3. Profitability and Cost Management

Profitability and Cost Management

Generation of CALC script duration has increased after ugrading to Essbase 21C.

Issue: You may notice an occasional increase in the total ledger computation duration after upgrading to Essbase 21C. When this increased duration is observed, running the Execution Statistics System Report will show a significant increase in the duration of the generation of calculation scripts for multiple rules. The root cause of the issue is a significant increased duration for the driver detection Essbase 21c MDX query.

Workaround:

  1. Run execution statistics report to confirm a significant increased duration of the generation of calculation scripts and identify a test rule for below.
  2. On the servers within the instances, shutdown all of the services including the Essbase Service.
  3. To test the workaround and apply the settings to your Essbase configuration, contact Oracle Support for the Essbase Settings.
  4. Restart all of the services.
  5. Run single rule calculation for the test rule identified within the original execution statistics report.
  6. Run execution statistics report to confirm reduced duration of the generation of calculation scripts for the test rule.

Note:

Essbase Config File Location: 
MIDDLEWARE_HOME/user_projects/domains/essbase_domain/config/fmwconfig/essconfig/essbase/essbase.cfg

DATACACHESIZE Error

Issue: Essbase LCM Import Job process fails with the following error message. 

Essbase Error(1006023): Data cache is full

Workaround: To resolve the issue, increase the size of the Data Cache within the Essbase 11g instance before re-importing the Essbase 11g cube into the Essbase 21c instance. To increase the Data Cache size to 100 MB, use one of the following procedures:

  1. Essbase Administrative Services
    1. Open the database properties for the Essbase Database with the error.
    2. Navigate to the Caches tab.
    3. Expand the Cache sizes tree node if required.
    4. Include the Data Cache setting (KB) to 102,400.
    5. Apply the changes.
  2. MaxL
    1. Use the StartMaxL or another tool.
    2. Issue the following MaxL command for each BSO application and HPCM Standard Application. 
      
alter database set data_cache_size 100MB

    Related Information: