RE: 8.1.5 upgrade paths to 10.2.x
- From: "Goulet, Dick" <richard.goulet@xxxxxxxxxxxxx>
- To: "LS Cheng" <exriscer@xxxxxxxxx>
- Date: Tue, 16 Oct 2007 14:40:31 -0400
Would not call them "exotic", just a darn lot faster & less error prone.
______________________________________________________________
Dick Goulet / Capgemini
North America P&C / East Business Unit
Senior Oracle DBA / Hosting
Office: 508.573.1978 / Mobile: 508.742.5795 / www.capgemini.com
Fax: 508.229.2019 / Email: richard.goulet@xxxxxxxxxxxxx
45 Bartlett St. / Marlborough, MA 01752
Together: the Collaborative Business Experience
______________________________________________________________
________________________________
From: LS Cheng [mailto:exriscer@xxxxxxxxx]
Sent: Tuesday, October 16, 2007 2:36 PM
To: Goulet, Dick
Cc: zimsbait@xxxxxxxxx; development@xxxxxxxxxxxxxxxxx;
oracle-l@xxxxxxxxxxxxx
Subject: Re: 8.1.5 upgrade paths to 10.2.x
with a 60gb database I wouldnt mess around with the exotic ways...
On 10/16/07, Goulet, Dick <richard.goulet@xxxxxxxxxxxxx> wrote:
Better idea, which I've done recently. Upgrade DB to 8.1.7 then to
10.2, approximate time 3 hours. Then use Transportable database to move
datafiles to AIX, convert them with RMAN & restart your db. This entire
process on HP-UX to AIX took 18 hours total for a 700GB database. Would
have been faster if we had paralleled things.
______________________________________________________________
Dick Goulet / Capgemini
North America P&C / East Business Unit
Senior Oracle DBA / Hosting
Office: 508.573.1978 / Mobile: 508.742.5795 / www.capgemini.com
Fax: 508.229.2019 / Email: richard.goulet@xxxxxxxxxxxxx
45 Bartlett St. / Marlborough, MA 01752
Together: the Collaborative Business Experience
______________________________________________________________
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of z b
Sent: Monday, October 15, 2007 3:53 PM
To: development@xxxxxxxxxxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: 8.1.5 upgrade paths to 10.2.x
To "parallelize" you could use limit the dump files to, say, 500MB
dump files. (filesize parameter)
Ftp the files and start the import while the export is still running.
Of course - test a couple of times before actually scheduling. :)
On 10/15/07, development@xxxxxxxxxxxxxxxxx
< development@xxxxxxxxxxxxxxxxx <mailto:development@xxxxxxxxxxxxxxxxx> >
wrote:
> Hello group!
>
> I have got a tricky problem at hand - migrate an Oracle 8.1.5 on
Solaris
> 7 database to 10.2.0.x on AIX. The problem here is that I am not
allowed
> much downtime. Having started with Oracle 8i I am not too sure how
that
> can be done. Obviously to get from 8.1.5 I have to go to 8.1.7 first,
a
> direct update is supported which is good. I am thinking of a new
Oracle
> home on the same machine, copying the database and migrating it.
>
> From there on I don't see any other way than exp/imp using pipes for
> faster processing. It is a bit of a mystery how I can keep the
downtime
> low, the database is some 60GB in size btw.
>
> Thanks for any input on this,
>
> Martin
>
>
>
>
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
--
//www.freelists.org/webpage/oracle-l
This message contains information that may be privileged or confidential
and is the property of the Capgemini Group. It is intended only for the
person to whom it is addressed. If you are not the intended recipient,
you are not authorized to read, print, retain, copy, disseminate,
distribute, or use this message or any part thereof. If you receive this
message in error, please notify the sender immediately and delete all
copies of this message.
--
//www.freelists.org/webpage/oracle-l
This message contains information that may be privileged or confidential and is
the property of the Capgemini Group. It is intended only for the person to whom
it is addressed. If you are not the intended recipient, you are not authorized
to read, print, retain, copy, disseminate, distribute, or use this message or
any part thereof. If you receive this message in error, please notify the
sender immediately and delete all copies of this message.
Other related posts:
