Re: Database upgrade - backout strategy

enzoweb_at_hotmail.com (Andy) wrote in message news:<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?

You can try to use log miner to capture all changes made to database after upgrade. In case of going back, you can apply these changes to database recovered from backup. It's not very nice, but with sensible number of transactions, it can work.

P.S. Which doesn't mean that I recommend this. In fact, I think that scenario that you've described is not very clever to use.

--
_________________________________________

Dusan Bolek, Ing.
Oracle team leader

Note: pagesflames_at_usa.net has been cancelled due to changes (maybe we
can call it an overture to bankruptcy) on that server. I'm still using
this email to prevent SPAM. Maybe one day I will change it and have a
proper mail even for news, but right now I can be reached by this
email.