How to Manually Determining and Resolving Archive Gaps in ASM (Copy archivelog in ASM using RMAN)
(Doc ID 1271114.1)
Last updated on JULY 17, 2023
Applies to:
Oracle Database Cloud Exadata Service - Version N/A and laterOracle Database Backup Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - 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.
NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.
For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:
Primary Database:
DB_NAME: PRIM
Standby Database:
DB_UNIQUE_NAME: STDBY
Diskgroup name is +DGROUP2
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| OPTION -I : Copy archivelog |
| OPTION II : Take backup of archivelog |