Redo I/O Is Higher On Active Data Guard Physical Standby Than Primary
Last updated on APRIL 19, 2017
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 and later
Information in this document applies to any platform.
The physical standby becomes un-synchronized with the primary and 'apply lag' may be found to grow via v$dataguard_stats and/or v$standby_event_histogram views.
When database performance metrics are captured for the physical standby it may appear that 'db file parallel read' waits or related datafile read I/O waits appear to spike heavily.
The redo being applied at the time is related to Automatic Optimizer Statistics against three very large partitioned tables.
Initialization parameter DB_LOST_WRITE_PROTECT has been set on both primary and physical standby databases.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms