The migration method can be a bit tricky, but I'm curious as to what
part of it was causing your problems.

At a previous job I pored over the migration manual for about 6 weeks
identifying which steps were necessary for our shop and which weren't,
and then automating the whole thing for push button migrations.

Used on several databases to go from 7.3.x and 8.0.x to 8.1.6 and 8.1.7.

Jared

PS.  The automation 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"???


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
have often had problems with the migrate method. When I went from Oracle 8
to 8i, finally had to give up on getting the migrate method to work. 
Dennis Williams
DBA
Lifetouch, Inc.
[EMAIL PROTECTED]


-----Original Message-----
Sent: Sunday, May 05, 2002 11:23 AM
To: Multiple recipients of list ORACLE-L


Hello fellow Oracle DBAs,

I really need your opinion on this matter:

I routinely do upgrades of Oracle software and databases on all types of
systems: Compaq Unix, Netware, Linux, etc. (as do we all from time to 
time).
On one Windows/NT 4 system where I am presently doing an upgrade from a
lower version of Oracle 8 to 8.1.7, I am dealing with a particular System
Administrator for the NT box who knows a little about Oracle, but that is
obviously laboring under some misconceptions.

He strongly believes that the ONLY way one should upgrade a database (once
the software has been upgraded) is to do a "migration" (presumably as
detailed in the Oracle Migration manual) and he is URGING me to do it this
way.

On small databases (i.e. less than 10G) where downtime is not an issue, 
the
way I have always done it and the way I intend to do it this case is:

(1) Take a full database "export" under the old version
(2) Install the Version 8.1.7 software
(3) Recreate from scratch the database under the new software
(4) Do a full database "import" to the new database.

For our systems, I as the DBA believe and have found this to be a fully
reliable, quick, and clean method and the preferable way to do it, rather
than go through the migration procedure. He on the other hand believes 
that
NOT doing it via the "migration" route is very "risky".

Without going into a long spiel with him about what an upgrade IS as far 
as
the database itself is concerned (i.e. the data dictionary objects being
brought up to the new version), and why the way I intend to do it with a
full import is perfectly acceptable to accomplish this, I'd like to just
offer this person the opinions of some of you out there in ORACLE-L List
Land where the Oracle DBA expertise is highly respected for its stature,
I.E. so he doesn't have to believe me.

In other words, I don't want to try to convince him against his
will......I'd rather have impartial competent experts give him unbiased
testimony. Thus I humbly solicit your opinion on this matter. I believe 
that
my above procedure is a simple and fully reliable way of bringing the
database up to the new software level......or perhaps it is ***I*** that 
am
laboring under the misconception???  May I please have your take on
this.....

Much appreciate,

JDamiano

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: James Damiano
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: DENNIS WILLIAMS
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).



-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: 
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to