RMAN is connected to a target database instance and an auxilary instance. You execute 3625the command: RMAN> DUPLICATE TARGET DATABASE TO dupdb FROM ACTIVE DATABASE SECTION SIZE 1G; What is the…

Question

Options

• ARMAN uses the pull method to restore files using image copies
• BRMAN uses the push method to transfer image copies
• CRMAN uses the push method to transfer backup sets
• DRMAN uses the pull method to restore files using backup sets

• A
  8% (4)
• B
  6% (3)
• C
  15% (8)
• D
  71% (37)

Explanation

When the SECTION SIZE clause is included in an active database duplication command, RMAN is forced to use backup sets rather than image copies, and because auxiliary channels are present (implied by the connection to the auxiliary instance), the auxiliary instance uses the pull method - its channels connect back to the target and pull the backup set pieces, making D correct. Option A is wrong because image copies are used by default without SECTION SIZE, and the pull method applies to backup sets, not image copies. Option B is doubly wrong: image copies are not used here, and the push method describes target channels sending data outward, not auxiliary channels retrieving it. Option C gets the backup set part right but incorrectly assigns the push method - push applies when no auxiliary channels are configured; with auxiliary channels present, it's always pull. Memory tip: Think "Section Size → backup Sets → Suck (pull) data to auxiliary" - the three S's lock in both the transfer format and direction.

No community discussion yet for this question.