Restore a NOARCHIVELOG Database - Exercise
Respond to a media failure affecting the USERS tablespace
Objective: Order the steps for restoring a database from a consistent backup, and recognize which changes will be lost.
Scenario
A disk failure destroys a datafile belonging to the read/write USERS tablespace in a PDB. Your single-instance Oracle AI Database 26ai CDB runs in NOARCHIVELOG mode.
- The instance is already shut down. Replacement storage is available at the original file locations.
- A validated, consistent whole-CDB RMAN backup is available, taken while mounted after a clean shutdown. Its unique tag is
CONSISTENT_WHOLE_BACKUP.
- The current control file and server parameter file are intact; RMAN knows the backup locations. No datafiles or PDBs have been added or removed since that backup.
- There are no subsequent incremental backups and no complete redo history to recover changes since the backup.
- The approved plan is to restore the whole CDB, accepting the loss of all changes since the backup across its PDBs.
Scope: This is a planning exercise. Submitting your answer does not execute database commands.
Instructions
Arrange the six steps below in execution order. Enter each letter A–F once, separated by spaces or commas. Select Submit to check your order and read the explanation.
Steps to arrange
- A
- Open the restored CDB with
ALTER DATABASE OPEN RESETLOGS;.
- B
- Restore all database datafiles from the designated consistent backup.
- C
- Connect RMAN to the target CDB using an authorized administrative account.
- D
- Open the required PDBs, validate application data, and arrange a new consistent backup before returning the system to service.
- E
- Start the instance and mount the CDB without opening it.
- F
- Run
RECOVER DATABASE NOREDO;.
Exercise scoring
This exercise is unscored. The result page checks your sequence and explains the solution.