You are probably right but it was good to have V6-type control over the
mechanism. log_simultaneous_copies, log_small_entry_max_size (maximum
number of characters that was allocated when allocation latch was acquired)
and log_entry_prebuild_threshold (the size of redo after which the user
process was building redo entries, instead of LGWR) were easy to understand
and maintain. These days, I have no control. Do you remember X$KCBCH tables
(I'm not sure about the spelling of this one) that was helping you compute
"hit ratio" if there were few more block buffers? World certainly was simpler
before you and Cary destroyed the hit ratio. Shame on you :)!
On 2003.07.02 22:24, Anjo Kolk wrote:
Wrong alert in HP Open view (you can configure that) and (again) ignoring
other more relevant performance information ('High CPU usage'). I have never
seen a system where tuning the redo copy latches made a huge improvement in
performance.
Anjo.
--
Mladen Gogala
Oracle DBA
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Mladen Gogala
INET: [EMAIL PROTECTED]
Fat City Network Services -- 858-538-5051 http://www.fatcity.com
San Diego, California -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
Received on Wed Jul 02 2003 - 20:58:54 CDT
