10g,无论怎么该LOG_BUFFER ,都是保持14242816,估计是BUG

10g,中用了自动内存管理,在INIT.ORA 文件手动设置了LOG_BUFFER = 4194304 ,但不关是去掉哪个参数,还是加上,

DB 启动以后看到的结果都是14242816..

我已经提交给METALINK 了,已经3天了,他们一直在"Work in process" .感觉是BUG 的可能性很大..

[@more@]

Subject:	The Log_buffer Cannot be Changed In 10g R2
	Doc ID:	Note:351857.1	Type:	PROBLEM
	Last Revision Date:	14-MAR-2006	Status:	MODERATED

In this Document
Symptoms
Cause
Solution
References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.1
This problem can occur on any platform.

Symptoms

In customer environment, no matter what value is specified for the log_buffer, the buffer size remains at @14mbs

In 10G R2 Reference manual, it states that this parameter can no longer be modified and its set by default to 512K or 128K * the cpu count in the server. The document is in error.

Cause

@From Bug 4592994....

In 10G R2, Oracle combines fixed SGA area and redo buffer [log buffer] together. If there is a free space after Oracle puts the combined buffers into a granule, that space is added to the redo buffer. Thus you see redo buffer has more space as expected. This is an expected behavior.

"In 10.2 the log buffer is rounded up to use the rest of the granule...

@ From bug 4930608...
@ The granule size can be found from the hidden parameter "_ksmg_granule_size" and
@ in your case is probably 16Mb".

Solution

Log_buffer can no longer be modified and will be set by default by Oracle.

References

Bug 4930608 - Unable To Change Log_Buffer In 10g R2

ITPub博客

10g,无论怎么该LOG_BUFFER ,都是保持14242816,是BUG

Applies to:

Symptoms

Cause

Solution

References

最新文章