1Z0-067 · Question #220
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…
The correct answer is B. It uses parallelization for the backup set. See the full explanation below for the reasoning.
Question
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 CHANNEL c1) (DATAFILE 2, 3, 9 CHANNEL c2) (DATAFILE 6, 7, 8 CHANNEL c3) SQL `ALTER SYSTEM ARCHIVE LOG CURRENT'; } Which statement is true about the command? Choose the best answer.
Options
- AIt uses multisection backup.
- BIt uses parallelization for the backup set.
- CIt uses asynchronous I/O for the backup.
- DIt creates compressed backup sets.
How the community answered
(49 responses)- A16% (8)
- B71% (35)
- C4% (2)
- D8% (4)
Community Discussion
8
Samuel O.Dec 19, 2025B is your answer here, and the reasoning is pretty clear once you have seen this pattern in production. When you explicitly allocate multiple channels and then split the datafiles across those channels inside the BACKUP command, RMAN is distributing the work across c1, c2, and c3 simultaneously, which is parallelization at the backup set level. Each channel writes its own backup set to the SBT device at the same time rather than one stream finishing before the next starts. The other choices do not apply because multisection backup splits a single large file across channels, compressed sets require the AS COMPRESSED BACKUPSET clause, and asynchronous I/O is a storage layer behavior that has nothing to do with what this syntax is controlling.
Imani T.Dec 22, 2025Samuel nailed the core of it, though worth noting that even with three allocated channels you can still get serialization bottlenecks if the SBT device itself is a single-stream target, so the parallelization lives in the RMAN layer but the actual throughput gain depends on whether your media manager supports concurrent sessions.
Imani T.Jan 10, 2026B is right, three channels splitting datafiles across sets is parallelization.
Anjali D.Jan 12, 2026Imani is right that splitting across channels fits the parallelization definition, but worth noting for the exam that the answer hinges on whether the question is testing parallelization as a concept or striping specifically, since some answer banks treat those as distinct distractors.
Brenda K.Dec 5, 2025Clock is ticking the second you see this one, but do not rush into a trap. The RUN block manually allocates three separate SBT channels and then assigns specific datafiles to each channel inside the BACKUP command using the parenthetical syntax, which is exactly how you set up a multisection backup to split large files across channels. I have drilled this scenario enough times to know that the channel-to-datafile assignment inside those parentheses is the dead giveaway for multisection, not just parallelism, because parallelism at the backup set level lets RMAN decide the distribution on its own without you pinning files to specific channels like this. Option B would be correct if the command just said BACKUP INCREMENTAL LEVEL 0 DATAFILE 1,2,3,4,5,6,7,8,9 and let the three channels divvy up the work automatically, but that is not what is written here. Mark A and move on, this is a medium-burn question so do not let it eat more than 90 seconds.
Imani T.Dec 6, 2025Brenda, I see where you're coming from, but the parenthetical syntax assigning different datafiles to different channels is just manual parallelism control, and B is the right call here because multisection backup requires the SECTION SIZE clause to split a single large datafile into multiple sections across channels, and that clause is nowhere in this command.
Anjali D.Dec 29, 2025I keep coming back to D on this one because that BACKUP command going to SBT device type is hitting tape, and RMAN compresses to tape by default when no explicit format is set, so you are getting compressed backup sets whether you asked for it or not. Has anyone in the group checked the Oracle docs on default SBT behavior to push back on this, because I am pretty sure that seals it?
Imani T.Dec 29, 2025Anjali, SBT just defines the media management layer, it does not trigger compression on its own, and Oracle's docs are clear that RMAN only compresses backup sets when you explicitly configure it or specify AS COMPRESSED BACKUPSET in the command, so B is the right call here because the default behavior without that explicit setting is uncompressed backup sets regardless of device type.