Re: Moving then migrating database

I’ve done migrations in a similar method to what you describe without incident. Instead of using incrementals, I :

 -ran a full backup/restore right before the maintenance window
 -applied the few archive logs that occurred between said restore and the window
 -shutdown the original db and applied final archive log(s) to new db
 -started new db

If the desired heterogeneous configuration is supported, using Data Guard as Rodrigo suggests also works well.

As for the upgrade portion, unless you have to do both at the same time, I’d suggest separating this from the move. New hardware, plus a different version OS, plus an upgraded db leaves you with several variables to sort through if an issue comes up.

On Wed, Jun 6, 2012 at 7:15 AM, Sandra Becker <sbecker6925_at_gmail.com> wrote:
> Currently:
>     OS:  SLES10
>     Oracle:  10.2.0.5
> Moving to:
>    OS:  SLES11
>     Oracle:  11.2.0.2  (the latest version for zLinux when we began
> migrating)
>

...
>
> Question:  Will the following work?
>
>   1. Using last level 0 backup of the database, restore it to the new
>   VM/storage a few days before the actual migration date.
>   2. Using the incremental backups taken daily, run the restores on the
>   new VM/storage.
>   3. On the migration date:
>      - shutdown the database
>      - run a final incremental backup
>      - restore the final incremental to the new VM/storage
>      - upgrade the database to 11g
>

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