Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Different Oracle patchlevels between primary and (physical) standby

Different Oracle patchlevels between primary and (physical) standby

From: Andre van Winssen <awinssen_at_xs4all.nl>
Date: Thu, 25 Aug 2005 20:52:52 +0200
Message-ID: <002d01c5a9a6$36cb8520$0301a8c0@KAST01>


Hi,  

The production db I am looking after has to move to a new server. Because downtime is not appreciated (!) my first idea was to build a physical standby of the current production db on the new server and then do a switchover. This has the benefit that most of the work can be done in the background, only at failover time will production be affected for a short period.  

As I would also like to patch the current db to a higher level (from 9.2.0.5 to 9.2.0.6 + interimpatch or 9.2.0.7 if available) I want to try following:

on the standby server I will install the patched Oracle version, and after the failover has been done I will follow the normal db upgrade procedure against the new primary db, i.e. startup migrate and running catpatch.sql  

So this means that there will be a discrepency in Oracle version between primary and standby while the redo logs are shipped and applied.  

Of course everything will be tested properly first but still am wondering if anyone tried this before  

Regards,

Andre van Winssen  

--
http://www.freelists.org/webpage/oracle-l
Received on Thu Aug 25 2005 - 13:55:35 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US