Syntax is simple:
oracle [prod] backups $ sqlplus / as sysdba
SQL*Plus: Release 18.104.22.168.0 Production on Fri Sep 16 07:14:23 2016
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Oracle Database 11g Enterprise Edition Release 22.214.171.124.0 – 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> alter system set archive_lag_target=900 scope=both;
When do you set this and why? Here’s my take:
This parameter forces a log switch every X seconds – 900 seconds in the example above.
If you have a variable load, not at all unusual in fact from my experience most databases have a great variation of redo log ver time, at times generate. During the hours of operation when redo log generation is at it’s peak it is generally advantageous to increase the size of your redo logs and increase the number of groups.
Then when the database idles down, if you do not set ARCHIVE_LAG_TARGET the database may not experience enough activity go force a log switch. ARCHIVE_LAG_TARGET takes care of this for you.