ARCHIVE_LAG_TARGET parameter limit to 300 is degrading performance

Question

I've noted that CPU/IO increaces in a frequency of 5 minutes, degrading performance.
It is in sync with de redo log switch, fixed on 300 seconds with the paramter ARCHIVE_LAG_TARGET.
It cannot be changed to 0 or larger numbers as Oracle on premise can be.

Is there any workaround for this issue? Why this parameter allows 300 seconds as maximum, when the Oracle documentation show that about 30 minutes is the recommended value to avoid performance issues?
Thanks

SV · Answer

The archive_lag_target is set to 300 because in RDS Oracle RPO is 5 mins and that requires redo log to be switched every 5 mins and be stored in S3 bucket for recovery purposes. If this operation is causing a performance issue for your database  then you need to allocate more resources to your RDS database e.g. bigger instance and storage with more IOPS and throughput. You can change archive_lag_target parameter in Oracle databases running on EC2 or in RDS Custom for Oracle.

rePost-User-3648123 - FernandoI · Answer

Hello
ok,  It is data I cannot find in documentation..
Thank you very much

ARCHIVE_LAG_TARGET parameter limit to 300 is degrading performance

Relevant content