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

MOSC Banner

How do we resolve the gap on standby database ?

edited Mar 24, 2017 3:53PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 8 commentsAnswered ✓

Hi,

We have a physical standby database to the production primary.

Recently, we created a restore point on standby and activated this standby to perform some tests.

After the tests, we flashed back to the restore point which was successful.

We started the managed recovery, but now we are getting the error:

FAL[client]: Failed to request the gap sequence

GAP - thread 1 sequence 1-1

FAL[client]: all defined FAL servers have been attempted.

The problem is that the standby created its own archive log sequence 1 through 13 when it was open.

Prior to OPEN - The sequence number - 74733

Current Sequence of PRIMARY - 74772.

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