RECOVER

The RECOVER command initiates media recovery on a database, a tablespace, or a datafile. Chapter 10 provides an explanation of how recovery works. You must be connected as SYSDBA, SYSOPER, or INTERNAL in order to use this command.

RECOVER [DATABASE [[UNTIL {CANCEL|CHANGE system_change_number|TIME date_time}
                  [USING BACKUP CONTROLFILE]
                  [PARALLEL([DEGREE {num_of_procs|DEFAULT}
                  |INSTANCES {num_of_inst|DEFAULT}]...)
                  |NOPARALLEL]
                  |TABLESPACE tablespace_name [,tablespace_name...]
                  [PARALLEL([DEGREE {num_of_procs|DEFAULT}
                  |INSTANCES {num_of_inst|DEFAULT}]...)
                  |NOPARALLEL]
                  |DATAFILE datafile_name [,datafile_name...]
                  [PARALLEL([DEGREE {num_of_procs|DEFAULT}
                  |INSTANCES {num_of_inst|DEFAULT}]...)
                  |NOPARALLEL]

where:

RECOVER DATABASE

Initiates media recovery on the entire database. The database must be mounted, but not open.

RECOVER TABLESPACE tablespace_name

Initiates media recovery on the specified tablespace or list of tablespaces. A maximum of 16 tablespaces may be recovered with one command. The tablespace(s) must be offline, but the database must be mounted and open.

RECOVER DATAFILE datafile_name

Initiates media recovery on the specified datafile or list of datafiles. Unlike with tablespaces, there is no limit on the number of datafiles you can recover with one command. The datafiles to be recovered must be offline. As long as none of the datafiles are part of the SYSTEM tablespace, the database may remain open.

UNTIL CANCEL

Allows you to recover one log file at a time, with the opportunity ...

Get Oracle SQL*Plus: The Definitive Guide now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.