
Originally Posted by
engiri
One. Decrease your log buffer Say to 1mb (I dont know your current size but 1 m is normally good).
Two. You might be keeping other datafiles or temp files in the redo log area. Move redo to a separate device. Do not keep them in RAID 5.
Three. See the log file size, if frequent switches are there increase the size.
I also face frequent log switches in one of my db with solaris 8,
might be the undo the reason for the redo fast filling.
Your points 1.) and 3.) have nothing to do with log file sync wait event.
What the original poster realy need to check is if there realy is the need for apparent high commit rate. The most likely reason for log file sync event is when user issues a commit (or rollback). So he/she need to check who (or what) is causing frequent commits.
Jurij Modic
ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?