We recently upgraded to Hyperion 11.1.2.4 and updated our HFM servers in Dev/QA/Prod to 11.1.2.4.205 patch level.
In order to bring my HFM application from 11.1.2.2 to 11.1.2.4, below are the steps we followed:
1- Run app copy on Dev 2.4 server using UDL from HFM 2.2 as source and Target HFM 2.4 UDL
2- Then run EPM system configuration on HFM 2.4 Dev server and select the option "Upgrade Applications from Earlier Release"
3- Then open the HFM 2.4 Dev Consolidations screen, register the app, provision the user and then the user can login
4- Run the app copy from Dev 2.4 to QA 2.4 and then QA 2.4 to Prod 2.4,
since the app that was copied from 2.2 release is now in 2.4 format
This blog is dedicated to Oracle Hyperion EPM Technical Architecture and Support tips.
Tuesday, September 12, 2017
Essbase Cloud and ESSCLI utility
http://docs.oracle.com/en/cloud/paas/analytics-cloud/essug/cli-command-reference.html
For all Essbase Cloud related commands and how to use the new utility.
For all Essbase Cloud related commands and how to use the new utility.
Monday, September 4, 2017
Hyperion Smart View and Diagnostics toolbar
With the new Smart View 11.1.2.5.x release, there is a new Diagnostics toolbar functionality introduced to gather user input and view errors faced during Smart view functions.
To enable the functionality goto;
To enable the functionality goto;
SmartviewàOptionsàAdvancedàShow
Diagnostics Group on Smart View Ribbon
You will notice the Start/Stop Diagnostics buttons get
enabled
You have various options to Mask Data or Members, and what
you should send as errors…..
Log files are saved in this folder C:\Users\username.domain\AppData\Roaming\Oracle\SmartView\Diagnostics
Once done, then click on Stop Diagnostics and click on Clear
Diagnostics Folder to clear the data logs.
Wednesday, June 28, 2017
Essbase Release 11.1.2.4.000 Patch Set Update (PSU): 11.1.2.4.018
Essbase Features No Longer Supported in this Release
Delayed freespace recovery is no longer supported:
· MaxL statement: alter database recover freespace
· Oracle recommends using the alter database force restructure statement.
· Configuration setting: DELAYEDRECOVERY
DRM Hyperion 11.2.x release updates from Kscope17
VERSION SUPPORTED UNTIL
11.1.2.3.x Mar 2018
DRM
11.1.2.4.x DEC 2020
DRM
11.2.x DEC 2030
New certifications expected in 11.2.x:
- FMW 12
- Java 8, (JDK 1.8)
Third party:
- Windows server 2016
- SQL Server 2014, 2016
- Chrome and edge browsersTuesday, June 13, 2017
HFM MaxNumCubesInRAM settings...now in Workspace
MaxNumCubesInRAM
This setting controls the number of cubes that are held in memory at any given time. The number of cubes in memory is checked when either of the two conditions NumMinutesBeforeCheckingLRU or NumCubesLoadedBeforeCheckingLRU is reached. Lowering this setting can alleviate high memory usage for sparse applications (applications with many entities, but relatively few records per entity).
This setting affects all data operations including consolidations and data retrievals.
Range: 100-500,000 - Default value: 60,000
Below is a screen shot of where you can find this setting in the new release 11.1.2.4
Navigate to Administer, Consolidation Administration, then expand Admin Tasks and then Settings.
Thursday, May 4, 2017
Planning performance for Business Rules and Calc Scripts
Recently, we migrated some BR and Calc Scripts from an older release 11.1.1.3 to 11.1.2.4 and some of the performance settings needed to be tuned.
One of the ones i came across was the I/O Access Mode and Data Compression settings to improve performance. Check that compression settings are still present.
In EAS, expand the application and database. Right-click on the database > Edit > Properties > Storage tab. Check that your "Data compression" is not set to "No compression" and that "Pending I/O access mode" is set to "Buffered I/O".
Sometimes the compression setting can revert to "no compression", causing the rapid growth of the data files on disk.
One of the ones i came across was the I/O Access Mode and Data Compression settings to improve performance. Check that compression settings are still present.
In EAS, expand the application and database. Right-click on the database > Edit > Properties > Storage tab. Check that your "Data compression" is not set to "No compression" and that "Pending I/O access mode" is set to "Buffered I/O".
Sometimes the compression setting can revert to "no compression", causing the rapid growth of the data files on disk.
Subscribe to:
Posts (Atom)



