Sampling for Performance Data Using PL/SQL Procedure
The database logoff trigger method for collecting historical performance data comes close to meeting all the requirements for root cause analysis established previously, except it lacks fine-grain data and a SQL statement repository. It looks like you need something between the trace event 10046 and the database logoff trigger. We can live with near fine-grain data, but we must absolutely have low overhead ongoing monitoring capability as well as wait event and SQL statement repositories. To achieve this, sampling may be the best approach. If you can sample every foreground process that connects to the instance at regular intervals and write the data to repository tables, you will have a history ...
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.
