1Z0-052 · Question #140
You are managing an Oracle Database 11g database running in ARCHIVELOG mode. The Flash Recovery Area is specified as the destination for the archived redo log files. You notice this warning in the…
The correct answer is A. Back up the Flash Recovery Area. B. Decrease the retention time for the database backup and flashback log files. To reclaim space in a full Flash Recovery Area, you must either back it up via RMAN so files can be tracked and aged out, or reduce the retention policy so more files become obsolete and eligible for deletion.
Question
You are managing an Oracle Database 11g database running in ARCHIVELOG mode. The Flash Recovery Area is specified as the destination for the archived redo log files. You notice this warning in the alert log file:
ORA19815: WARNING: db_recovery_file_dest_size of 3221225472 bytes is 100.00% used, and has 0 remaining bytes available. What would you do to reclaim the used space in the Flash Recovery Area? (Choose two.)
Options
- ABack up the Flash Recovery Area.
- BDecrease the retention time for the database backup and flashback log files.
- CManually delete all the archived log files from the Flash Recovery Area by using operating system (OS)
- DManually delete all the expired backup sets from the Flash Recovery Area by using operating system
How the community answered
(21 responses)- A81% (17)
- C5% (1)
- D14% (3)
Why each option
To reclaim space in a full Flash Recovery Area, you must either back it up via RMAN so files can be tracked and aged out, or reduce the retention policy so more files become obsolete and eligible for deletion.
Backing up the Flash Recovery Area with RMAN causes RMAN to record the backup metadata in its repository and mark the backed-up archived logs and flashback logs as eligible for deletion, allowing Oracle to automatically reclaim the space while maintaining recoverability.
Decreasing the retention time causes RMAN to classify more backup files and flashback logs as obsolete based on the shorter policy window, which allows RMAN to delete them and free space in the Flash Recovery Area without breaking the backup strategy.
Manually deleting archived log files using OS commands bypasses the RMAN catalog entirely, so Oracle does not register the deletion and does not reclaim the space allocation in the Flash Recovery Area; RMAN may also no longer be able to guarantee recoverability.
Manually deleting expired backup sets using OS commands has the same problem as option C - RMAN's catalog is not updated, the freed space is not recognized by the Flash Recovery Area quota tracking, and catalog integrity is compromised.
Concept tested: Flash Recovery Area space reclamation using RMAN
Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/bradv/using-flash-recovery-area.html
Topics
Community Discussion
No community discussion yet for this question.