Exalytics and Financial Reporting - WLS Console Shows Different Java Heap Setting Compared to EPM setCustomParamsFinancialReporting.sh
Last updated on MARCH 22, 2017
Applies to:Hyperion Essbase Administration Services - Version 188.8.131.52.000 and later
Oracle Exalytics Software - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Using EPM/Essbase version 220.127.116.11.500, as a managed WLS server with JDK160_29 on Exalytics. Recently increased java heap size in the setCustomParamsFinancialReporting.sh file in the EPM home as shown below:
With this change, the java heap is expected to be 16GB, yet the WLS console and Linux operating system show a lower than expected value (512 MB). Tested using the start.sh script in "/u01/app/oracle/product/EPM/Middleware/user_projects/epmsystem1/bin" to start all the services and also tried using WLS Console -> Server -> Managed server -> start. In all cases, the server starts successfully but the memory displayed in the WLS console and operating system is lower than what was set via the entries in the setCustomParamsFinancialReporting.sh file.
Why is the memory change not taking effect as expected?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms