RE: log_buffer Value setting NOT effective ?
Date: Thu, 22 May 2008 13:21:19 +0530
Even though log_buffer is set to 1M, on Database Startup it is automatically getting reset to 14MB (shown below)
Qs 1 - Is there a Patch for this Bug?
Qs 2 - Alternatively, Can _ksmg_granule_size be manually set to a small Value e.g. 1M? Is it safe to do so?
Cheers & Thanks indeed
P.S. Metalink Note:351857.1 posting:-
This is already explained in bug 4592994.<https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_id=4592994&p_database_id=BUG>
In 10.2 the log buffer is rounded up to use the rest of
the granule. The granule size can be found from the
hidden parameter "_ksmg_granule_size" and in your case
is probably 16Mb. The calculation for the granule size
is a little convoluted but it depends on the
number of datafiles etc..
- CAUTION - Disclaimer ***************** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS******** End of Disclaimer ********INFOSYS***