The Legacy Obituaries

RMAN Data Recovery Advisor

pre-11.2 · ha · deprecated 19c · desupported 26ai

Survived, partially.

✓ certified by the mortician

In life

Data Recovery Advisor is the Recovery Manager component that diagnoses data failures such as missing or corrupt files and corrupt blocks, proposes repair options and can run them. It is driven through the RMAN commands LIST FAILURE, ADVISE FAILURE, REPAIR FAILURE and CHANGE FAILURE.

Migrations care mainly for estates that stay on Oracle in Azure, on virtual machines or Oracle Database@Azure, where RMAN remains the backup tool and operational runbooks referencing these commands have to be rewritten. For the PaaS targets the topic disappears, because backup and repair are platform-managed.

Oracle's 19c Upgrade Guide lists the advisor as deprecated starting with 19c (notice dated July 2023), and the 26ai guide desupports it (also July 2023). The four RMAN commands are removed and Oracle names no replacement feature.

Cause of departure

Desupported in Oracle Database 26ai after deprecation in 19c.

Obituary

RMAN Data Recovery Advisor, born before 11.2, diagnosed block and file corruption and proposed RMAN repairs. It kept a failure catalog and offered automated repair advice, sparing administrators some detective work.

Deprecated in 19c and desupported in 26ai, it departed without an Oracle replacement. On Managed Instance, DBCC CHECKDB repair options cannot run because the database cannot enter SINGLE_USER mode; suspected corruption goes to Azure support.

It is survived by Azure SQL Managed Instance, only by workaround, through automatic backups, redundancy and replicas. Oracle Database@Azure survives partly: RMAN and managed backups remain, but the failure catalog and automated advice do not.

Survived by

Oracle Database@Azure partial effort S

Applies to Oracle 11.2, 12.1, 12.2, 18c, 19c, 21c, 23ai

RMAN remains fully available on Oracle Database@Azure, and the service adds managed automatic backups to Autonomous Recovery Service or Object Storage with policy-based retention, so recovery scenarios that Data Recovery Advisor scripted are performed with RMAN commands or console restores. The advisor's failure catalog and automated repair advice are simply absent.

  • Enable automatic backups (Recovery Service for 19.18 and later, or Object Storage) when creating the database.
  • Use the console's restore or RMAN directly for block, datafile or point-in-time recovery.
  • Document manual diagnosis steps (V$DATABASE_BLOCK_CORRUPTION, RMAN VALIDATE) to replace LIST FAILURE / ADVISE FAILURE.

Complications

minor Automatic backups on Exadata Database Service go either to Autonomous Recovery Service (requires Oracle Database 19.18 or later; Bronze 14, Silver 35, Gold 65 and Platinum 95 day policies) or to Object Storage (7 to 60 day retention with weekly L0 and daily L1 backups); PDBs are backed up at the CDB level from the console.

Azure SQL Managed Instance workaround effort S

Applies to Oracle 11.2, 12.1, 12.2, 18c, 19c, 21c, 23ai

Data Recovery Advisor diagnosed block and file corruption and proposed RMAN repairs. Managed Instance removes most of that workflow: backups are automatic with point-in-time restore, storage redundancy handles media failure, Business Critical replicas repair damaged pages automatically, and DBCC CHECKDB repair options cannot be run because the database cannot enter single-user mode, with Microsoft stating that suspected corruption is handled by Azure support.

  • Rely on point-in-time restore or geo-restore to recover from logical corruption.
  • Run DBCC CHECKDB without repair options on a schedule and back up WITH CHECKSUM.
  • Open an Azure support case when corruption is detected instead of attempting repairs.

Complications

major On Managed Instance DBCC CHECKDB cannot be run with REPAIR_ALLOW_DATA_LOSS, REPAIR_FAST or REPAIR_REBUILD because the database cannot be placed in SINGLE_USER mode; Microsoft states that potential corruption is handled by the Azure support team.
· General Purpose, Next-gen General Purpose, Business Critical · microsoft T-SQL differences between SQL Server and Azure SQL Managed Instance

Notices of correction

  1. oracle Oracle Database Changes, Desupports, and Deprecations (Upgrade Guide 19c) · Upgrade Guide 19c, E96252-82, Aug 2026 · read 2026-09-26
  2. oracle Oracle Database Changes, Desupports, and Deprecations (Upgrade Guide 26ai) · Upgrade Guide 26ai, G43570-12, updated Jul 2026 · read 2026-09-26
  3. oracle Exadata Database Service on Dedicated Infrastructure: Manage databases · Oracle Cloud documentation, retrieved 2026-09-26 · read 2026-09-26
  4. microsoft Business continuity and disaster recovery for Oracle Database@Azure (Exadata Database Service) · page updated 2026-08-27; carries a deprecation notice (removal planned 2026-10-30) · read 2026-09-26
  5. microsoft T-SQL differences between SQL Server and Azure SQL Managed Instance · page updated 2026-09-09 · read 2026-09-26
  6. microsoft vCore purchasing model: Azure SQL Managed Instance service tiers · page updated 2026-08-27 · read 2026-09-26

← All notices

RMAN Data Recovery Advisor — Legacy Obituaries