How to Manually Determining and Resolving Archive Gaps in ASM (Copy archivelog in ASM using RMAN)
Last updated on DECEMBER 06, 2017
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 to 126.96.36.199 [Release 10.2 to 11.2]
Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [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***
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.
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