Skip to content
pvmehta.com

pvmehta.com

  • Home
  • About Me
  • Toggle search form
  • How to find pinned objects from shared pool. (pinned via dbms_shared_pool.keep) Oracle
  • Find_planinfo.sql Oracle
  • _B_TREE_BITMAP_PLANS issue during 8.1.7 to 9.2.0.8 upgrade Oracle
  • Postgres DB user and OS user. POSTGRESQL
  • Oracle Data Direct to TAPE Oracle
  • Running PDB on single node in RAC Oracle
  • check_copy_progress.sh Linux/Unix
  • How to find Unix server conguraiton including Server Model number and underlying disk sub-system ( On Solaris) Linux/Unix
  • Generating XML from SQLPLUS Oracle
  • TRUNCATE table and disabling referential constraints. Oracle
  • Kill a session dynanically using execute immediate Oracle
  • runsql_once.ksh Linux/Unix
  • get_vmstat.ksh Linux/Unix
  • Shuffle an array PHP/MYSQL/Wordpress
  • Which environment is used by currently running process ( Very good) Linux/Unix

find_arc.sql

Posted on 09-Apr-2026 By Admin

Monitoring Oracle Archive Logs: A Quick Guide

As an Oracle DBA, keeping a close eye on your archived redo logs is crucial for maintaining database health and ensuring smooth recovery operations. Today, I’ll share a simple yet powerful script that helps you monitor your archive logs effectively.

The Power of v$archived_log

The v$archived_log view is a goldmine of information about your archived redo logs. It contains details about all archived logs that have been generated by your database, including their sequence numbers, timestamps, and whether they’ve been applied to a standby database.

The Monitoring Script

Here’s a script that gives you a clear view of your archive log activity over the past 24 hours:

-- Set display preferences for better readability
set lines 120 pages 200

-- Format dates for better human readability
alter session set nls_date_format='DD-MON-RRRR:Hh24:MI:SS';

-- Query archive log information from the past day
select
    dest_id,
    FIRST_TIME,
    THREAD#,
    SEQUENCE#,
    ARCHIVED,
    APPLIED
from
    v$archived_log
where
    first_time > sysdate -1
order by
    1,2
/

Understanding the Output

This script returns several key pieces of information:

  1. DEST_ID: The archive destination ID where the log was archived
  2. FIRST_TIME: When the log was first created
  3. THREAD#: The thread number (useful in RAC environments)
  4. SEQUENCE#: The log sequence number
  5. ARCHIVED: Whether the log has been archived (YES/NO)
  6. APPLIED: Whether the log has been applied (relevant for standby databases)

Why This Matters

Regularly monitoring your archive logs helps you:

  • Verify that logs are being archived properly
  • Identify any gaps in your log sequence
  • Monitor the lag between primary and standby databases
  • Plan your backup and recovery strategies effectively

Pro Tip

For a more comprehensive view, you might want to combine this with information from v$archive_dest and v$archive_dest_status to get a complete picture of your archive log destinations and their status.

What archive log monitoring techniques do you find most valuable in your environment? Share your thoughts in the comments!

Oracle, SQL scripts

Post navigation

Previous Post: pvm_pre_change.sql
Next Post: Running PDB on single node in RAC

Related Posts

  • standard Monitoring – 1 Oracle
  • Absolute file number and relative file number Oracle
  • CPU Core related projections AWS
  • tracksqltime.sql Oracle
  • moving lob object to other tablespace lob_mvmt.sql Oracle
  • Drop database in Oracle 10g Oracle

Categories

  • Ansible (0)
  • AWS (2)
  • Azure (1)
  • Django (0)
  • GIT (1)
  • Linux/Unix (149)
  • MYSQL (5)
  • Oracle (403)
  • PHP/MYSQL/Wordpress (10)
  • POSTGRESQL (1)
  • Power-BI (0)
  • Python/PySpark (7)
  • RAC (18)
  • rman-dataguard (26)
  • shell (150)
  • SQL scripts (350)
  • SQL Server (6)
  • Uncategorized (5)
  • Videos (0)

Recent Posts

  • Key Management in Oracle: The Core Issue: Missing Master Key12-May-2026
  • SAT Mathematics 10 questions and answer at the end.30-Apr-2026
  • top 10 AI news today30-Apr-2026
  • runon_allpdbs_show_conname.sh23-Apr-2026
  • runon_allcdbs_find_pdbs.sql23-Apr-2026
  • Running PDB on single node in RAC09-Apr-2026
  • find_arc.sql09-Apr-2026
  • pvm_pre_change.sql08-Apr-2026
  • find_encr_wallet.sql08-Apr-2026
  • find_pdbs.sql08-Apr-2026

Archives

  • 2026
  • 2025
  • 2024
  • 2023
  • 2010
  • 2009
  • 2008
  • 2007
  • 2006
  • 2005
  • Metalink Note: Note:250655.1 : ADDM Basics USING THE AUTOMATIC DATABASE DIAGNOSTIC MONITOR Oracle
  • Wait.sql Oracle
  • ORA-8031 issue and solution if it is occuring due to truncate. Oracle
  • Another export with Query Oracle
  • SQLPLUS COPY command Precautions. Oracle
  • Restoring a user’s original password 1051962.101 Oracle
  • Export Import with QUERY Oracle
  • Creating never expiring DB user accounts in Oracle Oracle

Copyright © 2026 pvmehta.com.

Powered by PressBook News WordPress theme