Oracle Apps DBA: Keeping E-Business Suite Alive · Module 4 · The application tier and the AD utilities
Lab briefing · Operate the tier by hand
Lesson 43 of 184 · 2 min
Stop every service, start them IN THE WRONG ORDER, observe what each failure LOOKS LIKE TO A USER, then do it correctly. The wrong order is the exercise, and doing it deliberately is the only cheap way to learn what those failures look like. You will meet each of them eventually; the choice is whether you meet them here or during an incident. START BY STOPPING EVERYTHING PROPERLY AND TIMING IT. Application tier, then database. How long a clean shutdown takes is a number you need for every future maintenance window, and nobody knows it until they have measured it once. THEN THE WRONG ORDER: BRING THE APPLICATION TIER UP AGAINST A CLOSED DATABASE. Read what the start script says. Then try to use the system as a user would — open the login page and see what a person actually sees. That is the point of the exercise: 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.
In this module: Module 4 · The application tier and the AD utilities
- 1What the application tier does
- 2Starting and stopping the services
- 3adadmin, and what it is for
- 4Compiling and generating
- 5adctrl and the concurrent managers
- 6Reading an AD log
- 7Worker processes, and the one that failed
- 8Custom top, and where your code belongs
- 9What breaks: three application-tier failures
- 10Lab briefing · Operate the tier by hand
