Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 6 · Reports at scale: scheduling, delivery, performance
The scheduler, and what a job really is
Lesson 55 of 177 · 2 min
An Enterprise Scheduler job is a definition, not a run. The definition says what to execute and what parameters it takes; each execution is a request, with its own id, its own parameters, its own log and its own status. A SCHEDULED REPORT IS A DIFFERENT OBJECT FROM THE ONE YOU RAN BY HAND, and that is the sentence that prevents a whole family of confusion. When you run a report interactively, the parameters come from you and the output comes back to your screen. When it runs on a schedule, the parameters come from the SCHEDULE, the identity comes from whoever submitted it, and the output goes to a delivery destination — three different sources, none of them you at 2am. The queue is shared. Your job sits alongside every other background process in the estate: payroll runs, accounting creation, integrations, other people's reports. A job that takes an…
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