Duplicate Copy of Foreign Archivelogs Created in Logical Standby (Doc ID 2233869.1)

Last updated on APRIL 18, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 10.1.0.2 to 12.2.0.1 [Release 10.1 to 12.2]
Information in this document applies to any platform.

Symptoms

Duplicate copy of Foreign Archive Logs were getting created in Logical Standby archive log destination.

When Foreign Archive Logs are deleted manually using RMAN, only the first copy gets deleted thereby maintaining the second copy indefinitely.

Only work around was to delete them manually from ASMCMD prompt.

 

As seen from RMAN and ASMCMD below, 2 copies of foreign archive logs were listed, but only 1 record found in the control file for each sequence.

So the auto cleanup would leave the second copy in ASM forever.

When Foreign Archive Logs are deleted manually using RMAN, only the first copy would get deleted, thereby maintaining the second copy in the ASM Disk Group indefinitely.

Only work around was to delete them manually from ASMCMD prompt.

 

--From RMAN

RMAN> list archivelog all completed after 'sysdate-1/360' ;

using target database control file instead of recovery catalog
List of Archived Log Copies for database with db_unique_name ORCL
=====================================================================

Key Thrd Seq S Low Time
------- ---- ------- - ---------
13880 2 1768 A 13-FEB-17
Name: +FRA/ORCL/ARCHIVELOG/2017_02_13/thread_2_seq_1768.3821.935831741

13881 2 1768 A 13-FEB-17
Name: +FRA/ORCL/ARCHIVELOG/2017_02_13/thread_2_seq_1768.1863.935831741

13882 3 1129 A 13-FEB-17
Name: +FRA/ORCL/ARCHIVELOG/2017_02_13/thread_3_seq_1129.3716.935831743

13883 3 1129 A 13-FEB-17
Name: +FRA/ORCL/ARCHIVELOG/2017_02_13/thread_3_seq_1129.1000.935831743

 

--From ASMCMD


ASMCMD> ls -lt

ARCHIVELOG UNPROT COARSE FEB 13 09:00:00 Y thread_3_seq_1128.2038.935831267
ARCHIVELOG UNPROT COARSE FEB 13 09:00:00 Y thread_3_seq_1128.3273.935831267
ARCHIVELOG UNPROT COARSE FEB 13 09:00:00 Y thread_3_seq_1129.1000.935831743
ARCHIVELOG UNPROT COARSE FEB 13 09:00:00 Y thread_3_seq_1129.3716.935831743

ASMCMD> pwd
+FRA/ORCL/ARCHIVELOG/2017_02_13

Changes

None.

Issue with log_archive_dest configuration.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms