Xref: alice comp.databases.oracle.server:56853
Path: alice!news-feed.fnsi.net!newsxfer.visi.net!newsfeed.wirehub.nl!news.wirehub.nl!not-for-mail
From: "Kristiaan J. Kolk" <akolk@gelrevision.nl>
Newsgroups: comp.databases.oracle.server
Subject: Re: redo copy latch sleep 80% ??
Date: Sun, 11 Jul 1999 21:03:50 +0200
Organization: Wirehub! Internet, The Netherlands (complaints to abuse@wirehub.net)
Lines: 25
Message-ID: <3788EA96.BE7A6D07@gelrevision.nl>
References: <37821474.0@news.qgraph.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.9 i686)
X-Accept-Language: en
Cache-Post-Path: newsreader1.wirehub.nl!root@cp238erm06.gelrevision.nl
X-Cache: nntpcache 2.3.3 (see http://www.nntpcache.org/)

You don't do anything. As this is most likely no issue when looking at
the overall system performance. Making any changes on these hit or sleep
ratios on these latches will not help that much ......

mail me if you need more info.

Anjo.

Ron Vissers wrote:

> Hi,
>
> I'm tinkering with Quest's Instance monitor and its detecting issues
> with the redo copy latches.
>
> The tuning books instruct me to increase LOG_SIMULTANEOUS_COPIES to
> twice the number of cpu's we have.
>
> Unfortunately, we're already there and have been there for some time.
> (3 cpu's, 6 L_S_C's)
>
> Where do I go from here?
>
> Ron