Re: Upgrading a Windows 2000 server box with Oracle 8i to Windows 2003 Server with 9i

"Nick Palmer" <nick_at_kcicorp.com> wrote in message news:<vmeee2lpvhvm3a_at_corp.supernews.com>...
> Well, the databases are not too large, and are not very complex. In general
> in these databases, there is only one userid of any importance, and so only
> one schema that I'm worried about backing up. So I'm thinking my best bet
> is to do full exports of all the databases and then use these to import into
> the newly created databases under 9i.
>
> Now that leads to a another question. Should I upgrade to the 8i database
> to 9i before upgrading to 2003 server, or shutdown Oracle, upgrade to 2003
> server and then upgrade to 9i ? Ideally maybe I should do full database
> exports and then remove Oracle 8i from this box, upgrade it to 2003 and then
> install 9i and do the imports. Only problem there is I'm not sure how I can
> completely remove 8i and all the services it install.
>
> Nick.
>

now you're talking - except for the ideally part. export + cold backup (multiple copies, create a log file and read it carefully).

THERE ARE EXPORT BUGS OUT THERE ON 8.1.7.x. THEY MAY NOT APPEAR UNTIL YOU ATTEMPT TO IMPORT. I'd advise to unload the DDL to recreate all objects in the app owner schema.
You might want to move segments to different tablespaces, etc.

There exists several docs on metalink as to how to completely remove an 8.1.7 installation prior to re-installing oracle software.

I would agree that cold/hot/rman/arch + exp of the 8.1.7.x databases, removal of oracle software, remove c:\program files\oracle, remove d:\oracle, remove HKLM\ORACLE (backup registry first, of course) - REBOOT - is the way to go.

heck - why not just nuke the box entirely and install W2K3 from scratch on a clean system, and install 9.2.0.1.0 + 2.2.0.18.0 + 9.2.0.4.0 prior to creating new databases?

it certainly reduces the implcations of migrations/upgrades, rather than clean installs.

you'll want to unload the existing user accounts (plus hashed passwords), sys privs, roles, object privs into scripts so that you can move these (seamlessly).

yes, you could import the full dump file (destroy=N), but I've always been aprehensive of importing the old system schema into a new database. seems like bringing along too much cruft.

this really is worth a trial run on another box, don't you think?

also - the default charset for 9.2 differs from 8.1.7. be aware of that when importing the dump file produced with an 8.1.7 client.

Paul Received on Wed Sep 17 2003 - 01:10:21 CDT