Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: LOG_SMALL_ENTRY_MAX_SIZE

Re: LOG_SMALL_ENTRY_MAX_SIZE

From: Mohamed Buhari <mbuhari_at_assigncorp.com>
Date: 28 Jan 2000 13:03:21 EST
Message-ID: <3891D9E8.998FEC96@assigncorp.com>

LOG_SMALL_ENTRY_MAX_SIZE is maximum size of redo entry taht can be copied on the redo allocation latch. The thumb rule is

1.Try to tune the redo allocation latch if the contention is high . 2.On a multicpu system, allocation latch contention can be reduced by decreasing the value of LOG_SMALL_ENTRY_MAX_SIZE and by increasing the value of LOG_SIMULTANEOUS_COPIES to 2*(no of cpus). 3.Go by iterative process. Use the following query to find the contention level :

SELECT ln.name, gets, misses, immediate_gets, immediate_misses FROM v$latch l, v$latchname ln
WHERE ln.name IN (’redo allocation’, ’redo copy’) AND ln.latch# = l.latch#
/

Mohamed
ORACLE DBA Christ Follower wrote:

> Has anyone try to tune Oracle redo allocation latch by changing
> LOG_SMALL_ENTRY_MAX_SIZE and LOG_ENTRY_PREBUILD_THRESHOLD on a multiple
> CPU environment? I can't find any decent explanation from the Oracle
> online document. Your comment is greatly appreciated.
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Fri Jan 28 2000 - 12:03:21 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US