RE: ZERO Database Downtime???

  • From: "Mercadante, Thomas F (LABOR)" <Thomas.Mercadante@xxxxxxxxxxxxxxxxx>
  • To: "Tom Fox" <tom@xxxxxxxxx>
  • Date: Wed, 29 Mar 2006 13:30:13 -0500

Heck I don't know.

Because the migration documentation says to do it the other way?
Upgrade the software and then upgrade the data dictionary?

I'm assuming that it might be a bad idea to have upgraded OS software
without the matching upgraded data dictionary components.

Maybe that's a bad assumption - buts that's always the way Oracle has
said to do it.

-----Original Message-----
From: Tom Fox [mailto:tom@xxxxxxxxx] 
Sent: Wednesday, March 29, 2006 1:10 PM
To: Mercadante, Thomas F (LABOR)
Cc: Jared Still; davidsharples@xxxxxxxxx; MFontana@xxxxxxxxx;
Subject: RE: ZERO Database Downtime???

Why wouldn't you upgrade all instances to the latest version first, then

apply the database upgrade after all instances are up?

This would allow for no database downtime.


On Wed, 29 Mar 2006, Mercadante, Thomas F (LABOR) wrote:

> But see, all of this is *not* RAC!  And the RAC sales pitch *always*
> sells rolling upgrades and "your database is never down".
> Lies and obfuscations!

Other related posts: