Re: Database upgrade - backout strategy

As long as you keep the parameter compatible = 8.0.6 Oracle has downgrade scripts to go back.
If compatable has been set higher, you can still go back but you must remove the incompatabilities first so it is more difficult. It is described in the Migration Guide, Chapter 13. I suggest you read the platform specific release notes and installation guide and check on Metalink too.
The question is: how reliable is it? Since I think not many people need to do it, I have some doubts (although I AM an Oracle fan). I would certainly not do it without testing. But you have tested the upgrade, didn't you, so why would you need a downgrade for your production environment?

Andy <enzoweb_at_hotmail.com> schreef in berichtnieuws 8d4033cd.0209092134.b86550c_at_posting.google.com...
| We are planning to upgrade from V806 to V817 and I'd like to know
| opinions on backout strategies. The scenario is that the database has
| been upgraded and has been in use for about 4 -5 days (it's not too
| transaction heavy) when errors are detected and it is decided to back
| out to V806 without losing the 4 -5 days of work. The database is
| about 150Gb in size.
|
| The only thing I can think of is to export from V817 using the V806
| executable and importing into V806. The only issue here is time (15-20
| hours?) since there is no referential integrity on the database (it's
| a legacy application).
|
| Can anyone think of alternatives, preferably faster?
Received on Tue Sep 10 2002 - 12:27:16 CDT