Oracle Apps DBA: Keeping E-Business Suite Alive · Module 8 · Concurrent processing
Work shifts
Lesson 85 of 184 · 2 min
Different capacity at different times of day. Useful, and A COMMON CAUSE OF "IT RUNS FINE IN THE MORNING". A work shift lets a manager have different numbers of processes at different times — few during the day so interactive users get the database, many at night when the batch window opens. THAT IS GENUINELY USEFUL AND IT IS THE RIGHT TOOL FOR AN ESTATE WITH A HEAVY OVERNIGHT LOAD. Daytime responsiveness and overnight throughput are different requirements, and a single fixed capacity serves one of them badly. AND IT IS THE EXPLANATION FOR THE COMMONEST BAFFLING SYMPTOM IN THIS MODULE: A JOB THAT BEHAVES DIFFERENTLY DEPENDING ON WHEN IT RUNS. Fine in the morning, queues in the afternoon. Fine on weekdays, sits all weekend. Nothing about the job changed and nothing is broken — the capacity available to it did. THE WEEKEND CASE IS THE ONE THAT COSTS MOST.…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Apps DBA: Keeping E-Business Suite Alive, with a certificate on completion and a fourteen-day refund window.
In this module: Module 8 · Concurrent processing
- 1What a concurrent request is
- 2Managers, queues and workers
- 3Specialisation rules
- 4Work shifts
- 5A request that will never finishFree preview
- 6Reading a request log
- 7Killing a request safely
- 8Managers that will not start
- 9Output, printing and delivery
- 10Purging: the table that ate the database
- 11What breaks: four concurrent processing failures