Re: Upgrade 9 to 11 & Big Endian to Little Endian
- From: "Leyi Zhang (Kamus)" <kamusis@xxxxxxxxx>
- To: orcl@xxxxxxx
- Date: Fri, 3 Sep 2010 08:23:01 +0800
Hi orcl
1. Maybe you should know RMAN CONVERT will be a long time operation,
I'm not sure which is faster compared to a well tuned exp+imp work.
2. What is your database outage time window? several hours or several minutes?
3. You can use exp+imp for the initial step, then create material view
log on every important table in 9i database, and create material view
refresh ON PREBUILT TABLE in 10g database, when finally 10g data
synchronized with 9i data, then plan an database outage time (will be
very small. like several minutes) and drop the mv in 10g but leave the
tables, switch 10g database to production.
--
Kamus <kamusis@xxxxxxxxx>
Visit my blog for more : http://www.dbform.com
Join ACOUG: http://www.acoug.org
On Fri, Sep 3, 2010 at 5:01 AM, orcl <orcl@xxxxxxx> wrote:
> All - We have a bunch of databases on Solaris 9.2 (big endian) that need to
> be upgraded to 11.2 on Linux (little endian).
>
> Since 9i doesn’t have an rman convert datafile, what are the options to make
> the move in one shot?
>
> Im pretty sure imp/exp can do the smaller databases but most of them are
> large, so that won’t be an option.
>
> I bet another suggestion is to upgrade first to 10... then use rman convert,
> I don’t think management will support a "two hop" upgrade. (double work,
> double outage, double testing)
>
> Does anyone have firsthand experience of the hard and fast options for this
> situation?
>
> I did some initial research and its all saying imp/exp or go to 10 first.
>
> Im looking for other options. (if any)
>
> Much Appreciated
>
> Bob
>
>
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
