Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

WAIT_FOR_GAP but sequence applied=YES

KSGJun 11 2017 — edited Jun 11 2017

Hi

11.2.0.4.0

3 Node RAC

Solaris 10

We have recently rebuild a standby server and started the MRP process. The mrp was running fine but now throws the error

Error:

Completed:  ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION

Sun Jun 11 20:06:40 2017

Media Recovery Waiting for thread 3 sequence 37185

Fetching gap sequence in thread 3, gap sequence 37185-37185

Sun Jun 11 20:08:01 2017

RFS[11]: Opened log for thread 1 sequence 44498 dbid 1811266939 branch 899070205

Archived Log entry 3625 added for thread 1 sequence 44498 rlc 899070205 ID 0x6ec45736 dest 2:

Sun Jun 11 20:08:34 2017

FAL[client]: Failed to request gap sequence

GAP - thread 3 sequence 37185-37185

DBID 1811266939 branch 899070205

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

------------------------------------------------------------

Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization

parameter is defined to a value that's sufficiently large

enough to maintain adequate log switch information to resolve

archivelog gaps.

------------------------------------------------------------

When I checked the sequence 37185, it shows applied.

SEQUENCE# NAME                                                                         ARC APPLIED

---------- -------------------------------------------------------------------------------- --- ---------

37185 +FRA/stdby/archivelog/2017_06_10/thread_2_seq_37185.5921.946327251       YES YES

Thanks..

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jul 9 2017
Added on Jun 11 2017
4 comments
1,241 views