Free tools Windows power users keep installed
One-click scans. No signup required.
Start with V$ARCHIVE_DEST to see where Oracle is archiving and whether a destination reports an error; if the 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 file type accounts for it. Then check retention consumers before removing anything: archived logs may still be needed by RMAN, a standby database, or Flashback Database.
1. Find the archive destinations and check their status
Query V$ARCHIVE_DEST for each configured destination. Its rows report destination identity, role, status, destination string, errors, and quota information for the current instance. A destination may be a local filesystem path, an ASM disk group, the FRA, or a remote service such as a standby destination.
As an Amazon Associate I earn from qualifying purchases.
SELECT dest_id, dest_name, status, target, destination,
error, quota_size, quota_used
FROM v$archive_dest
ORDER BY dest_id;Review STATUS and ERROR together. Oracle documents statuses including VALID, INACTIVE, DEFERRED, ERROR, DISABLED, BAD PARAM, ALTERNATE, and FULL; FULL means the destination exceeded its quota. A valid status does not tell you that a non-FRA filesystem has plenty of physical free space. Oracle’s V$ARCHIVE_DEST reference describes the view and its columns.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →2. Determine whether the destination is the FRA
If a destination string is USE_DB_RECOVERY_FILE_DEST, check the FRA’s configured location and quota in V$RECOVERY_FILE_DEST:
#1 Best Overall
SELECT name, space_limit, space_used, space_reclaimable,
number_of_files
FROM v$recovery_file_dest;SPACE_LIMIT, SPACE_USED, and SPACE_RECLAIMABLE are reported in bytes. The FRA is not automatically the destination in every configuration: Oracle may use it as a local archive destination when an FRA is configured and no other local archive destination is specified. Archive logs can instead go to an ordinary path or ASM disk group. See Oracle’s archive destination documentation and RMAN maintenance documentation.
Compare the FRA quota with the actual capacity available on its backing filesystem or ASM disk group. They are separate limits: a configured FRA quota does not guarantee that the underlying storage has that much free capacity. If the destination is a non-FRA filesystem path, use the applicable operating-system capacity tools; for ASM, check the relevant disk-group capacity. The archive-destination view identifies the path and Oracle’s archive status, but it does not account for every file consuming that external storage.
3. If it is the FRA, identify the file type using space
V$RECOVERY_AREA_USAGE breaks FRA usage down by file type, including archived logs, backup pieces, image copies, flashback logs, online logs, and control files.
SELECT file_type, percent_space_used, percent_space_reclaimable,
number_of_files
FROM v$recovery_area_usage
ORDER BY percent_space_used DESC;Read PERCENT_SPACE_USED alongside PERCENT_SPACE_RECLAIMABLE. The biggest category is the biggest consumer, not necessarily the category that is safe to remove now. For example, high ARCHIVELOG usage may reflect logs still required for backups or standby recovery; high FLASHBACKLOG usage may be tied to Flashback Database or a guaranteed restore point. Oracle documents these views in its RMAN maintenance guidance.
Rank #3
- New
- Mint Condition
- Dispatch same day for order received before 12 noon
- Guaranteed packaging
- No quibbles returns
4. Inspect archived-log records and standby apply status
Use V$ARCHIVED_LOG to inspect recorded log names, destination IDs, completion times, deletion state, backup count, and 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 is control-file history, not a live inventory of every file currently on disk. Repeated rows can represent multiple copies of the same thread and sequence. When assessing physical standby logs registered by RFS, do not treat APPLIED='NO' or APPLIED='IN-MEMORY' as fully applied for deletion purposes; Oracle says to treat IN-MEMORY as NO in this context. See Oracle’s V$ARCHIVED_LOG reference.
5. Find the retention consumer before cleaning up
Oracle’s FRA deletion eligibility takes account of retention rules and recovery consumers. Archived redo may remain necessary to RMAN, one or more standby databases, or Flashback Database. Check backup and archived-log deletion policies, standby transport and apply progress, and flashback requirements before changing retention or deleting files.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCheck guaranteed restore points
A guaranteed restore point can retain flashback logs needed to flash back to its SCN. Review restore-point metadata and storage where available:
Best Value
SELECT name, guarantee_flashback_database, storage_size
FROM v$restore_point
ORDER BY time;Use this alongside the FRA usage breakdown: a flashback-log consumer can explain space pressure even when archived redo is not the largest category.
Reclaim with RMAN-aware policies
Oracle identifies the RMAN retention policy and archived-log deletion policy as the appropriate controls for FRA deletion. Avoid starting with operating-system deletion: removing a file outside RMAN can leave repository records that no longer reflect what is on storage. If files have already been removed externally, Oracle documents using RMAN CROSSCHECK to reconcile their presence and DELETE EXPIRED to clear expired records. Before any cleanup, verify backup availability and Data Guard, flashback, and restore-point requirements. See Oracle’s RMAN maintenance documentation.
6. Respond promptly if a destination is full
Oracle warns: “You must ensure that there is sufficient disk space at all times for archive log destinations.” It also warns that a disk-full error while archiving can cause an irrecoverable error and stop the database responding. Check the alert log for disk-full messages, then inspect the destination’s Oracle status and error, the underlying filesystem or ASM capacity, and—if the target is the FRA—the category usage and reclaimable space. Oracle’s Managing Archived Redo Log Files covers destination capacity and archiving risks.
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.
