I'm in the middle of going from 8.1.7.4 to 10g right now. First we set
up an old Unix server and tested it on there are few times. Last week we
upgraded our development server. In a couple of weeks we will upgrade
our backup server. In late August we will finally do the production
server. About that time a new version of Oracle will be out. ;-)

Of course we plan on doing complete tape and hard drive backups before
moving to production.

We were going to do our backup server last; however, I can't get 10g
data to IMP into 8i. 8i to 10g is no problem.

Basically I just installed 10g and let it upgrade one instance from 8i
to 10g as part of the install. I then use DBUA to upgrade other
instances. Next I installed the 10g bug patch to take it from 10.2.0.1
to 10.2.0.2.

The biggest lesson learned: Anytime that you start up a 10g instance in
SQL Plus, exit and go back in before doing anything else. Not doing so
creates huge problems especially when installing the 10g bug patch. This
is a known issue. Check out Metalink Note 350972.1. It may just be a
Solaris SPARC problem; however, the note says that problem can occur on
any platform.

Jerry Whittle
COINS DBA
NCI Information Systems Inc.
jerome.whittle.[Email address protected]
618-622-4145
-----Original Message-----
From: BenBart
[mailto:oracledba-ezmlmshield-x46740619.[Email address protected]

Hi all,

I am looking at carrying out my Oracle8.1.74 to Oracle10gRelease2 as
follows and I just want some feedback from the experts here:

1. Install Oracle10gRelease2.
2. Clone the current 8.1.7.4 database with a different database name
but on the same server, for example, original database is TEST1,
cloned database is TEST1A
3. Shutdown the STANDBY database and stop log-shipping.
4. Run DBUA and upgrade TEST1A to Oracle10gRelease2 and "pray" that
everything goes well.
5. Shutdown TEST1 and TEST1A.
6. Stop all LISTENER.
7. Rename the Oracle10gRelease2 LISTENER config file and use the
LISTENER configuration used on 8.1.7.4 and modify the TEST1
LISTENER to point to TEST1A instead and start the Oracle10g
LISTENER and the "upgraded" TEST1A database/instance.
8. On the client end, they should be connecting to the database as if
they are still using 8.1.7.4 and still connecting to TEST1 but
which is actually TEST1A.
9. In case of problem, stop all database and Oracle10g LISTENER.
Re-start the Oracle8.1.7.4 LISTENER and the original TEST1
database/instance.
10. On the standby server, install Oracle10gRelease2 and re-create the
STANDBY database.


Can everyone put in their thoughts and opinions here please and tell me
whether am right so far? AS these 8.1.7.4 databases are not 24x7, I'll
be doing this on the weekend, so worst case scenario, I just restore my
8.1.7.4's most recent database backup.

Oracle LazyDBA home page