MSAMM
Back to course

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

A request that will never finish

Lesson 86 of 184 · 2 min · Free preview

Pending, running for eleven hours, or completed with an error nobody read. HOW TO TELL THE THREE APART IN UNDER A MINUTE, WHICH IS THE WHOLE SKILL. "My request will never finish" is three completely different situations with three completely different fixes, and distinguishing them is the fastest diagnosis in this course. PENDING MEANS IT HAS NOT STARTED, SO NOTHING IS WRONG WITH THE PROGRAM AT ALL. It is a queue question — Lesson 2's two checks: which manager should run this, and is that manager running with a free process? Investigating the program here is investigating something that has not happened yet. RUNNING FOR ELEVEN HOURS MEANS IT STARTED AND IS STILL GOING, AND THE FIRST QUESTION IS WHETHER THAT IS NORMAL. Some programs legitimately run for hours. The useful comparison is this request against previous runs of the SAME program — eleven hours against a usual twenty minutes…

This lesson is free

Watch the full lesson, with its written notes, without an account. It is one of the free lessons this course opens with.

Watch the full lesson

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