At least I would stronly encourage not to have the standby database receiving and/or applying logs whilst the primary is upgraded. Oracle docs suggest to do this. However, what if the upgrade fails? Then you have two databases upgraded halfway. I never understood why Oracle wants this approach in a HA environment. If you stop the standby during the upgrade (or have it open read-only, as Jason suggested) you can easily activate the standby when the upgrade of the primary fails for whatever reason. Best regards, Carel-Jan Engel === If you think education is expensive, try ignorance. (Derek Bok) === On Wed, 2008-05-28 at 10:46 +0100, S. Anthony Sequeira wrote: > On Wed, 2008-05-28 at 10:58 +0200, Carel-Jan Engel wrote: > > Are you trying to ask whether a rolling upgrade is possible? > > > > If so, the answer is NO. > > Despite attempts from Oracle to redefine the meaning of 'rolling > > upgrade', update a system without any downtime for the application is > > not possible. > > Hi Carel-Jan, > > No I'm asking whether it's possible to apply the patch with at least one > node servicing the database, as I did for the pre-production database, > with a short downtime for the recompile views post-installation step. > Unfortunately this doesn't seem possible with a standby database > involved. > > Regards. > -- > S. Anthony Sequeira > ++ > Why be a man when you can be a success? > -- Bertolt Brecht > ++ > > -- > //www.freelists.org/webpage/oracle-l > >