Re: Database Upgrade/Migration Dilemma

Rick,

Well, migrating across two major versions of Oracle to another platform without testing beforehand is just silly. Is there a reason this can't be tested? If the new server is available, my suggestion would be to test the database migration, make it available to the applications people for testing, and if the applications people choose not to test then that is not your responsibility.

   As far as the application being up during the migration, testing it first will give you an idea of how long the migration will take, for the window of vulnerability. Can the application be disabled from updating? While not recommended, one idea would be to compare data after the migration and manually look for data that got "stranded", then move that across manually. Not idea, but might be workable in your situation.

   Yes, I agree that you've been given some amateurish ideas. Now your task is to use your powers of persuasion. Also, a lot depends on the application and what is at stake for the organization. Just looking at your signature, perhaps this data isn't considered valuable on the order payroll data, for example.

Dennis Williams

--
http://www.freelists.org/webpage/oracle-l