Oracle Apps DBA: Keeping E-Business Suite Alive · Module 2 · The stack you are responsible for
Logs: where they are and which one to open first
Lesson 20 of 184 · 2 min
Database alert log, application logs, patch logs, concurrent request logs. THE ORDER TO CHECK THEM IN, WHICH IS NOT THE ORDER THEY ARE LISTED. The order is decided by what the symptom is, not by a fixed sequence — and choosing correctly is most of the speed difference between a fast diagnosis and a slow one. IF THE SYMPTOM IS "EVERYTHING IS BROKEN", START AT THE DATABASE ALERT LOG. It records instance-level events — startup, shutdown, errors, space problems, corruption — and if the database is unhappy, nothing above it can be well. It is also the log with the highest ratio of important lines to noise, which is why it is first for a broad symptom. IF ONE USER OR ONE JOB IS AFFECTED, GO STRAIGHT TO THAT REQUEST'S OWN LOG. A concurrent request produces a log and an output file naming what it did and where it stopped.…
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 2 · The stack you are responsible for
- 1The two tiers, and why the split matters
- 2What is running right now
- 3The file system layout
- 4Environment files, and sourcing the right one
- 5The context file
- 6AutoConfig, and what it overwrites
- 7Ports, and the ones you will be asked about
- 8Logs: where they are and which one to open first
- 9What breaks: three architecture surprises
- 10Lab briefing · Map a running instance