Analysis of optimal redo log size

Alert.log shows a very high frequency of redo log switches, only a few seconds between them; such aggressive log switches cause checkpoint hardly to keep pace with log switches and generate a lot of “CHECKPOINT NOT COMPLETE” in alert.log file. it not only happens during heavy activity period but also normal working hours. Waiting on “CHECKPOINT NOT COMPLETE” decreases system performance, as recommended, it can be solved in 2 manners:

1) use async_io or increases number of db writers to speed up checkpoint process

2) increase number of redo log groups to extend the cycle of reusing an old redo log

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: