Question
Oracle RMAN ↔ DBUA: Evaluating Rollback Options After a Failed Upgrade
Rahul Atlas
0 reputation · 17 Aug 2020, 17:08 UTC
95.7K views
Loading…
0 reputation · 17 Aug 2020, 17:08 UTC
Goal: Identify the most suitable rollback strategy when Oracle Database Upgrade Assistant (DBUA) reports a failure during an upgrade, choosing between a Recovery Manager (RMAN) restore of a pre‑upgrade backup and a FLASHBACK DATABASE to a guaranteed restore point.
Constraints and uncertainties: The RMAN path requires a recent consistent backup, ARCHIVELOG mode, and sufficient time to restore and recover; the flashback path needs Enterprise Edition, the FLASHBACK DATABASE privilege, a guaranteed restore point created beforehand, and adequate Flash Recovery Area space to hold the redo generated after the point. Downtime tolerance, storage consumption, and licensing costs further complicate the selection, and Oracle documentation does not prescribe a default method.
What factors should outweigh the others when deciding between RMAN restore and FLASHBACK DATABASE? How does the availability of Enterprise Edition features versus backup infrastructure influence the choice? In what scenarios does the storage overhead of flashback outweigh the time cost of RMAN recovery?
35275 reputation · 17 Aug 2020, 18:48 UTC
The most critical factor outweighing all others is Recovery Time Objective (RTO). If the business cannot tolerate the hours required to restore terabytes of data from disk or tape, FLASHBACK DATABASE is the superior choice, provided the technical prerequisites were met prior to the upgrade attempt.
The choice depends on the intersection of licensing, pre-upgrade configuration, and storage availability.
| Factor | Flashback Database | RMAN Restore |
|---|---|---|
| Licensing | Enterprise Edition Required | Standard or Enterprise Edition |
| Speed | Very Fast (reverts blocks) | Slow (full data movement) |
| Storage | High (FRA must hold all redo) | Moderate (Backup storage) |
| Requirement | Guaranteed Restore Point (GRP) | Consistent Pre-upgrade Backup |
The storage overhead of Flashback Database outweighs the time cost of RMAN in scenarios involving high-churn databases. Because a Guaranteed Restore Point (GRP) prevents the database from overwriting flashback logs in the Fast Recovery Area (FRA), a failed upgrade that generates massive amounts of redo can fill the FRA, potentially freezing the database instance. If the FRA is undersized relative to the expected upgrade logs, RMAN is the safer, more predictable path.
Depending on your chosen path, execute the following scoped commands:
oracle-- Ensure database is mounted but not open
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
-- Revert to the pre-upgrade point
FLASHBACK DATABASE TO RESTORE POINT pre_upgrade_grp;
-- Open with resetlogs
ALTER DATABASE OPEN RESETLOGS;
-- Connect to RMAN
rman target /
-- Restore and recover
RESTORE DATABASE;
RECOVER DATABASE;
ALTER DATABASE OPEN RESETLOGS;
To determine which path is currently viable, verify your environment with these queries:
SELECT flashback_on FROM v$database;LIST BACKUP SUMMARY; (within RMAN)Missing Diagnostic Detail: Please provide the total size of your Fast Recovery Area (FRA) and the volume of redo generated during the failed upgrade. This determines if a Flashback operation is physically possible without triggering a disk-full hang.
Use comments to ask for clarification. Post a solution as an answer.
6,710 reputation · 17 Aug 2020, 19:15 UTC
DBUA automatically creates a guaranteed restore point named PRE_UPGRADE_ before the upgrade starts. Because it is guaranteed, the database will not overwrite flashback logs for that point, ensuring FLASHBACK DATABASE TO RESTORE POINT PRE_UPGRADE_* works even if the upgrade generates large amounts of redo. However, the Flash Recovery Area must still have enough space to retain those logs; if the FRA is undersized, the instance can hang despite the guarantee. In contrast, the level 0 RMAN backup taken by DBUA can be restored and recovered without needing FRA space for flashback logs, but it requires sufficient backup storage and time to apply redo. If you lack Enterprise Edition or the guaranteed restore point was not created (e.g., DBUA ran with -nobackup), you must rely on the RMAN backup.