Which three are true about recovering tables using RMAN?

Question

Options

• ARMAN can recover tables owned by the SYSTEM user.
• BRMAN can recover tables owned by the SYS user.
• CRMAN can recover tables in the SYSTEM tablespace.
• DRMAN always uses an auxiliary instance.
• ERMAN can recover a table after a DDL operation has altered the table structure.
• FRMAN can recover tables in the SYSAUX tablespace.
• GRMAN can recover tables in a standby database.

• A
  72% (28)
• B
  8% (3)
• C
  3% (1)
• F
  5% (2)
• G
  13% (5)

Explanation

RMAN's table recovery feature (Oracle 12c+) always creates or uses an auxiliary instance to restore the backup, extract the target table via Data Pump, and import it into the production database - making D unconditionally true. A is correct because SYSTEM is a regular administrative user whose tables are eligible for this feature. E is correct because you can target a recovery SCN or timestamp before the DDL change occurred, effectively rolling back the structural alteration.

Why the distractors are wrong:

• B (SYS): SYS owns the core data dictionary itself; RMAN explicitly excludes SYS-owned objects from table recovery.
• C & F (SYSTEM/SYSAUX tablespaces): Tables residing in these two special tablespaces are ineligible - RMAN table recovery is blocked for objects stored there, regardless of who owns them.
• G (Standby database): Table recovery must target the primary database; it cannot be run against a standby.

Memory tip: Think of the restrictions as two axes - who (not SYS) and where (not SYSTEM/SYSAUX tablespace, not standby). If either axis is restricted, recovery is blocked. Everything else - SYSTEM user, DDL-altered tables, with a mandatory auxiliary instance - is fair game.

No community discussion yet for this question.