Re: switch DG to 64bit with no downtime?
- From: Ilmar Kerm <ilmar.kerm@xxxxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Mon, 26 Mar 2012 20:22:23 +0300
On Mon, Mar 26, 2012 at 7:26 PM, kathryn axelrod <kat.axe@xxxxxxxxx> wrote:
> Hi,
>
> I was hoping there might be some kind of unconventional process
> similar to doing a rolling upgrade with a logical that would allow all
> of the 64bit conversion steps to be run on the standby before
> switchover. However, based on a few offline replies, I'm assuming
> there is no such pure-DG option; thus my modified question is –
>
> Does anyone have any suggestions of how convert from 32bit to 64 with
> no more downtime than the usual switchover blip (including ideas that
> involve extra servers or 3rd party tools)?
>
> As it is an OLTP system, were I to attempt an imp/exp to a 3rd box, by
> the time it was imported and the 3rd db was converted, the data loss
> would be far too great…I was also thinking that perhaps I could set up
> an additional 64bit db and send over the data via Streams, but as per
> 418755.1, source and downstream sites must have the same bitness.
> Nonetheless, I’m hoping that someone has a clever method they used or
> any ideas of how to make this work (no matter how big or small, all
> are appreciated!)
I see 418755.1 mentioning the same platform only about downstream
capture (ship logfiles to destination, capture changes on
destination).
Using Streams without downstream capture should work (capture changes
on source, ship messages over databaselink to destination).
--
Ilmar Kerm
--
//www.freelists.org/webpage/oracle-l
Other related posts:
