Sizing your logfiles to switch every x minutes is next to impossible in the real world. How fast a logfile fills up is directly proportional to the transaction volume. If you size your logfiles to swith every x minutes during the heaviest transaction load, they will be oversized for normal load and might not even switch at other times. If you size your logfiles for normal load, they may switch quickly during peak periods. The key is to strike a balance between recoverability and performance with the business will dictate.


Kishore has a reasonable request. "How do I make sure my database does a logswitch every x minutes?" As several have suggested, it can only be done via a scheduled job (cron, batch, dbms_job, etc.) There are currently no init.ora parameters that will periodically force a log switch.