Which two quarantine types can disable Smart Scan for multiple databases that offload SQL statements to a cell on an Exadata Database Machine?

Question

Options

• ASQL Plan Quarantine
• BManually created Quarantine
• CDatabase Quarantine
• DDisk Region Quarantine
• ECell Offload Quarantine

• A
  77% (24)
• B
  6% (2)
• C
  3% (1)
• D
  13% (4)

Explanation

SQL Plan Quarantine (A) and Cell Offload Quarantine (E) are correct because both operate at scopes that span multiple databases. A Cell Offload Quarantine is automatically triggered when an offloaded SQL causes a cell issue - it disables Smart Scan for that SQL across all databases that attempt to offload it to that cell, inherently affecting multiple databases. A SQL Plan Quarantine quarantines a specific execution plan, and since multiple databases (e.g., PDBs in a CDB or RAC databases) can share or generate the same plan, it too can disable Smart Scan across multiple databases.

Why the distractors are wrong:

• B (Manually created Quarantine) is not a recognized Exadata quarantine type - quarantines are system-generated or managed via specific Oracle mechanisms, not "manually created" as a category.
• C (Database Quarantine) is scoped to a single database, so by definition it cannot disable Smart Scan for multiple databases simultaneously.
• D (Disk Region Quarantine) relates to I/O isolation on disk regions, not to Smart Scan offload disablement across databases.

Memory tip: Think "SQL and Cell cross boundaries" - SQL plans can be shared across databases, and Cells serve multiple databases. Those are the two quarantine types that can punch through database boundaries and affect Smart Scan for more than one database at once.

No community discussion yet for this question.