Performing Incomplete Recovery - RMAN Recipes for Oracle Database 12c - page 365

restored
DF CHK SCN =
29950

archive log 1
SCN range:
29940-29952

cannot open database

apply
redo

begin media
recovery

partially
recovered
DF

archive log 2
SCN range:
29953-29973

apply
redo

datafile fuzzy
cannot open database

clear fuzzy SCN:
29954

incomplete recovery possible,
must open database with
open reset logs

partially
recovered
DF

archive log 3
SCN range:
29974-29983

apply
redo

last good
CF CHK SCN:
29980

current online redo
SCN range:
29984-29999

incomplete recovery possible,
must open database with
open reset logs

partially
recovered
DF

apply
redo

last committed
TXN SCN:
29999 complete recovery

DF SCN = CF SCN =
last committed TXN SCN
open database normally

fully recovered
DF SCN = 29999

CF SCN = 29999

Figure 12-1. SCN ranges of incomplete and complete recovery

There are two major exceptions where you can perform incomplete recovery on a subset of your database:

• Tablespace point-in-time recovery (TSPITR)

• Table point-in-time recovery (new in Oracle Database 12c)

Tablespace point-in-time recovery uses the recover tablespace until command. TSPITR is used in rare situations
and restores and recovers only the tablespace(s) you specify. This type of recovery is described in Recipe 12-10 and
involves many steps to achieve the desired result.
Table point-in-time recovery is a new feature in Oracle Database 12c. This type of recovery uses the RMAN
recover table command. This topic is covered in Chapter 13, which deals with various other methods for table-level
recovery (like flashback to before drop or flashback to before SCN).
The recovery portion of an incomplete database recovery is usually initiated with the recover database until
command. RMAN will automatically recover your database to the point specified with the until clause. Just like the
restore command, you can recover until a time, change/SCN, log sequence number, or restore point. When RMAN
reaches the specified point, it will automatically terminate the recovery process.

■ regardless of what you specify in the until clause, rman will convert that into a corresponding until scn
clause and assign the appropriate SCn. This is to avoid any timing issues, particularly those caused by daylight
saving time.

Note

During a recovery, RMAN will automatically determine how to apply redo. First, RMAN will apply any
incremental backups available. Next, any archived redo log files on disk will be applied. If the archived redo log files