MSAMM
Back to course

Oracle Apps DBA: Keeping E-Business Suite Alive · Module 4 · The application tier and the AD utilities

Worker processes, and the one that failed

Lesson 40 of 184 · 3 min

Parallel workers, restarting a failed one, and THE DECISION between fixing it and letting the job continue without it. AD utilities split work across parallel workers so a job that would take twelve hours takes three. Each takes tasks from a queue, and the job is finished when every worker has finished its share. SO A FAILED WORKER STALLS THE WHOLE JOB RATHER THAN FAILING IT. The utility waits, reporting that a worker has failed, and it will wait indefinitely — which is the behaviour to recognise, because the visible symptom is a patch that has stopped making progress rather than a patch that has errored. THE FIRST STEP IS ALWAYS THE SAME: FIND OUT WHY. The worker's own log names the task and the error — Lesson 6 — and the cause is usually one of a small set: a space problem, an object that was not in the…

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 4 · The application tier and the AD utilities

  1. 1What the application tier does
  2. 2Starting and stopping the services
  3. 3adadmin, and what it is for
  4. 4Compiling and generating
  5. 5adctrl and the concurrent managers
  6. 6Reading an AD log
  7. 7Worker processes, and the one that failed
  8. 8Custom top, and where your code belongs
  9. 9What breaks: three application-tier failures
  10. 10Lab briefing · Operate the tier by hand