Database Tuning (MOSC)

MOSC Banner

10.2 log_buffer auto-tuning

edited Jan 19, 2011 1:45AM in Database Tuning (MOSC) 4 commentsAnswered
MOSC note: 351857.1 states that log_buffer default size is auto-tuned by ASMM, and can not be lowered.  The spfile parameter now only specifies the lower limit in the same manner as the other auto-tuned pools.

I use ASMM to manage an Oracle database.  The database is experiences high log sync wait conditions.  OEM sends alerts when this condition happens that are disguised as lgwr blocking locks.

Quest Performance Anayzer says  the log_buffer size should be lowered to eliminate the waits.  Oracle has tuned the log_buffer size to 30MB, and the value was set by ASMM.

Is there a way in influence the automatic log_buffer tuning?  I would like it set lower to address the high log sync waits.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center