Examine the RMAN command: RMAN> RUN { ALLOCATE CHANNEL c1 DEVICE TYPE sbt; ALLOCATE CHANNEL c2 DEVICE TYPE sbt; ALLOCATE CHANNEL c3 DEVICE TYPE sbt; BACKUP INCREMENTAL LEVEL = 0 (DATAFILE 1,4,5…

Question

Options

• AIt uses multisection backup.
• BIt uses parallelization for the backup set.
• CIt uses asynchronousI/O for the backup.
• DIt creates compressed backup sets.

• A
  17% (5)
• B
  72% (21)
• C
  7% (2)
• D
  3% (1)

Explanation

Option B is correct because three separate channels (c1, c2, c3) are explicitly allocated and assigned distinct sets of datafiles, meaning all three backup operations run simultaneously - that is the definition of parallelization in RMAN. Each channel produces its own backup set concurrently, reducing overall backup time.

Why the distractors are wrong:

• A (multisection backup) - Multisection backup splits a single large datafile across multiple channels using the SECTION SIZE clause. That clause is absent here; instead, different datafiles are assigned to each channel, which is channel parallelization, not multisection.
• C (asynchronous I/O) - Async I/O is an OS/storage-level setting, not something controlled or declared in an RMAN RUN block. Nothing in this syntax enables or references it.
• D (compressed backup sets) - Compression requires either the AS COMPRESSED BACKUPSET clause in the BACKUP command or a CONFIGURE COMPRESSION ALGORITHM setting. Neither is present here.

Memory tip: Think of it this way - channels = workers. Multiple channels doing work at the same time = parallelization. If you see SECTION SIZE instead, that's multisection. If you see AS COMPRESSED BACKUPSET, that's compression. No keyword = no feature.

No community discussion yet for this question.