01-07-2012
383,
29
Join Date: Mar 2008
Last Activity: 27 March 2017, 3:48 PM EDT
Location: Surrounded...
Posts: 383
Thanks Given: 1
Thanked 29 Times in 28 Posts
It's never simple if you're leaving it to the Vendor's documentation. Same goes for the app using the database, if you're using one from off the shelf or an outside Vendor. Many Vendors will publish their own "certified" listings for this sort of effort. (There's always at least three tiers to a DB environment; platform/OS, DB and app.)
Oracle publishes their end-point release for each version, along with platform requirements such as OS version requirements, etc. Assuming you're already set with a copy of Oracle for your new target OS, your hardest task would be to migrate the data. You'd want to instantiate the DB (ie, schema, etc), and then you could probably offload the data and reload it via utilities such as SQL*Loader. If not, and you're into risk, you could hope that your older version of Oracle will work in the new environment and maybe squeak by on a tape restore.
Same would go for pretty much every other DB product out there...unless there's consultants involved already. Then it's a matter of revenue stream protection.
Good luck.