Oracle Performance Tuning
AWR/ASH, wait events, SQL & optimizer tuning
Oracle performance work goes wrong when it starts from ratios and hunches instead of where time actually goes. The method that holds up is time-based: read DB time, rank the wait events by their share of it, and follow the top one to the SQL or the segment behind it. These guides teach that method end to end — how to read an AWR report without drowning, the half-dozen wait events that carry most real problems, and how to tell a SQL problem from a storage problem — with a free lab that reproduces each wait event on your own machine so you see the signature, not just read about it.
Guides in this pillar
- ORA-00060 Deadlock: Find It, Fix It, Prevent It
ORA-00060 rolls back one statement, not your transaction. How to read the deadlock graph, the causes (lock order, unindexed FKs, bitmaps, ITL), and the fixes. - Oracle Wait Events, Decoded: The Half-Dozen
A wait event is just where a session spent time not on CPU. Learn the six that matter, rank them by DB time, and ignore the idle ones. - How to Read an AWR Report Without Drowning
A field guide to Oracle AWR and ASH: DB Time as the master metric, the sections that matter, wait events decoded, the ratios to ignore — plus a free lab.