How to Manually Determining and Resolving Archive Gaps in ASM (Copy archivelog in ASM using RMAN) (Doc ID 1271114.1)

Last updated on JUNE 06, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.2.0.1 [Release 10.2 to 11.2]
Oracle Database - Enterprise Edition - Version 11.2.0.4 to 11.2.0.4 [Release 11.2]
Information in this document applies to any platform.
***Checked for relevance on 10-JUNE-2013***
***Checked for relevance on 10-Dec-2015***

Goal

The note describes how to find a GAP and resolve it in case of ASM on both primary and standby or ASM on either primary or standby.

Solution

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