In a Nutshell
A database performance problem may easily be diagnosed if the DBA knows what each session is doing or has done in the database. In practice, however, a DBA normally administers many databases, and it is impossible to baby-sit each one. Therefore, a question such as, “Why did the job run so slowly?” is challenging to even the most competent DBA. The Oracle Wait Interface is great at finding the root causes of performance problems, provided the DBA is aware of the bottlenecks. Tuning exercises without the guidance of bottlenecks (or symptoms) is almost always unprofitable and a waste of time.
This chapter offers a couple of methods for capturing performance data—that is, using the database logoff trigger and PL/SQL procedure. In addition, ...
Get Oracle Wait Interface: A Practical Guide to Performance Diagnostics & Tuning now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
