If your primary has huge load or if there are huge gap on your standby, you may need to increase your apply rate on your standby database.
Do not forget your standby server’s CPU and Disk should be strong enough for this actions.
Here is the steps
- First let us check current gap:
NAME | VALUE | TIME_COMPUTED |
---|---|---|
transport lag | +00 00:00:53 | 03/02/2022 09:54:17 |
apply lag | +07 05:25:53 | 03/02/2022 09:54:17 |
- Check related parameter on Standby database
SQL> show parameter PARALLEL_EXECUTION_MESSAGE_SIZE NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ parallel_execution_message_size integer 16384
Let us change parameter
SQL> alter system set parallel_execution_message_size=32680 scope=spfile sid='*'; << reboot standby database
- Start parallel recovery on stabdby database
SQL> alter database recover managed standby database using current logfile disconnect from session parallel 64;
- Check current gap:
NAME | VALUE | TIME_COMPUTED |
---|---|---|
transport lag | +00 00:00:00 | 03/02/2022 09:54:17 |
apply lag | +03 04:35:03 | 03/02/2022 10:04:57 |
Reference:
DATA GUARD REDO APPLY AND MEDIA RECOVERY BEST PRACTICES
http://www.oracle.com/technetwork/database/features/availability/maa-wp-10gr2-recoverybestpractices-131010.pdf
Bir Cevap Yazın