Dataguard on 11.1.0.7 with Cascaded Physical Standby: WAIT_FOR_GAP status without gap
edited Dec 6, 2017 4:04AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 3 commentsAnswered
Hello,
I have a strange situation in a Dataguard 11.1.0.7 with cascaded physical standbys in which there is no gap, but the MRP process of the cascaded standby physical instance has the status WAIT_FOR_GAP.
The configuration is like this:
Primary: ORAPRO08
log_archive_config=DG_CONFIG=(ORAPRO08,SORAPRO08,STBORAPRO08
log_archive_dest_1=LOCATION=/arcpro8/arc8/ORAPRO08/arc VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=ORAPRO08
log_archive_dest_2=SERVICE=SORAPRO08 ASYNC DB_UNIQUE_NAME=SORAPRO08 VALID_FOR=(ONLINE_LOGFILE,PRIMARY_ROLE)
fal_client=STBORAPRO08
fal_server=SORAPRO08
Standby_local: SORAPRO08
log_archive_config=DG_CONFIG=(ORAPRO08,SORAPRO08,STBORAPRO08)
1