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

MOSC Banner

How to get physical standby database to apply redo immediately upon receipt?

edited Sep 24, 2013 10:12PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 2 commentsAnswered ✓
Oracle 11.2.0.3.0, Data Guard configured on RHEL x86-64.

Prior to some setting changes (none of which should have affected performance), the Physical Standby database used for reporting would apply changes made in the Primary Database nearly immediately.  I cannot figure out how it happened, but now the changes are only visible in the Standby Database (which is in READ ONLY WITH APPLY mode) after forcing a log switch on the Primary Database.

What setting makes the Standby Database wait to apply redo until a log switch occurs on the Primary Database?  Both Primary and Standby are in the default "High Performance" mode.

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