RMAN Removes Archived Redo Logs Required By Integrated Extract When Using A BACKED UP TO Policy (Doc ID 1990815.1)

Last updated on FEBRUARY 22, 2019

Applies to:

Symptoms

RMAN removes archived redo logs required by Integrated Extract when using a BACKED UP TO archive deletion policy

When you query to find the archived log file based on SCN, they appear to have been deleted due to RMAN policies--archive logs are backed up every two hours.  The logs are then deleted after they've been backed up twice.

GGSCI (devoradb01.wwt.com) 3> info ERPEXT

EXTRACT    ERPEXT    Last Started 2015-01-27 10:50   Status STARTING
Checkpoint Lag       00:00:02 (updated 01:08:06 ago)
Process ID           1577
Log Read Checkpoint  Oracle Integrated Redo Logs
                    2015-01-27 12:59:39
                    SCN 2975.3281272024 (12780808977624)

SQL>select name, thread#, sequence#, status, first_time, next_time,
first_change#, next_change#
from v$archived_log
where 12780808977624 between first_change# and next_change#;

THREAD# SEQUENCE# STATUS  FIRST_TIME                NEXT_TIME              FIRST_CHANGE#              NEXT_CHANGE#

1         7955      D     1/27/2015 12:10:07 PM     1/27/2015 1:04:35 PM   12780807428753             12780809060959
2         6060      D     1/27/2015 12:10:09 PM     1/27/2015 1:21:35 PM   12780807429222             12780809646243

'D' in the STATUS column shows that the archive log has been deleted from the disk

SQL>select capture_name, start_scn, first_scn,
CAPTURED_SCN,APPLIED_SCN,REQUIRED_CHECKPOINT_SCN from dba_capture where
CAPTURE_NAME like '%ERPEXT';


CAPTURE_NAME      START_SCN             FIRST_SCN             CAPTURED_SCN        APPLIED_SCN          REQUIRED_CHECKPOINT_SCN
OGG$CAP_ERPEXT  12780649471976    12780649471976     12780808977701     12780649694918    12780649694918

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.