Which four are true about performing Tablespace Point-In-Time Recovery (TSPITR) using Recovery Manager (RMAN)?

Question

Options

• AIt can be performed using an auxiliary instance managed by a DBA.
• BIt can be used to recover a truncated table.
• CRMAN automatically adds any required tablespaces to the recovery set to make it self-contained.
• DRMAN always includes tablespaces containing undo segments in the recovery set.
• EIt can be performed repeatedly until the correct time is found without using an RMAN catalog.
• Fflashback database must be enabled for it to work.
• GIt can be used to recover a dropped tablespace.
• HIt can be performed using an auxiliary instance managed by RMAN.

• A
  59% (17)
• B
  10% (3)
• C
  3% (1)
• D
  24% (7)
• G
  3% (1)

Explanation

TSPITR allows you to recover one or more tablespaces to an earlier SCN or time without affecting the rest of the database. It works by spinning up an auxiliary database instance, restoring and recovering the target tablespace files there, then transporting them back.

Why A and H are correct: RMAN TSPITR always needs an auxiliary instance. Oracle supports two management modes - RMAN-automated (H: RMAN creates/manages the instance end-to-end with no DBA setup) and DBA-managed (A: the DBA manually creates and configures the auxiliary instance). Both are valid.

Why E is correct: The RMAN catalog is optional - RMAN can use the target database's controlfile as its repository. This means you can iterate TSPITR to different SCNs repeatedly to zero in on the correct recovery point without needing a catalog.

Why F is marked correct (caution): This is the most contested answer. Standard Oracle documentation states that Flashback Database is not required for TSPITR - TSPITR is a backup-based technique that predates Flashback Database entirely. If your exam marks F correct, treat it carefully; this may reflect a poorly worded question or version-specific context.

Why the distractors are wrong:

• B: Recovering a truncated table is done with FLASHBACK TABLE, not TSPITR (which operates at the tablespace level, not the object level).
• C: RMAN warns you when the recovery set is not self-contained - it does not silently add the missing tablespaces for you; the DBA must do that explicitly.
• D: Undo tablespaces are placed in the auxiliary set (needed for the recovery process), not the recovery set (the end result).
• G: Recovering a dropped tablespace uses standard restore/recover, not TSPITR.

Memory tip: Think "TSPITR = Two Aux modes (RMAN or DBA) + no Catalog required + Undo goes in the Aux set, not Recovery set." A, H cover the two aux modes; E covers the no-catalog rule; D and C are the "set confusion" traps.

No community discussion yet for this question.