Redo latch contention

Hi All,

        I had some situation of Redo Allocation and copy latch contention as stated in following output.....

SQL> SELECT substr(NAME,1,18) NAME, GETS,MISSES, IMMEDIATE_GETS, IMMEDIATE_MISSES
FROM V$LATCH WHERE NAME LIKE '%redo%'
/

NAME                     GETS     MISSES IMMEDIATE_GETS IMMEDIATE_MISSES

------------------ ---------- ---------- -------------- ----------------

redo allocation         74878         16              0                0

redo copy                 114        100          53756              232

redo writing            30219          1              0                0

3 rows selected.

        Realizing small contention on redo allocation latch, I increased the value of "log_small_entry_max_size" from 80 to 90.

        But this would definitely overload (already suffering) redo copy latches, so I increased the value of log_simultaneous_copies from 2 to 6.

        This sorted out redo latch contention, but somewhere in FM it's mentioned that value of log_simultaneous_copies shouldn't be more than
(2 * #_of_CPUs). Again I know that the CPU is "not" heavily used so far.
So...

1. Is it OK to set log_simultaneous_copies higher than 2*CPU. What are the golden rules. I have seen some authers not mentioning this.
2. Why this parameter is missing from Oracle 8i?? Has Oracle changed the algorithm?? What is the new strategy to handle redo latch contention??

        Interestingly, in Oracle 8i (Oracle 8.1.6) Tuning Manuals they still talk of these parameters(which are made obsolete)...

        Appreciate your inputs ;-)

Cheers,
Rajesh

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Rajesh Dayal
  INET: Rajesh_at_ohitelecom.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (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).