High Availability Data Guard, Sharding and Global Data Services (MOSC)

MOSC Banner

Archive Gap Resolution in ORACLE 11g

edited Oct 8, 2014 6:09AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 2 commentsAnswered

Basically There are 4 Possibilities to resolve an Archive Gap on a Standby Database.

  1. Automatic Gap Resolution
  2. FAL (Fetch Archive Log) Gap Resolution
  3. Manual Gap Resolution
  4. Roll forward using Incremental Backup (Physical Standby only)

I have two questions :

How oracle database decides which Methods of Gap Resolution need to be follow ? is there any algorithm or conditions ?

Last i heard somewhere that in ORACLE 11g, if there is archive log gap situation and we simply copy paste missing archive logs from primary to standby server archive_dest location.

database will be automatically do rest of the things, we do not need to register copied archive logs with standby database, is this correct ?

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center