MSAMM
Back to course

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

What breaks: three application-tier failures

Lesson 42 of 184 · 3 min

A service that started but ANSWERS NOTHING, a customisation OVERWRITTEN BY AutoConfig, and a worker that has been FAILING QUIETLY FOR AN HOUR. THE SERVICE THAT STARTED BUT ANSWERS NOTHING IS THE ONE THAT DEFEATS PROCESS CHECKS. The process is running, the start script reported success, and requests get no response — because the component started and then failed to initialise, or is waiting on something that never arrives, or is running against a database that is not open. THE LESSON IS THAT A PROCESS EXISTING IS NOT A SERVICE WORKING, which is the limit of Module 2 Lesson 2's baseline stated honestly. The check that discriminates is a request rather than a process list — ask the component for something and see whether it answers. Same family as every "a 200 does not tell you which site answered" problem: existence is not function. THE CUSTOMISATION OVERWRITTEN BY AutoConfig IS…

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