Re: disaster recover from RMAN backup

Ted,

Thanks for your reply! I am pretty sure I used the right controlfile.
I tried again by moving the manual controlfile and spfile rman command (I
was not using controlfile autobackup) to the very end of the backup script
and re-did the backup. Then I deleted everything and re-did all the steps
that I listed in my previous email, got the same error.

-Li


On 6/13/07, Ted Coyle <oracle-l@xxxxxxxxxxxx> wrote:


 Are you sure you recovered the right contolfile?



Test using existing controlfiles and see if you get the error.



Ted


 ------------------------------

*From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto:
oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *Richard J. Goulet
*Sent:* Wednesday, June 13, 2007 3:55 PM
*To:* Li Li
*Cc:* oracle-l
*Subject:* RE: disaster recover from RMAN backup



Phooey.  That might have explained it.



______________________________________________________________
Dick Goulet / *Capgemini*
North America P&C / East Business Unit
Senior Oracle DBA / Hosting
Office: 508.573.1978 / Mobile: 508.742.5795 / www.capgemini.com
Fax: 508.229.2019 /  Email: *richard.goulet@xxxxxxxxxxxxx*
45 Bartlett St. / Marlborough, MA 01752

*Together: the Collaborative Business Experience *
______________________________________________________________




 ------------------------------

*From:* Li Li [mailto:litanli@xxxxxxxxx]
*Sent:* Wednesday, June 13, 2007 3:48 PM
*To:* Richard J. Goulet
*Cc:* oracle-l
*Subject:* Re: disaster recover from RMAN backup

no :(

On 6/13/07, *Richard J. Goulet* <richard.goulet@xxxxxxxxxxxxx> wrote:

Was this datafile/tablespace transported from another database??



______________________________________________________________
Dick Goulet / *Capgemini*
North America P&C / East Business Unit
Senior Oracle DBA / Hosting
Office: 508.573.1978 / Mobile: 508.742.5795 / www.capgemini.com
Fax: 508.229.2019 /  Email: *richard.goulet@xxxxxxxxxxxxx*
45 Bartlett St. / Marlborough, MA 01752

*Together: the Collaborative Business Experience *
______________________________________________________________




 ------------------------------

*From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
*On Behalf Of *Li Li
*Sent:* Wednesday, June 13, 2007 3:11 PM
*To:* oracle-l
*Subject:* disaster recover from RMAN backup



Hi, List,



I am testing a disaster recovery senario. RMAN backup was done with no
catalog. Below are what I did:



1. startup nomount

2. restore spfile from xxx

3. shutdown

4. startup (this time it picks up the restored spfile)

5. restore controlfile from xxx

6. alter database mount

7. restore database check readonly (I have 2 read only tablespaces)

8. recover database until logseq 5 (log seq 4 was the last archivelog
backed up by rman)



everything worked fine until step 8, I got an error on step 8 until
follows:



ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error
below

ORA-01122: database file 9 failed verification check

ORA-01110: data file 9: 'H:\xxx\xxx\xxx.dbf'

ORA-01206: file is not part of this database - wrong database id



file 9 is one of the READ ONLY tablespaces.

Any comment on what's wrong in here?



TIA,

-Li





This message contains information that may be privileged or confidential
and is the property of the Capgemini Group. It is intended only for the
person to whom it is addressed. If you are not the intended recipient, you
are not authorized to read, print, retain, copy, disseminate, distribute, or
use this message or any part thereof. If you receive this message in error,
please notify the sender immediately and delete all copies of this message.


  This message contains information that may be privileged or confidential
and is the property of the Capgemini Group. It is intended only for the
person to whom it is addressed. If you are not the intended recipient, you
are not authorized to read, print, retain, copy, disseminate, distribute, or
use this message or any part thereof. If you receive this message in error,
please notify the sender immediately and delete all copies of this message.

Other related posts: