MSAMM
Back to course

Oracle Apps DBA: Keeping E-Business Suite Alive · Module 8 · Concurrent processing

What a concurrent request is

Lesson 82 of 184 · 2 min

A job submitted by a user or a schedule, RUN BY A MANAGER, producing output. The model everything else in this module hangs off. Almost everything that happens in EBS outside a screen happens as a concurrent request. Reports, interfaces, period-end programs, data loads, the routine housekeeping that keeps the estate working. Which is why an idle concurrent processing tier is a business that has stopped without anybody noticing — Module 4 Lesson 1's silent failure. THE MODEL IS FOUR PARTS AND EVERY DIAGNOSIS IN THIS MODULE IS ABOUT WHICH PART IS STUCK. A REQUEST is the instance of a job: this program, with these parameters, submitted by this person at this time. It has a status — and reading that status correctly is Lesson 5, which is most of the skill. A MANAGER is a process that picks requests up and runs them. Several managers exist, each with a…

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.

See the course and enrol9 free lessons

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 8 · Concurrent processing

  1. 1What a concurrent request is
  2. 2Managers, queues and workers
  3. 3Specialisation rules
  4. 4Work shifts
  5. 5A request that will never finishFree preview
  6. 6Reading a request log
  7. 7Killing a request safely
  8. 8Managers that will not start
  9. 9Output, printing and delivery
  10. 10Purging: the table that ate the database
  11. 11What breaks: four concurrent processing failures