MSAMM
Back to course

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

What breaks: four concurrent processing failures

Lesson 92 of 184 · 2 min

A queue blocked by ONE LONG JOB, a manager DOWN SINCE A REBOOT, output going to A PRINTER THAT NO LONGER EXISTS, and A PURGE NOBODY HAD EVER RUN. THE QUEUE BLOCKED BY ONE LONG JOB IS THE MOST VISIBLE AND THE MOST MISDIAGNOSED. Every user reports the system as slow; nothing is slow. One report is occupying the manager processes and everything else is waiting — and the host is idle, so every capacity metric says the system is healthy. Lesson 3, and the fix is specialisation rather than more hardware. THE MANAGER DOWN SINCE A REBOOT IS THE SILENT ONE AND IT RUNS LONGEST. The host restarted, the database and application tier came back, and one manager did not — so a specific class of job has not run since. Nothing failed, because nothing ran, and it is discovered when somebody asks where a weekly report has been.…

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