Re: Taking export from SECONDARY_INSTANCE from 02 node RAC

From: Michael Austin <maustin_at_firstdbasource.com>
Date: Thu, 26 Feb 2009 19:35:15 -0600
Message-ID: <DpHpl.14592$as4.1339_at_nlpi069.nbdc.sbc.com>

shweta.kaparwan_at_googlemail.com wrote:
> Hi All
>
> We are at :
>
> Oracle 9.2.0.6
> HP Ux : 11.23
> RAC : 02 Node
> ( say node-A & node-B)
>
>
>
> Primary Instance is running in node-A & secondary instance running in
> node-B.
>
> All db connections goes to PRIMARY_INSTANCE , we control it via TNS.
> Hence at a given time PRIMARY_INSTANCE running in host-A is Active
> and SECONDARY_INSTANCE in host-B is UP but IDLE with respect to db
> connections. i.e. no connections goes to host-B.
>
>
> Now question:
>
> I want to start the export backup database ( size 50 GB) from host-B
> by connecting to SECONDARY_INSTANCE.
>
> i.e. my "exp" connection/session will be connecting to
> SECONDARY_INSTANCE in host-B.
>
> Whether this will cause " a ton of interconnect traffic all of a
> sudden as many of the blocks will have to be shipped for the first
> time to the other node".
>
> In simple words , how good it would be to export via
> SECONDARY_INSTANCE or are there any bad part of it in above scenario?
>
>
> Many Thanks
>
> Regards
>
> Shweta
>
>
>
>
>
>
>
>

If the second node is even up - see the others comments. Taking an export on a busy database (RAC or not) could result in an inconsistent db. Depending on what you are doing, that may suffice (creating an empty db for example?). If you need to be able to restore for DR purposes, use RMAN.

BTW 9i is no longer supported - if you value your database and your data, you would keep it in a supported state. Received on Thu Feb 26 2009 - 19:35:15 CST