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

MOSC Banner

Delaying the REDO application to Standby - But then what?

edited Feb 12, 2017 4:01AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 6 commentsAnswered

Hello everyone

We have a 11g primary and physical standby database and we are NOT using flashback on either the primary or standby

We have a question

Lets suppose we have the primary database on SEQ # 100 and standby database is in synch with primary

Now we make some database changes on the primary database but we dont want those database changes to be propagated over

to the standby database so BEFORE we apply those changes on the primary database we would set the log_archive_dest_state_2 to DEFER on the primary database as this would help to not to ship the REDO out to primary. Now as a result of those database changes, the archive log seq on primary database bumped to 110 (from 100). Those are not yet shipped OR applied on to the standby since we set the log_archive_Dest_state_2 to DEFER

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