RE: rman nocatalog - point in time recovery

  • From: "Ruth Gramolini" <rgramolini@xxxxxxxxxxxxxxx>
  • To: <oracle-l@xxxxxxxxxxxxx>
  • Date: Wed, 14 Jul 2004 08:40:57 -0400

Sometimes I find it is just expedient to use sqlplus to open the database.
Sometimes, there is no other way.  Rman is still a work in progress and it
has been seriously improved since the 8.0.5... days but when you are doing
incomplete recovery and it seems to want a redo log instead of an archived
log, then I have found,  sqlplus recover the way you did it is the easiest
way.  Even Oracle support has told me this.

HTH,
Ruth

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Schauss, Peter
Sent: Tuesday, July 13, 2004 4:44 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: rman nocatalog - point in time recovery


This may not be the cleanest solution, but it worked:

rman
run {
set until logseq=1235 thread =1;
allocate channel ch1 type disk;
allocate channel ch2 type disk;
allocate channel ch3 type disk;
restore database;
}
exit;

sqlplus internal
sqlplus> recover database until cancel using backup controlfile;
sqlplus> alter database open resetlogs;
sqlplus> exit;

Is there a better way to do this?

thanks,
Peter Schauss

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Schauss, Peter
Sent: Tuesday, July 13, 2004 4:12 PM
To: Oracle-L (E-mail)
Subject: rman nocatalog - point in time recovery


Enviroment: Oracle 8.1.7.4 / AIX 5.2

Scenario:

- I have an rman backup (nocatalog) and a separate control file backup
done at 11:00 pm.

- The database is in archivelog mode.

- At 11:00 am the next morning I have a failure which causes
loss of the entire database.

- Archivelogs through 10:45 are intact.  The last archive log is sequence
1234.

- I have the backup files created from the 11:00 pm rman backup in the
directory
to which they were backed up.

- I want to restore the database to the state it was in at 10:45 am by
applying
the redo logs through number 1234.

I restore my control files by copying them to the appropriate directories on
the disk (e.g. /ora1/oradata/sid/control01.ctl ...  /ora2/...  /ora3/...).

I run the following commands in rman

run {
set until logseq=1234 thread=1;
allocate channel ch1 type disk;
allocate channel ch2 type disk;
allocate channel ch3 type disk;
restore database;
recover database;
alter database open resetlogs;
}

Oracle says:

RMAN-03002: failure during compilation of command
RMAN-03013: command type: set
RMAN-06003: ORACLE error from target database: RMAN-20206: log sequence not
found in the recovery catalog

What am I missing here?

Thanks,
Peter Schauss
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to:  oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to:  oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to:  oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Other related posts: