Describing the basics of database backup, restore, and recovery
Describing the types of failure that can occur in an Oracle database
Describing ways to tune instance recovery
Identifying the importance of checkpoints, redo log files, and archived log files
Configuring ARCHIVELOG mode
Configuring a database for recoverability
Creating consistent database backups
Backing up your database without shutting it down
Creating incremental backups
Automating database backups
Monitoring the Flash Recovery area
Describing the difference between image copies and backup sets
Describing the different types of database backups
Backing up a control file to trace
Managing backups
Recovering from loss of a control file
Using RMAN (the Recovery Manager provided since Oracle 8):
If flash recovery area is configured and control file auto backup is on then:
RMAN> connect target / RMAN> startup nomount; RMAN> restore controlfile from autobackup;
This will restore the control file to the location specified by the initialization parameter CONTROL_FILES mentioned in initialization parameter.
If flash recovery area is configured and control file auto backup is off then:
RMAN> connect target / RMAN> startup nomount; RMAN> restore controlfile from 'C:\FRA\DBNAME\backupset\date_of_backup\backupset_name';
This will restore the control file to the location specified by the initialization parameter CONTROL_FILES mentioned in initialization parameter.
If restoration is being done using recovery catalog then:
RMAN> connect target / RMAN> connect catalog catalog_database_user/password@recovery_catalog_service; RMAN> startup nomount; RMAN> restore controlfile;
This will restore the control file to the location specified by the initialization parameter CONTROL_FILES mentioned in initialization parameter.
If no flash recovery area is configured, no recovery catalog is available and RMAN backup piece is available at default location then:
RMAN> connect target / RMAN> startup nomount; RMAN> set dbid 1234567890; RMAN> restore controlfile from autobackup;