Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 5 · OTBI and subject areas
Performance and the analysis nobody can run
Lesson 52 of 177 · 2 min
The analysis nobody can run is almost always one of three shapes, and all three work perfectly for the person who built them. ONE: an unfiltered date range. No period filter means every transaction ever recorded, and it is the default state of an analysis somebody built by dragging columns. It works in a fresh test environment with four months of data and fails in a production estate with nine years. TWO: a high-cardinality column on the display. Invoice number, transaction id, employee name at the detail level — each one turns an aggregate into a list, and a list of two million rows is not an analysis, it is an export somebody will cancel. THREE: your own data volume. The analysis you tested against a subset behaves differently against ten times the rows, and the difference is rarely linear — it is fine, fine, fine, then a timeout. The…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Fusion Technical: Reports, Data, Integrations and Extensions, with a certificate on completion and a fourteen-day refund window.
In this module: Module 5 · OTBI and subject areas
- 1What a subject area is
- 2Finding the right subject area
- 3Building an analysis
- 4Joins across subject areas, and when you cannot
- 5Calculations, bins and hierarchies
- 6Dashboards and prompts
- 7Security in OTBI: it is already applied
- 8Real-time versus reported figures
- 9Performance and the analysis nobody can run
- 10When OTBI is the wrong answer
- 11Lab briefing · An analysis and a dashboard