How to Manually Determining and Resolving Archive Gaps in ASM (Copy archivelog in ASM using RMAN) [I

How to Manually Determining and Resolving Archive Gaps in ASM (Copy archivelog in ASM using RMAN) [ID 1271114.1]
		修改时间 04-JAN-2012     类型 HOWTO     状态 MODERATED

In this Document
  Goal
  Solution

---

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 11.2.0.1 - Release: 10.2 to 11.2
Information in this document applies to any platform.

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

1. Check for the GAP,

On standby,



2. On primary Check the location where the missing logfiles exist.

SELECT NAME FROM V$ARCHIVED_LOG WHERE THREAD#=<n> AND DEST_ID=<n> AND SEQUENCE# BETWEEN <LOW_SEQUENCE#> AND <HIGH_SEQUENCE#>;


For example,





3. Use RMAN to copy to someother local filesystem.




Do the same for all the logs.

4. SCP to standby.

scp /u01/app/oracle/ARC00001113_0732997804.001 drs1.idc.oracle.com:/u04/standby/

5. Register manually by mentioning the copied file location.

On standby,