From oracle-l-bounce@freelists.org  Fri Jul 29 09:26:29 2005
Return-Path: <oracle-l-bounce@freelists.org>
Received: from air891.startdedicated.com (root@localhost)
 by orafaq.com (8.12.10/8.12.10) with ESMTP id j6TEQT31029196
 for <oracle-l@orafaq.com>; Fri, 29 Jul 2005 09:26:29 -0500
X-ClientAddr: 206.53.239.180
Received: from turing.freelists.org (freelists-180.iquest.net [206.53.239.180])
 by air891.startdedicated.com (8.12.10/8.12.10) with ESMTP id j6TEQHIP029136
 for <oracle-l@orafaq.com>; Fri, 29 Jul 2005 09:26:18 -0500
Received: from localhost (localhost [127.0.0.1])
 by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id D09651D9C5E;
 Fri, 29 Jul 2005 09:26:10 -0500 (EST)
Received: from turing.freelists.org ([127.0.0.1])
 by localhost (turing [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 13474-01; Fri, 29 Jul 2005 09:26:10 -0500 (EST)
Received: from turing (localhost [127.0.0.1])
 by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 51B591DA168;
 Fri, 29 Jul 2005 09:26:10 -0500 (EST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=Pdjv9b4l7zANohrkfUQ4W5uf4Ac3jZyHVN1a66PgWx1PgJQoPdpMlips1WDSqf0neudcdb3jPiY18RjR5+oXGYaO2kMunBVwtt9cz0uatGXFEpttmWkacfaPnU2pDUaDCeqZI0GsOShJKVueMF3IcPUvSVdx5euDUSw/UHaqHBM=
Message-ID: <be592d5505072907247e819217@mail.gmail.com>
Date: Fri, 29 Jul 2005 15:24:18 +0100
From: David Sharples <davidsharples@gmail.com>
To: oracle-l <oracle-l@freelists.org>
Subject: dataguard / applying archive logs
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by Ecartis
Content-Disposition: inline
X-archive-position: 23047
X-ecartis-version: Ecartis v1.0.0
Sender: oracle-l-bounce@freelists.org
Errors-To: oracle-l-bounce@freelists.org
X-original-sender: davidsharples@gmail.com
Precedence: normal
Reply-To: davidsharples@gmail.com
X-list: oracle-l
X-Virus-Scanned: by amavisd-new-20030616-p9 (Debian) at avenirtech.net
X-mailscan-MailScanner-Information: Please contact the ISP for more information
X-mailscan-MailScanner: Found to be clean
X-MailScanner-From: oracle-l-bounce@freelists.org
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on 
 air891.startdedicated.com
X-Spam-Status: No, hits=-3.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
 version=2.63

Hi, 9.2.0.5 Linux

Got a physical standby database which is going to be in read only mode
for a number of weeks.

The archive logs from the primary are naturally going to build up on
the server read to be applied.

What we want to be able to do is only apply one days archive logs at a
time, before putting it in read only mode then doing out work on it
then putting back to managed recovery and apply the next days logs

So on the primary (a 4 node RAC) we will note the log sequence numbers
at the end of each working day

So say for example at the end of day one, we have these logs

thread#1 log 1
thread#2 log 1
thread#3 log 1
thread#4 log 1

When we put the standby into managed recovery can we say only apply up
to sequence 1 for each thread?  It should be possible if someone was
watching the logs being applied and cancelling managed recovery but
that is dangerous and prone to failure.

Anyway this can be done automatically

Thanks
--
http://www.freelists.org/webpage/oracle-l

