Oracle Apps DBA: Keeping E-Business Suite Alive · Module 4 · The application tier and the AD utilities
Reading an AD log
Lesson 39 of 184 · 2 min
Long, verbose, and MOSTLY NOISE. Where the real failure is, and how to find it WITHOUT READING FORTY THOUSAND LINES. An AD log — from a patch, from adadmin, from any of these utilities — is enormous. It records every file it touched, every object it compiled, every worker it started. Reading it end to end is not a technique, it is a way to spend an afternoon. THE FIRST MOVE IS TO SEARCH FOR FAILURE RATHER THAN TO READ FORWARD. Search for the error markers — ORA numbers, the word "error", "fail" — and you go from forty thousand lines to a handful. That is not a shortcut; it is the correct way to use a log of this shape. THE SECOND IS TO GO TO THE END, WHICH SOUNDS OBVIOUS AND IS NOT DONE. These utilities write a summary at the bottom saying what completed, what failed, and…
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