1Z0-062 · Question #361
Your database is configured in ARCHIVELOG mode. Examine the RMAN configuration parameters: Examine the command: RMAN> BACKUP DATABASE PLUS ARCHIVELOG DELETE INPUT; Which two are true? (Choose two.)
The correct answer is B. It creates image copies of the archivelogs E. It fails because the DELETE INPUT option can be used only with the BACKUP AS BACKUPSET. The RMAN command BACKUP DATABASE PLUS ARCHIVELOG DELETE INPUT creates image copies of the archivelogs; however, the command is stated to fail because the DELETE INPUT option for archivelogs is strictly valid only when they are backed up as backupsets.
Question
Your database is configured in ARCHIVELOG mode. Examine the RMAN configuration parameters:
Examine the command:
RMAN> BACKUP DATABASE PLUS ARCHIVELOG DELETE INPUT; Which two are true? (Choose two.)
Options
- AIt fails because the DELETE INPUT option can be used only with the BACKUP AS COPY
- BIt creates image copies of the archivelogs
- CIt creates a backupset of archive log files
- DIt creates image copies of the database files
- EIt fails because the DELETE INPUT option can be used only with the BACKUP AS BACKUPSET
How the community answered
(33 responses)- A6% (2)
- B76% (25)
- C3% (1)
- D15% (5)
Why each option
The RMAN command `BACKUP DATABASE PLUS ARCHIVELOG DELETE INPUT` creates image copies of the archivelogs; however, the command is stated to fail because the `DELETE INPUT` option for archivelogs is strictly valid only when they are backed up as backupsets.
The `DELETE INPUT` option is commonly used with `BACKUP AS BACKUPSET` for archivelogs, not exclusively with `BACKUP AS COPY`.
This statement implies that the `PLUS ARCHIVELOG` portion of the RMAN command, under certain configurations or interpretations, results in the creation of image copies for the archivelogs, rather than backupsets.
This statement is contradicted by choice B, as the archivelogs are stated to be created as image copies rather than backupsets.
The `BACKUP DATABASE` command by default creates backupsets of database files, not image copies, unless `AS COPY` is explicitly specified.
The `DELETE INPUT` option, when used with archivelogs, is fundamentally allowed only when those archivelogs are backed up as backupsets. If the RMAN command's behavior for `PLUS ARCHIVELOG` does not inherently produce backupsets, the command attempting `DELETE INPUT` for those archivelogs could fail due to this incompatibility.
Concept tested: RMAN backup options, DELETE INPUT, backup types
Source: https://docs.oracle.com/database/121/BRADV/rcmsyntx.htm#BRADV89422
Topics
Community Discussion
No community discussion yet for this question.