Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 6 · Reports at scale: scheduling, delivery, performance
Incremental extracts and high-water marks
Lesson 60 of 177 · 2 min
Sending only what changed is the right design and it has exactly two failure modes, which are mirror images of each other. MISSING A RECORD BECAUSE THE BOUNDARY MOVED. The run takes everything changed since the last run, and something is written while the extract is executing — it falls between the query and the mark, and it is never sent. Nothing errors, and the record simply never arrives in the other system, which is discovered months later during a reconciliation nobody planned. RESENDING BECAUSE IT DID NOT. The mark is not advanced, or is advanced only on success and the run half-succeeded, so the next run sends the same rows again. Whether that matters depends entirely on the receiver: an idempotent one shrugs, a naive one creates duplicates. The high-water mark is the mechanism, and three rules make it safe. Base it on a timestamp the APPLICATION sets, not…
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