James,
As everyone else has already mentioned, either method is just fine.
Preferable is in the eye of the beholder. It really comes down to whatever
you are more comfortable with.
I guess my final response to him would be - thanks for the input - and to
go ahead and do it the way you want to.
The method that you propose is exactly the method that I used to upgrade a
10G Win NT database from 7.3.4 to 8.0.5. It worked flawlessly; though as I
remember I had to use the 7.3.4 client to do the import.
I also did an upgrade from 8.0.5 to 8.1.5 on a much larger database
(couldn't
of list ORACLE-L [EMAIL PROTECTED]
cc:
Subject:RE: DB Version upgrade with CreateDB/Import Risky???
James - I think that your system administrator is too much of a Microsoft
head. I can admit that to someone that knows nothing about Oracle, the
official method might sound
was of course done in Perl.
DENNIS WILLIAMS [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
05/05/2002 02:23 PM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
cc:
Subject:RE: DB Version upgrade with CreateDB/Import
Risky
to ORACLE-L
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
cc:
Subject:RE: DB Version upgrade with CreateDB/Import
Risky???
James - I think that your system administrator is too much of a Microsoft
head. I can admit that to someone that knows
Um, why not just install the software and then run that silly little
upgrade script they give you. Oh yeah, and change the oracle_home
parameter in the listener and change the compatible parameter in the
init.
Not that your way is wrong but seems to be a tad more then what you
need to do.
Hello James
In the last 2 years I did about 5-6 migrations from 7.3.4 to 8.1.6.0
and 10-12 from 8.1.6.0 to 8.1.6.3.4.
All done on NT with upgrades.
No scratch and rebuild. No problems at all.
Sorry to disappoint you.
Yechiel Adar
Mehish
- Original Message -
To: Multiple recipients of
James,
Your plan is perfectly acceptable. In fact, if time allows, it may
be preferable. If there are structural issues in the database (i.e.
migrated rows, tables in index tablespace (and vice versa)), this is one
method of killing two birds with one stone. It does require that there
is
James - I think that your system administrator is too much of a Microsoft
head. I can admit that to someone that knows nothing about Oracle, the
official method might sound safer. I have done the upgrades both ways for
many years, and I have never had a problem with the CreateDB/Import route. I
