What was the root cause for the 25.11 update being withheld from Production environments?
A few customers reported issues in their 25.11 test environments related to calculation accuracy and system slowness. These problems were specific to customizations within certain customer applications and were only observed sporadically across different customers.
Why did Oracle also decide to skip the 25.12 (December 2025) and 26.01 (January 2026) updates?
The year-end is a critical period for many customers’ business processes. Oracle deferred these updates to avoid any risk of disruption during this time, allowing additional time to fix reported issues and to validate future updates.Based on issues reported so far, what areas of the applications would Oracle recommend customers test to ensure Essbase 21c works well?
The Oracle Essbase 21c upgrade has no impact on these business processes:
- Narrative Reporting
- Account Reconciliation
- Enterprise Data Management
Oracle recommends customers investigate the following areas of their applications to ensure Oracle Essbase 21c does not have any cause for concern:
Overall Tests across Financial Consolidation and Close, Planning, Profitability and Cost Management, and Tax Reporting: Run all allocations, data loads, data exports, and reports and confirm that there are no regressions in results and no performance degradations.
Financial Consolidation and Close:
Performance Test:
Run Consolidate and Translate Rules: These rules in Essbase 21c should take a similar amount of time as it used to take in Essbase 11g when the same set of entities were calculated - especially if your insertion points use the Essbase functions
@CALCMODEand@EQUALin Hybrid Mode (SET HYBRIDBSOINCALCSCRIPT FULL).- Run On-Demand Rules: These rules in Essbase 21c should take a similar amount of time as it used to take in Essbase 11g when the same set of entities were calculated. Especially test ODRs using
@CALCMODEand@EQUALEssbase functions in Hybrid Mode (SET HYBRIDBSOINCALCSCRIPT FULL). - Data Retrieval: Test your ad-hoc grids, data forms, and reports in Essbase 21c. Retrievals should take a similar amount of time as it used to take in Essbase 11g.
- Data Integration: Test the same data integration exports using All Data mode and Replace Mode.
- Restructure Cube: This task in Essbase 21c should take a similar amount of time as it used to take in Essbase 11g when same cube was selected.
Data Integrity Test:
- Ad-hoc Data Comparison: Consolidated data retrievals on ad-hoc grids with Essbase 21c (Sheet A) with Essbase 11g (Sheet B) must tie out. Sheet A - Sheet B = 0.
- Data Exports (Dynamic and Stored Sparse Data): Data Integration Export using All Data mode for Essbase 21c must tie with Essbase 11g.
- Custom Member Formula Tests: Ratios/Statistical Analysis must match between Essbase 21c and Essbase 11g with the same Solve Orders.
- Run On-Demand Rules: These rules in Essbase 21c should take a similar amount of time as it used to take in Essbase 11g when the same set of entities were calculated. Especially test ODRs using
No comments:
Post a Comment