You notice that the performance of your production 24x7 Oracle 12c database has significantly degraded. Sometimes, you are not able to connect to the database instance because it hangs. How can you…

Question

Options

• Aby performing emergency monitoring using Real-Time Automatic Database Diagnostic Monitor
• Bby running ADDM to fetch information from the latest Automatic Workload Repository (AWR)
• Cby using Active Session History (ASH) data and performing hang analysis
• Dby running ADDM in diagnostic mode

• A
  70% (21)
• B
  7% (2)
• C
  20% (6)
• D
  3% (1)

Explanation

Option A is correct because Real-Time ADDM (Automatic Database Diagnostic Monitor) is specifically engineered for emergency scenarios where the database is hung or severely degraded. It establishes a preliminary (emergency) connection that bypasses normal database connection mechanisms, allowing it to read in-memory SGA data directly - making it the only tool here that works when you literally cannot connect.

Why the distractors are wrong:

• B - Standard ADDM analyzes historical AWR snapshots (point-in-time data taken on a schedule). It cannot diagnose a currently hung database, and requires a normal connection to run in the first place.
• C - ASH data and hang analysis are valuable diagnostics, but querying ASH requires a functional database connection. If the instance is hanging and connections are failing, you cannot run ASH reports through normal means. (Note: Real-Time ADDM actually incorporates hang analysis internally.)
• D - "ADDM in diagnostic mode" is a fabricated option. No such distinct operational mode exists in Oracle 12c - this is a classic exam distractor designed to sound plausible.

Memory tip: Associate Real-Time ADDM with the phrase "emergency room for a hung database" - just as an ER bypasses normal check-in procedures for critical patients, Real-Time ADDM bypasses the normal connection path to reach a dying instance.

No community discussion yet for this question.