How to Disable and Enable Oracle Archive Log Destinations

calendar Nov 27, 2025 / · 3 min read · Oracle Database Data Guard Archive Log DBA Commands Database Administration Standby Database Oracle Backup Database Maintenance  ·
Share on: linkedin copy

How to Disable and Enable Oracle Archive Log Destinations

Purpose

The Oracle commands for disabling and enabling archive log destinations allow database administrators to control the availability of archive destinations without removing the configuration. These commands are commonly used in Oracle Data Guard environments to temporarily stop or resume redo log shipping to standby databases during maintenance operations, troubleshooting, or planned outages.

Breakdown of Code

Original Code

1-- Disable/Enable archive log destinations
2alter system set log_archive_dest_state_2 = 'defer';
3alter system set log_archive_dest_state_2 = 'enable';

Command Explanation

First Command: Defer (Disable)

1alter system set log_archive_dest_state_2 = 'defer';

This command temporarily disables the second archive log destination. When you defer a destination, Oracle preserves all the destination information and settings but excludes it from archiving operations. The redo logs will not be sent to this destination until you enable it again.

Second Command: Enable (Activate)

1alter system set log_archive_dest_state_2 = 'enable';

This command activates the second archive log destination. The destination becomes available for archiving operations immediately, and Oracle resumes sending archived redo logs to this location.

Key Points

  • Non-destructive operation: Using defer does not delete the destination configuration; it only makes it temporarily unavailable
  • Destination numbering: Oracle supports up to 31 archive destinations (LOG_ARCHIVE_DEST_1 through LOG_ARCHIVE_DEST_31)
  • Default state: The default state for any configured archive destination is enable
  • Immediate effect: Changes take effect immediately without requiring a database restart
  • Data Guard usage: Destination 2 is typically configured for standby database locations in Data Guard setups

Common Use Cases

Maintenance Operations

You can defer archive destinations when performing maintenance on standby databases to prevent archive log buildup or errors on the primary database. This is useful during:

  • Standby database patching or upgrades
  • Network maintenance between primary and standby sites
  • Storage maintenance on the standby location

Troubleshooting

Deferring destinations helps isolate issues when multiple archive destinations are configured. If one destination experiences problems, you can defer it while investigating without affecting other destinations.

Controlled Failover Testing

During disaster recovery testing, administrators can defer and enable destinations to control the flow of redo data and simulate various failure scenarios.

Additional State Values

Oracle provides four state values for archive destinations:

  • enable: Destination is active and receiving archive logs (default)
  • defer: Destination is temporarily disabled but configuration is preserved
  • alternate: Destination serves as a backup if primary destinations fail
  • reset: Functions like defer but also clears any previous error messages

Verification Commands

After changing the destination state, you can verify the configuration using:

1-- Check archive destination status
2SELECT dest_id, status, destination 
3FROM v$archive_dest 
4WHERE dest_id = 2;
5
6-- View archive destination parameters
7SHOW PARAMETER log_archive_dest_state_2;

The V$ARCHIVE_DEST dynamic performance view displays the current state and configuration for all archive destinations.

Best Practices

  • Always verify the destination state before performing maintenance operations
  • Document the reason when deferring destinations for audit and troubleshooting purposes
  • Monitor alert logs for archive-related errors after re-enabling destinations
  • Use the scope=both parameter to persist changes across database restarts: alter system set log_archive_dest_state_2 = 'defer' scope=both;
  • In Data Guard environments, coordinate with the standby database team before changing destination states

References

Posts in this series