You are given four high-level steps that a DBA (or database engineer) should follow when a performance problem is reported. The steps are intentionally out of order.
What to do:
- Reorder the steps so the first action appears at the top of the list and the last action appears at the bottom.
- When you think the sequence is correct, click Submit.
- The result page will tell you whether the sequence is correct. If it is not correct, adjust the order and try again.
Hint for reasoning: A solid tuning workflow starts by ruling out external bottlenecks (network, host, storage). Only after that should you move into database-level diagnostics and reporting.
- Exercise Scoring
This exercise is auto-scored. When you have completed the exercise, click Submit to receive full credit.
The Steps (Out of Order)
- Verify that there are no network slowdowns or transmission bottlenecks.
- Verify that the database server is not overloaded (CPU and memory), and check for I/O bottlenecks on storage.
- Check the Oracle instance for bottlenecks using performance views (for example, active sessions, wait events, redo pressure, and lock contention).
- Capture an elapsed-time performance report for the incident window using modern diagnostics (AWR/ASH where available) or equivalent instance snapshots.