iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Start with V$ARCHIVE_DEST to see where Oracle is sending archived redo and whether a destination reports an error or is full. If that destination is the Fast Recovery Area (FRA), use V$RECOVERY_FILE_DEST and V$RECOVERY_AREA_USAGE to identify how much space is used and which recovery-file type is consuming it. Then check RMAN, standby, and flashback requirements before removing files.
1. Find Oracle’s archive destinations and their status
Query V$ARCHIVE_DEST for the current instance’s configured destinations. It can show a local filesystem path, ASM disk group, FRA destination, or remote service such as a standby. Review the destination name and target alongside its status, error, and quota fields.
SELECT dest_id, dest_name, status, target, destination,
error, quota_size, quota_used
FROM v$archive_dest
ORDER BY dest_id;Oracle reports statuses including VALID, INACTIVE, DEFERRED, ERROR, DISABLED, BAD PARAM, ALTERNATE, and FULL. FULL means the destination exceeded its quota. Check ERROR for the reported cause when a destination is in an error state. See Oracle’s V$ARCHIVE_DEST reference and archive destination documentation.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
2. Determine whether the destination is the FRA
If DESTINATION resolves to USE_DB_RECOVERY_FILE_DEST, check the configured recovery-area location and quota:
#1 Best Overall
SELECT name, space_limit, space_used, space_reclaimable,
number_of_files
FROM v$recovery_file_dest;The byte-valued columns distinguish the FRA’s configured limit (SPACE_LIMIT), reported usage (SPACE_USED), and reclaimable space (SPACE_RECLAIMABLE). The FRA is not automatically the archive destination merely because it is configured: it is one possible local destination, though Oracle can select it when an FRA exists and no other local archive destination is specified. A destination may instead be an ordinary filesystem path or ASM disk group. Oracle documents these behaviors in its archive-log management guide and RMAN maintenance guide.
Compare the FRA quota with actual capacity in the underlying filesystem or ASM disk group; they are separate limits. For an archive destination outside the FRA, Oracle’s destination view identifies the path and status but does not account for every file consuming that storage. Check capacity with the appropriate operating-system or ASM tools.
3. Identify what is using FRA space
For an FRA, V$RECOVERY_AREA_USAGE breaks reported usage down by recovery-file type. Sort by used percentage and compare it with reclaimable percentage; the largest category is not necessarily safe to delete.
Recommended Free Tools
SELECT file_type, percent_space_used, percent_space_reclaimable,
number_of_files
FROM v$recovery_area_usage
ORDER BY percent_space_used DESC;Types include ARCHIVELOG, BACKUPPIECE, IMAGECOPY, FLASHBACKLOG, ONLINELOG, and CONTROLFILE. If archived logs are not the dominant category, investigate the type that is. For example, flashback-log usage may be retained to support a guaranteed restore point.
Rank #3
- New
- Mint Condition
- Dispatch same day for order received before 12 noon
- Guaranteed packaging
- No quibbles returns
4. Inspect archived logs and their recorded state
Use V$ARCHIVED_LOG to review recorded log names, destinations, completion times, deletion state, backup counts, and standby apply status:
SELECT thread#, sequence#, dest_id, name, completion_time,
applied, deleted, status, backup_count
FROM v$archived_log
WHERE name IS NOT NULL
ORDER BY completion_time DESC;This view reflects control-file history, not a live inventory of files on disk. Multiple rows can represent copies of the same thread and sequence, so do not count each row as a separate physical file without checking its destination and name. For physical-standby entries registered by RFS, APPLIED='NO' or APPLIED='IN-MEMORY' means the log should not be treated as fully applied when assessing deletion; Oracle says to treat IN-MEMORY like NO. Refer to the V$ARCHIVED_LOG reference.
5. Check which recovery consumers are keeping files
High archived-log usage does not by itself show that logs are obsolete. FRA reclamation depends on whether recovery requirements and other consumers have been satisfied. Check the requirements most relevant to the database:
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →- RMAN: Review the configured retention policy and archived-log deletion policy, as well as backup availability.
- Standby databases: Check transport and apply progress and confirm that standby requirements are met before removing logs.
- Flashback Database: Review flashback-log usage and restore points. A guaranteed restore point can retain flashback logs needed to return to its SCN.
Inspect restore-point storage where applicable:
SELECT name, guarantee_flashback_database, storage_size
FROM v$restore_point
ORDER BY time;Oracle describes FRA consumers, reclaimability, and RMAN maintenance in its RMAN maintenance documentation.
Best Value
6. Reclaim space without breaking recovery
Use RMAN retention and archived-log deletion policies to govern FRA cleanup. Before deleting, verify that required backups exist and that Data Guard and flashback or restore-point needs are satisfied. Do not use manual operating-system deletion as the first cleanup step: it bypasses recovery-aware policy and can leave RMAN’s records inconsistent with files on disk.
If files have already been removed outside RMAN, Oracle documents using CROSSCHECK to reconcile file presence and DELETE EXPIRED to clear expired records. These commands reconcile repository state; they do not make an otherwise needed backup or log safe to remove.
7. Respond promptly if a destination is full
A full archive destination is an operational risk, not just a storage warning. Oracle says, “You must ensure that there is sufficient disk space at all times for archive log destinations,” and warns that a disk-full error during archiving can cause an irrecoverable error and stop the database responding. Check Oracle’s destination status and error, the alert log for disk-full messages, and the underlying filesystem or ASM capacity. If the target is the FRA, also inspect file-type usage and reclaimability. See Oracle’s Managing Archived Redo Log Files.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
