| |
Upgrading an NT4 server running oracle db to
windows 2k AS |
|
| |
If you are running an NT 4.0
Server and an oracle 8i (or older) database system on a single
server you soon might be confronted with the question of how to upgrade to
Win2k.
Let us show you the few but necessary steps to succeed:
First you must check all the server for necessary junk and
see to it that your partition containing the win NT directory must have a fine
bit of free space: app. 600 - 1K MB
Don't run the risk of getting stuck with not enough space as you might have some extras that
need to be upgraded.
Then check the place where you put all those nice
adds. NT and IIS Resource kits and Option packs like to use
plenty of space. Well what to do if they are on c ? Hey, get them off
there and only keep if installed IIS4.0 on the other big drive.
May I presume that you don't keep all that precious data on c ? lots of
GB's do not belong on C ! Programs that do not belong to NT are not
welcome on c but on D or E !
Now get that NT Resource kit
of the system and any junk that will be replaced by the win2k kits.
If you have set up an application besides the db on your server you
must ask the manufacturer for possible incompatibilities when migrating
to win2k. Then shut down the program.
Are you running an oracle
8.05 (or older) enterprise database you must then shut down all oracle
services before upgrading to 8i v1.6 (1.5 is not win2k certified!). If
you forget to shut down the listener you will have a nasty surprise
after uninstalling the old version as you'll have to reinstall the
listener 8.1.6 before being able to test the db after this first
migration.
You think that's plenty to start with?
Have you shut down IIS 4.0 with its services "Web, FTP, SMTP, NNTP" ?
Oh, before I forget it: is your backup software win2k compatible? Bet,
you forgot to ask.
Let me explain at first about the whole idea behind
the steps needed to succeed in the migration to win 2k.
If your Server
is migrated to win2k in productive state you can have a total
failure. Therefore your NT server must be ready (including min. SP5)
before attempting to start the win2k setup.
Then after being sure to
have a working backup you will at your own risk (!) start the setup. Check that
you have the right language CD!
So lets start cooking:
Choose migrate/Upgrade to Windows 2k (Advanced) Server.
After
successfully installing Win2k and booting the first time as a win2k server, you
will be asked several important questions. Please check with your win2k
migration task advisor before feeding wrong data into the system.
We then need to follow these tasks:
Start the oracle db (incl.
listener) to see whether the services are able to run. Then start the iis4 and and your application (if there is one).
Can the
db be accessed via odbc? if yes, you have migrated successfully.
Now don't forget to update iis 4.0 to v.5 and install the win2k option/resource kits.
In our Lab we tested it with a real
life system which was replaced by a stronger server. After Migration everything
worked without a cough or sniff.
Never forget:
You are doing this at your own risk!
If it fails don't blame us!
|
|
| |
By C.Bartsch - Contact via
|
|
Consulting Articles 
