Oracle Apps DBA: Keeping E-Business Suite Alive · Module 11 · Performance: finding the actual problem
Lab briefing · Diagnose three slow systems
Lesson 123 of 184 · 3 min
Three instances, three different causes, and A WRITTEN FINDING FOR EACH that NAMES THE EVIDENCE RATHER THAN THE SUSPICION. The written finding is the deliverable, because a diagnosis nobody can check is indistinguishable from a guess that happened to be confident. WORK EACH ONE IN THE MODULE'S ORDER RATHER THAN JUMPING TO A THEORY. Lesson 2's four questions first — who, doing what, since when, compared to what — and write the answers down before touching a tool. Then measure where the time goes, per Lesson 3, and only then open a report. THE THREE CAUSES WILL BE DIFFERENT IN KIND, WHICH IS THE POINT OF THREE. One will be a plan that changed because statistics were stale — the commonest real cause, and the one the four questions identify almost immediately. One will be blocking, where every resource metric is healthy and the system is idle. And one will…
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 11 · Performance: finding the actual problem
- 1Measure before you tuneFree preview
- 2"The system is slow": turning that into a question
- 3Where time actually goes
- 4AWR and ASH, used properly
- 5A baseline is what makes a report meaningful
- 6Finding the expensive SQL
- 7Execution plans, enough to act
- 8Statistics: the commonest real cause
- 9Locking and blocking
- 10When it is the application, not the database
- 11What breaks: four performance investigations that went wrong
- 12Lab briefing · Diagnose three slow systems