The persistent configuration settings for RMAN have default for all parameters. Identify four RMAN commands that produce a multi-section backup.

Question

Options

• ABACKUP TABLESPACE SYSTEM SECTION SIZE 100M;
• BBACKUP AS COPY TABLESPACE SYSTEM SECTION SIZE 100M;
• CBACKUP ARCHIVELOG ALL SECTION SIZE 25M;
• DBACKUP TABLESPACE "TEMP" SECTION SIZE 10M;
• EBACKUP TABLESPACE "UNDO" INCLUDE CURRENT CONTROLFILE SECTION SIZE
• FBACKUP SPFILE SECTION SIZE 1M;
• GBACKUP INCREMENTAL LEVEL 0 TABLESPACE SYSAUX SECTION SIZE 100M;

• A
  75% (15)
• D
  5% (1)
• E
  5% (1)
• F
  15% (3)

Explanation

Multi-section backups require the SECTION SIZE clause and a supported backup object - RMAN divides eligible files into parallel chunks only for datafiles (regular, image copy, or incremental) and archived logs. Options A, B, C, and G all meet this requirement: A backs up a standard datafile set with sections, B does the same as an image copy (AS COPY), C sections archived logs, and G performs a sectioned Level 0 incremental backup - all fully supported multi-section scenarios.

The distractors fail for specific technical reasons: D is invalid because RMAN cannot back up TEMP tablespace files (temporary datafiles are never included in backups); E is invalid because INCLUDE CURRENT CONTROLFILE cannot participate in a multi-section backup - control files are always written as a single backup piece, making the command incompatible; F is invalid because the SPFILE is a tiny binary configuration file that RMAN does not support sectioning, regardless of the SECTION SIZE clause provided.

Memory tip: Think "SECTION SIZE works for Data, Copies, Archivelogs, and Incrementals" - the four pillars of normal RMAN backup operations. The three outliers (TEMP, CONTROLFILE, SPFILE) are all special non-user-data files that RMAN treats as indivisible or unbackupable, which is exactly why they cannot be sectioned.

No community discussion yet for this question.