Showing posts with label Oracle Troubleshooting. Show all posts
Showing posts with label Oracle Troubleshooting. Show all posts

Monday, March 2, 2026

Oracle Performance Engineering Guide: AWR, ASH and SQL Monitor in 19c and 23ai

Oracle Performance Engineering Guide: AWR, ASH and SQL Monitor in 19c and 23ai

Oracle Performance Engineering Guide: AWR, ASH and SQL Monitor in 19c and 23ai

Real Production Troubleshooting with Oracle's Performance Diagnostic Tools
📅 March 02, 2026
👤 Chetan Yadav - Senior Oracle & Cloud DBA
⏱️ 12-14 min read
⏱️ Estimated Reading Time: 12–14 minutes
📊 Master AWR, ASH, and SQL Monitor - The Oracle DBA's Performance Troubleshooting Trinity

Production was slow. Users were complaining. The application team blamed the database. I had 30 minutes to find the root cause before the CTO joined the war room call.

I opened an AWR report. Buffer busy waits: 87% of total wait time. But which sessions? Which objects? AWR doesn't tell you. That's when I switched to ASH. Three sessions hammering the same table block. SQL Monitor showed me the exact query execution plan with real-time wait events. Problem identified: missing index on a foreign key. Index created. Performance restored. Crisis averted.

Database performance monitoring dashboard showing analytics metrics graphs and charts representing Oracle AWR ASH SQL Monitor diagnostics

AWR, ASH, and SQL Monitor are Oracle's three essential performance diagnostic tools. AWR gives you the big picture over time. ASH shows you what's happening right now at the session level. SQL Monitor reveals how individual queries execute in real-time. Together, they form the complete performance troubleshooting toolkit that every Oracle DBA needs to master.

This guide covers real production troubleshooting techniques using AWR, ASH, and SQL Monitor in Oracle 19c and 23ai. If you're tired of guessing at performance problems or spending hours digging through logs, these are the diagnostic queries and analysis patterns that actually work.

Thursday, January 8, 2026

Oracle Listener Health Check: Preventing Silent Production Outages

This guide explains how Oracle Listener failures silently impact production systems Oracle Listener Health Check – Production Monitoring Guide | Chetan Yadav

⏱️ Estimated Reading Time: 14 minutes

Oracle Listener Health Check

It’s 2 AM. Your phone lights up with alerts. Applications are down, dashboards are red, and every connection attempt fails with TNS-12541: TNS:no listener. The database is up — but the business is still dead.

In real production environments, a failed Oracle Listener can block thousands of users, cause SLA breaches, and trigger revenue loss within minutes. We’ve seen P99 login latency jump from milliseconds to total outages.

This guide shows how to implement a production-grade Oracle Listener health check using scripts, monitoring logic, and automation — before the listener becomes your single point of failure.