From oracle-l-bounce@freelists.org  Wed Jul  7 01:55:00 2004
Return-Path: <oracle-l-bounce@freelists.org>
Received: from air189.startdedicated.com (root@localhost)
 by orafaq.com (8.11.6/8.11.6) with ESMTP id i676sjR08009
 for <oracle-l@orafaq.com>; Wed, 7 Jul 2004 01:54:55 -0500
X-ClientAddr: 206.53.239.180
Received: from turing.freelists.org (freelists-180.iquest.net [206.53.239.180])
 by air189.startdedicated.com (8.11.6/8.11.6) with ESMTP id i676sZ607979
 for <oracle-l@orafaq.com>; Wed, 7 Jul 2004 01:54:45 -0500
Received: from localhost (localhost [127.0.0.1])
 by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP
 id 6379472C243; Wed,  7 Jul 2004 01:36:02 -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 05729-36; Wed,  7 Jul 2004 01:36:02 -0500 (EST)
Received: from turing (localhost [127.0.0.1])
 by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP
 id B07C872C074; Wed,  7 Jul 2004 01:36:01 -0500 (EST)
Received: with ECARTIS (v1.0.0; list oracle-l); Wed, 07 Jul 2004 01:34:41 -0500 (EST)
X-Original-To: oracle-l@freelists.org
Delivered-To: oracle-l@freelists.org
Received: from localhost (localhost [127.0.0.1])
 by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id A11AA72C190
 for <oracle-l@freelists.org>; Wed,  7 Jul 2004 01:34:40 -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 02181-88 for <oracle-l@freelists.org>;
 Wed,  7 Jul 2004 01:34:40 -0500 (EST)
Received: from smtp-out3.xs4all.nl (smtp-out3.xs4all.nl [194.109.24.13])
 by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id E960072C074
 for <oracle-l@freelists.org>; Wed,  7 Jul 2004 01:34:39 -0500 (EST)
Received: from dbalert199.xs4all.nl (dbalert.xs4all.nl [213.84.185.230])
 by smtp-out3.xs4all.nl (8.12.10/8.12.10) with ESMTP id i676wNmu026776
 for <oracle-l@freelists.org>; Wed, 7 Jul 2004 08:58:23 +0200 (CEST)
Message-Id: <6.0.1.1.0.20040707085444.442641c0@pop.xs4all.nl>
X-Sender:  (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Wed, 07 Jul 2004 09:04:46 +0200
To: oracle-l@freelists.org
From: Carel-Jan Engel <cjpengel.dbalert@xs4all.nl>
Subject: Re: DR and reporting server 
In-Reply-To: <BAY19-F29WatWhitoT4000a8917@hotmail.com>
References: <BAY19-F29WatWhitoT4000a8917@hotmail.com>
Mime-Version: 1.0
Content-type: text/plain
X-Virus-Scanned: by amavisd-new at freelists.org
Content-Transfer-Encoding: 8bit
X-archive-position: 4534
X-ecartis-version: Ecartis v1.0.0
Sender: oracle-l-bounce@freelists.org
Errors-To: oracle-l-bounce@freelists.org
X-original-sender: cjpengel.dbalert@xs4all.nl
Precedence: normal
Reply-To: oracle-l@freelists.org
X-list: oracle-l
X-Virus-Scanned: by amavisd-new at freelists.org

Seema,
What do you want de reporting database to contain: All data current up to 
and including the last transaction of the primary, or will a daily refresh 
do the job? (This question is just about reporting requirements, not about 
availability/recoverability/data loss).

Referring to your previous post: LSB is there in 9i, but keep in mind that 
recovery of the transactions will only start _after_ a log-switch, even in 
maximum protection/maximum availability mode. Both modes will write your 
transaction synchronously to the Standby Redo Logfile, but not apply them 
instantly. So, reporting is always behind for a varying period of time. On 
the other hand, you can have your reporting database opened read-only, and 
switch it to recovery mode every night. Reporting will then be available 
through the day, just not including the transactions of the current day. DR 
will first recover the database up to the last transaction, and then bring 
up the database.

I found LSB rather instable, not suitable for DR (at least in 9i). For 
reporting it can be OK, depending on the datatypes you use.

When configured properly (listeners on both servers and tnsnames on 
clients) you can setup TAF (Transparent Application Failover). This will 
automatically reconnect the clients to the standby, after a 
switchover/failover.

When you need reporting up to the last transaction, 10g might help you. 
Still haven't found time to test, but the new DG feature of instant apply 
should circumvent the delay up to the logswitch.

Regards, Carel-Jan

===
If you think education is expensive, try ignorance. (Derek Bok)
===
At 01:35 AM 7/7/2004 -0400, you wrote:
>Hi,
>I have 2 db servers named DB1 and DB2.DB1 is as Primary db server and db2 is
>secondary server.I want to setup the server like followings.In case of
>disaster I can use db2 as primary servers by changing application
>configuration files on application box ,means DB2 should have read and write
>both features.In day to day basis we want db2 for reporting purposes.Which
>method would be best way to do this? If any good stuffs you guyes have
>please also suggest.ANy comments and suggestions are most welcome.
>thanks
>
>_________________________________________________________________
>FREE pop-up blocking with the new MSN Toolbar ­ get it now!
>http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
>
>----------------------------------------------------------------
>Please see the official ORACLE-L FAQ: http://www.orafaq.com
>----------------------------------------------------------------
>To unsubscribe send email to:  oracle-l-request@freelists.org
>put 'unsubscribe' in the subject line.
>--
>Archives are at http://www.freelists.org/archives/oracle-l/
>FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
>-----------------------------------------------------------------

----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to:  oracle-l-request@freelists.org
put 'unsubscribe' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

