RE: ZERO Database Downtime???

Yeah, that's what I meant. I would accept the invitation, but I don't have RAC running. :) It was just a quick thought off the top of my head.

From that blurb you wrote, I guess they took away the UPGRADE option in 10gR2. Is this related to their thought that RAC can be upgraded in a somewhat rolling state?

--Tom

On Wed, 29 Mar 2006, Jeremiah Wilton wrote:

> By this you must mean, first upgrade ORACLE_HOME binaries for each node, one
> at a time, then run the u10*.sql upgrade script on the database while
> everyone is connected and working.
>
> I would invite you to try this. Besides brief pauses in operation for the
> attrition and adding of each node, you can expect many invalid objects
> causing errors for users and many failed statements in the upgrade script
> due to ORA-54, leaving the upgrade in an unknown state. There is a reason
> the documentation says to run the upgrade script with the instances started
> in UPGRADE mode with no other users connected.
>
> Here's the blurb on UPGRADE mode from the docs:
>
> The UPGRADE keyword allows you to open a pre-10.2 database. It also
> restricts logons to AS SYSDBA sessions, disables system triggers, and
> performs additional operations that prepare the environment for the upgrade.
>
> --
> Jeremiah Wilton
> ORA-600 Consulting
> Recoveries - Consulting - Seminars
> http://www.ora-600.net
>
> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org]
> On Behalf Of Tom Fox
>
> 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.
>
>

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