rman backup:restoring to new host [message #390219] |
Thu, 05 March 2009 08:52 ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
zaff
Messages: 50 Registered: July 2008
|
Member |
|
|
I have performed a database restore/recovery on a new host with a backupset (as part of a disaster recovery scenario). The restore runs through fine. However, when I perform the recovery I get the following message:
RMAN> recover database;
Starting recover at 04-MAR-2009 10:32:26
using channel ORA_SBT_TAPE_1
using channel ORA_DISK_1
starting media recovery
channel ORA_SBT_TAPE_1: starting archive log restore to default destination
channel ORA_SBT_TAPE_1: restoring archive log
archive log thread=1 sequence=235
channel ORA_SBT_TAPE_1: reading from backup piece 8uk92t02_1_1
channel ORA_SBT_TAPE_1: restored backup piece 1
piece handle=8uk92t02_1_1 tag=TAG20090304T132418
channel ORA_SBT_TAPE_1: restore complete, elapsed time: 00:00:35
archive log filename=/usr/mvf/data/dbase/arch/arch.log1_235_678649266.dbf thread=1 sequence=235
unable to find archive log
archive log thread=1 sequence=236
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 03/04/2009 10:33:18
RMAN-06054: media recovery requesting unknown log: thread 1 seq 236 lowscn 11290198
The last sequence in the archivelog backup is 235 and of course there is no sequence 236 on the server, as this is a new host. The fact that seq 235 was applied, means that the db is in a consistent state. So should I be concerned about this error?...is this normal? If not, how can I prevent it?
The db starts up fine and operates as expected.
Thanks,
Zaff
|
|
|
Re: rman backup:restoring to new host [message #390289 is a reply to message #390219] |
Thu, 05 March 2009 13:25 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
dzt52r
Messages: 19 Registered: July 2007 Location: PA
|
Junior Member |
|
|
I believe this is due to the fact that you don't have redo logs, which is expected because you are doing a DR test. The 6054 is OK provided the backup performed a switch log and all archived logs were backed up. If this is the case you will not be missing any data up to the point of the backup. Your database will open just fine with a 'resetlogs' .
|
|
|
|
Re: rman backup:restoring to new host [message #390433 is a reply to message #390219] |
Fri, 06 March 2009 05:39 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
zaff
Messages: 50 Registered: July 2008
|
Member |
|
|
Dzt52r - In a DR scenario, where my primary server is destroyed, I will not have access to redo logs. I can only retrieve what I have in the backups, up to the last archive log.
Alexzeng I have previously tried the command you suggested. However, I get an error along the lines of
Quote: | the backup needs to be older then the seq.
|
Even though archivelog seq 236 is backed up after the datafiles. I'm in the middle of another run and I will post the exact error.
Thanks guys for your help,
Zaff
|
|
|
Re: rman backup:restoring to new host [message #390561 is a reply to message #390433] |
Sat, 07 March 2009 08:49 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
alexzeng
Messages: 133 Registered: August 2005 Location: alexzeng.wordpress.com
|
Senior Member |
|
|
zaff wrote on Fri, 06 March 2009 05:39 |
Alexzeng I have previously tried the command you suggested. However, I get an error along the lines of
Quote: | the backup needs to be older then the seq.
|
Even though archivelog seq 236 is backed up after the datafiles. I'm in the middle of another run and I will post the exact error.
Thanks guys for your help,
Zaff
|
In this case, you can restore again using
run{
set until sequence 236;
restore database;
recover database;
}
Regards,
Alex
|
|
|
|