Data Guard 11gr2 broker log messages, shutdown Primary database in x seconds
edited May 9, 2014 12:00PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 7 commentsAnswered
Situation: Heavy load with many Log switches taking place.
Sql Loader process are starting at 12:30AM each night
I get Lagging from the Borker as expected.
This in the Broker alert log every night during this time period of heavy load. drcxxxxxxxxxxx.log on the Primary database.
Should I be concerned about this? What does it really mean? Network issue? Observer or Broker issue?
04/23/2014 00:31:07
LGWR: FSFO - transaction cannot commit without exceeding
30 second lag limit, waiting for permission to proceed
LGWR: Target standby would lag if transaction was allowed to
commit Last redo was
applied on FSFO target standby at 04/23/2014 00:30:36
0