From:Steve Adams
Date:06-Sep-2000 23:59
Subject:   log_small_entry_max_size

Yes, the log_small_entry_max_size parameter is system modifiable with immediate effect from 7.3 to 8.0.


I went to your web site and was most impressed by the volume of knowledge that is available to us "newbie" oracle dbas. I will set the log_small_entry_max_size to 0 and examine the effects over the next few days. BTW, can this parameter be changed and have effect while the database is open or is it a init.ora parameter set at startup?


I suggest that you drop the small copy threshold to zero. Beyond that, you may not have a problem. The issues are explained on the Ixora web site.


I am starting to wade through all of the statistics I am gathering on my Oracle db and have come across an issue with redo copy contention. I have the log_small_entry_max_size set to 80 and the log_simulataneous_copies=6. The redo entries are 8,646,492 and the redo small copies are 2,497,986. I am thinking of increasing the last parameter to 12 since I have six cpus on this node and dropping the log_small_entry_max size to 40k to reduce the number of redo small copies but would like some thoughts from the group before doing so.