Re: Exp/Imp or Migrate ?

I've seen some 7.3.4 > 8.0.5 > 8.1.6 and 7.3.4 > 8.1.5 migrations work well. I've also seen some fail miserably - usually when the messages in the Alert.log have been ignored or misunderstood.

Assuming you have a clean database, everything working well and no strange messages in the alert.log, you should have a clean migration.

However, there are a number of reasons for building a nice, clean 8.1.7 environment (note - if possible, move straight to 8.1.7, as 8.1.6 will be desupported soon) Some of these reasons include the block size change you mention. Those reasons are listed in the 'migration' related manuals, which you can also get at http://technet.oracle.com

/Hans

"The Tentative DBA...." wrote:

> In a couple of months time I'll have to take a production database from
> 7.3.4 to 8.1.6. (Solaris 2.7). I'm considering the merits/demerits of
> the two possible routes and would appreciate any advice. Are there any
> known problems with a direct migration from 734 to 816 if I chose to go
> that route ?
>
> I need to change the block size urgently on the existing database and
> so would like to go the export import route. What makes me a little
> reluctant is that I've little or no experience with 816 and would be
> anxious to ensure that I rebuild the database correctly before I come
> around to doing the import.
>
> I had prepared for doing this job previously going from 734 to 806 and
> I had structured the database 'recreation' along the following lines.
> I'd appreciate it if anyone could review the steps to make sure they're
> complete in terms of 816;
>
> 1. Create database statement defining system datafiles and redo logs;
> 2. Run Catalog and Catproc
> 3. Create additional tablespaces, datafile and rollback segments
>
> Thanks,
>
> Mick.
>
> --
> If it isn't backed up, it's not worth shit !
>
> Sent via Deja.com
> http://www.deja.com/
Received on Sun Apr 29 2001 - 21:44:34 CDT