Re: Unsupported Recovery Technique......?

From: bdbafh <bdbafh_at_gmail.com>
Date: Thu, 20 Mar 2008 08:16:18 -0700 (PDT)
Message-ID: <d38a5c79-893e-44ca-af0c-6b18a6bb4283@x30g2000hsd.googlegroups.com>


On Mar 19, 11:01 pm, mc..._at_hotmail.com wrote:
> 10g Release 2
>
> I have cloned a 10.2.0.1 database onto a 10.2.0.3 home by using a cold
> backup and recreating the controlfile. During the 'alter database
> open resetlogs' the instance crashes because of the version mistmatch:
>
> ORA-00704: bootstrap process failure
> ORA-39700: database must be opened with UPGRADE option
> Thu Mar 20 02:46:27 2008
>
> I then run:
>
> startup mount
> alter database open upgrade
>
> and then upgrade the database to 10.2.0.3 with
>
> @$ORACLE_HOME/rdbms/admin/catupgrd.sql
>
> Everything appears OK.
>
> My question is....... is this a supported procedure..? Is there a
> danger that the database is corrupted in some way after performing
> this restore/upgrade step together....?
>
> Incidentally, I also used this technique to restore an RMAN backup
> from 10.2.0.1 to 10.2.0.3 and used exactly the same technique (alter
> database open upgrade). This also seemed to work fine but is it a
> supported/stable approach..?
>
> Thanks

Interesting.
What is the value for the parameter "compatible" in the spfile/ init.ora when you're recovering the cloned database backup set?

(guessing)
Perhaps setting that to 10.2.0.1 during the "open resetlogs" phase might prevent the database needing to be opened with the UPGRADE option.

After the logs have been reset, then startup upgrade and execute the upgrade script ...

hth.

-bdbafh Received on Thu Mar 20 2008 - 10:16:18 CDT

Original text of this message