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

MOSC Banner

force logging was disabled after switchover

edited Dec 19, 2014 10:05AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 4 commentsAnswered

RDBMS 11.2.0.4.  Force logging was enabled from both standby and primary after the standby database and dataguard broker were created.  After switchover, the force logging was disabled on a new primary.

There is another standby database configuration, the force logging was enabled from both primary and standby manually after the standby database was created, but BEFORE the dataguard broker was created. After a switchover, the force logging was still enabled on new primary database.

What made this difference?  Thanks in advance

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