RE: Use the same database release on the primary and standby databases

From: Mark W. Farnham <mwf_at_rsiz.com>
Date: Mon, 1 Feb 2010 12:55:28 -0500
Message-ID: <77C1855AC0234C9E866166DDFA1A9C21_at_rsiz.com>

I understand why you would need to clone oracle home, but I don't understand why you would need to reinstantiate the standby.

-----Original Message-----
From: Roger Xu [mailto:wellmetus_at_gmail.com] Sent: Monday, February 01, 2010 12:52 PM To: Mark W. Farnham
Cc: April Sims; vishal_at_vishalgupta.com; oracle-l_at_freelists.org Subject: Re: Use the same database release on the primary and standby databases

The reason we are relectant to upgrade at the standby site is that it is holding another standby instance from another primpary database. (If it runs into problem, we will have to clone the oracle_home, upgrade and recreate the standby.) Thanks, Roger

On Mon, Feb 1, 2010 at 11:46 AM, Mark W. Farnham <mwf_at_rsiz.com> wrote:
> For any point release this is *likely* to work in a given test, but there
is
> a PROBLEM.
>
> The problem is that unless Oracle declared that a given point release had
no
> changes to existing output possibilities to redo logs in support of any
> fixed or new features, you would be faced with the possibility of records
in
> the new redo logs that would not be understood correctly in the older
> release. So even if you tested a substantial set you would have no
> reasonable expectation of reliability.
>
> Regards,
>
> mwf
>

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

Received on Mon Feb 01 2010 - 11:55:28 CST