Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 6 · Reports at scale: scheduling, delivery, performance
Volume: when the extract stops fitting
Lesson 59 of 177 · 2 min
Three ceilings, and each forces a different redesign. The exact numbers move between releases, so learn the shapes rather than the figures. ROW LIMITS. Interactive tools cap what they will return, and an extract that grows past the cap stops returning everything — sometimes with a warning, sometimes with a truncated result. A truncated extract that reports success is the worst outcome available here, so check the row count against an independent count rather than trusting the file. OUTPUT SIZE. A large PDF is expensive to render and awkward to deliver; a large delimited file is neither. Where output is going to another system, choose a format whose size is proportional to the data rather than to the layout — and PDF for machine consumption is a decision to revisit, not a default. TIMEOUTS. A long-running request is eventually stopped, and the redesign is either less work per run or…
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 6 · Reports at scale: scheduling, delivery, performance
- 1The scheduler, and what a job really is
- 2Scheduling patterns that survive
- 3Delivery: email, FTP and content server
- 4Knowing a scheduled report failed
- 5Volume: when the extract stops fitting
- 6Incremental extracts and high-water marks
- 7What breaks: the 2am report
- 8Lab briefing · Schedule, deliver, and prove it ran