Developer and DBA Tips to Optimize SQL Apply
(Doc ID 603361.1)
Last updated on DECEMBER 28, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.2.0.3 [Release 10.2 to 11.2]Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.1.0.2 [Release 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Purpose
Developer and DBA Tips for Pro-Actively Optimizing SQL Apply
Utilizing Data Guard SQL Apply (logical standby database) will have zero impact on the primary database when configured with asynchronous redo transport. Some users, however, will be challenged to achieve standby apply performance that can keep pace with peak periods of primary workload. Keeping pace with primary workload is important to minimize failover time, and to enable queries and reports running on the logical standby database to return results that are up-to-date with primary database transactions.
Tuning SQL Apply or logical standby has significantly improved with every release to the point that SQL Apply 11g can keep up very high loads. However, there are certain workload profiles where SQL Apply rates may be sub-optimal compared to the rate at which the primary database is generating workload.
This note focuses on specific application use cases where SQL Apply performance may be sub-optimal. and describes pro-active developer and DBA best practices that can accelerate SQL Apply performance.
While the information contained in this note focuses on Oracle Database 11g Release 1 (11gR1), many of the same principals can be applied to Oracle Database 10g.
Details
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |