RE: RMAN Duplication for Migration and Archived Logs

  • From: "Robert Freeman" <robertgfreeman@xxxxxxxxx>
  • To: <don@xxxxxxxxx>, "Alex Gorbachev" <ag@xxxxxxxxxxxx>
  • Date: Tue, 7 Aug 2007 18:42:52 -0600

Assuming 10g I am fairly sure your answers are yes, yes and yes,


Robert G. Freeman
Oracle Consultant/DBA/Author
Principal Engineer/Team Manager
The Church of Jesus Christ of Latter-Day Saints
Father of Five, Husband of One,
Author of various geeky computer titles
from Osborne/McGraw Hill (Oracle Press)
Oracle Database 11g New Features Now Available for Pre-sales on!
Sig V1.2

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Don Seiler
Sent: Tuesday, August 07, 2007 1:54 PM
To: Alex Gorbachev
Cc: oracle-l
Subject: Re: RMAN Duplication for Migration and Archived Logs

A friend also suggested that I might be able to do something similar
using Oracle Streams Replication to minimize downtime.

I've only just begun the Streams reading, but thought I'd ask some
questions to get a jump-start:

1. Are there any known hang-ups going from 32-bit to 64-bit?
2. Does Oracle Streams include sequences, or does it just do table
DDL/DML changes?
3. Does Oracle Streams propagate VPD changes?

If any of these are "no", then I think it's out.  One not-so-appalling
option would be to do as I did when I migrated from HPUX to RHEL:
create a new database, recreate pl/sql, tables and indexes (with
better organization than I have currently), have a perl script to
recreate users and privileges.  The appeal here is that the large bulk
(90%) of my ~1TB database is read-only on that day and could be
migrated (probably via datapump) well ahead of the downtime window.
Then during the downtime window I'd run a script to recreate the
sequences and VPD settings, then datapump the OLTP stuffs over to get
the DML for the day.

What do you fine folks think?  Doing it the hard way?


On 8/2/07, Don Seiler <don@xxxxxxxxx> wrote:
> On 8/1/07, Alex Gorbachev <ag@xxxxxxxxxxxx> wrote:
> > The simple approach is to create a standby database. I think it should
> > work 32 bit -> 64 bit as well.
> I just found this in Section 2.3.1 of the Data Guard Concepts and
> Administration Guide [1]:
> "All members of a Data Guard configuration must run an Oracle image
> that is built for the same platform.
> For example, this means a Data Guard configuration with a primary
> database on a 32-bit Linux on Intel system can have a standby database
> that is configured on a 32-bit Linux on Intel system. However, a
> primary database on a 64-bit HP-UX system can also be configured with
> a standby database on a 32-bit HP-UX system, as long as both servers
> are running 32-bit images."
> Has anyone proven this wrong?  Are my standby plans ruined?
> [1]
> --
> Don Seiler
> oracle:
> ultimate:

Don Seiler


Other related posts: