Upgrading with a standby is simple. Upgrade the primary as usual.
When the standby complains it cannot read the log format of the new
version, shut it down and restart it on the new version's binaries
(new ORACLE_HOME).
If you don't have room for a new ORACLE_HOME, then stop the standby,
copy the upgraded ORACLE_HOME over from the primary (don't overwite
any of your configuration files - init<sid>.ora, listener.ora, etc.!),
and restart the standby.
If the two versions logs are compatible (this will be the case with
8.0.6.2 to 8.0.6.3), then just wait until the standby has consumed the
last log that was generated during the upgrade of the primary, then
shut it down and restart it on the new version's binaries. There is
no harm in running the standby on a different PATCH LEVEL (note - not
major point version) for a couple logs.
--
Jeremiah Wilton
http://www.speakeasy.net/~jwilton
On Fri, 17 Aug 2001, Hand, Michael T wrote:
> The rebuild process is very painful. The database is 560Gb and getting the
> backup tapes to the DR site and getting the standby instance built before
> there are "too many" redo logs (for the I/O channel) to apply can be
> problematic. However, the more I think about it, the more a rebuild seems
> to be the only choice. Any other options out there?
>
> -----Original Message-----
>
> Why not just rebuild the standby database from a backup of the upgraded
> production database?
>
> >From: "Hand, Michael T" <[EMAIL PROTECTED]>
> >
> >I will be performing an upgrade this weekend of out production database
> >from
> >8062 to 8063 (Alpha Tru64 40G machines). However we also have a standby
> >instance which will obviously also have to be upgraded (my first). Are
> >there any subtle things I have to look out for? One thing that comes to
> >mind is that rerunning catalog.sql (or other scripts) on production can't
> >be
> >done on the standby instance, those changes would have to be brought over
> >through the archived redo logs. Any others?
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Jeremiah Wilton
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
