MSAMM
Back to course

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

Starting and stopping the services

Lesson 35 of 184 · 2 min

The scripts, the order, and WHAT A PARTIAL START LOOKS LIKE FROM A USER'S SIDE. EBS ships scripts that start and stop the application tier services, and the ordinary case is one command per tier. The interesting cases are all failures of ORDER and of PARTIALNESS. THE ORDER RULE IS THE ONE FROM MODULE 3: DATABASE FIRST, THEN APPLICATION TIER; APPLICATION TIER DOWN FIRST, THEN DATABASE. Start the application tier against a closed database and components fail one by one, each with its own error, none of which says "the database is not open". You get a page of unrelated-looking failures for a cause that is stated nowhere in them. AND THE MULTI-NODE VERSION IS THE ONE PEOPLE MISS: EVERY APPLICATION NODE MUST BE STARTED, AND STOPPED. Module 2 Lesson 9's second surprise arrives here as a system that is up for most users and down for some — because…

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