Ruth,
thanks, I am back. I took the redundancy policy to 4 now and deleted
today's backupset and try to recover from the yesterday backupset which
is a valid status in the rman report. I still got error. Rman still
looking for today's backupset sequence. If I do the crosscheck and
delete the
Sorry, I tried set until time, it works. Now I think we can move rman to
production since we tested all kinds of restore.
Thanks and have nice day!
Joan
Joan Hsieh wrote:
Ruth,
thanks, I am back. I took the redundancy policy to 4 now and deleted
today's backupset and try to recover from
Joan - Glad to hear your success. In the meanwhile I replied to your earlier
message.
Just to clarify, when you used a time-based recovery, setting a time earlier
than the most recent backup, RMAN ignored the most recent backup and
restored from an earlier backup? Wouldn't that have the
Joan - I have not used the redundancy policy, but my understanding is this
just involves how many backup copies to retain. It does not relate to
recovery as I read the manual.
Do you have Robert Freeman's book Oracle9i RMAN Backup Recovery?
Are you attempting an incomplete recovery or a
If you don't set the redundancey policy to a recovery window of N days, than
the record of the backup will be kept indefinitely. You should be able to
restore the backups from tape and restore from a previous backup. You may
need to do a set until time if there was corruption or another problem.
Tanel,
Yes, rman keep asking the newer backupset which is start *450.rman. I don't
know the command change backuupset unavailable command. I will give it a try.
I know there is very rare situration that we need restore from an older
backupset, but need to prepare it in case we do need it. I
I have never attempted what you are doing, so I must confess some ignorance.
But, looking at your error message, it appears that rman knows what file it
needs and is unable to get it. One must assume there is no file named
/rmanbackup/ADVDBA_F_20031231:15:03:39_1.450.rman
available on the hard
Hi!
As Stephen pointed out, rman searches for a file named
/rmanbackup/ADVDBA_F_20031231:15:03:39_1.450.rman, but can't find it. Is
this file a newer backupset which rman is automatically trying to use?
If you want to skip this file, you could use change backupset unavailable
command for
I was actually talking from database recovery point of view (that you can do
point in time recovery prior to current controlfile time if you use using
backup controlfile option when recovering.
For restoring a de-registered backupset, I see two options (there might be
more, more convenient ones):
Thanks Tanel. I will test it out.
Happy new year!
Joan
Tanel Poder wrote:
I was actually talking from database recovery point of view (that you can do
point in time recovery prior to current controlfile time if you use using
backup controlfile option when recovering.
For restoring a
After I did some testing, it is impossble to restore and recover a
deleted obsolete backupset. So I took off the delete obsolete command.
Retention policy to redundancy still keep it to 1. I did couple backups
and run list backup of database and report obsolete command.
Although report obsolet
I think you can do CONFIGURE CONTROLFILE AUTOBACKUP ON,
which enables RMAN to automatically backup controlfile to
a default location. Then you can restore the controlfile
before you restore other database files.
-Original Message-
Sent: Tuesday, December 30, 2003 3:34 PM
To: Multiple
Joan - Which Oracle version?
Dennis Williams
DBA
Lifetouch, Inc.
[EMAIL PROTECTED]
-Original Message-
Sent: Tuesday, December 30, 2003 3:34 PM
To: Multiple recipients of list ORACLE-L
Hi Listers,
I have a question about rman restore. Right now, I configured RETENTION
POLICY TO
Dennis,
9.2.0.4
Joan
Quoting DENNIS WILLIAMS [EMAIL PROTECTED]:
Joan - Which Oracle version?
Dennis Williams
DBA
Lifetouch, Inc.
[EMAIL PROTECTED]
-Original Message-
Sent: Tuesday, December 30, 2003 3:34 PM
To: Multiple recipients of list ORACLE-L
Hi Listers,
I
Well Roger, Suppose I still have the current control file and want to use days
old full backupset (obsolete already) to restore and recover the database to
the point of time. How it related to recover the autobackup controlfile? I did
configure controlfile autobackup on though.
Thanks,
Joan
You can do point in time recovery using current controlfile as well. You
just say recover database until cancal using backup controlfile then, that
way Oracle ignores SCN information inside controlfile and trusts only
datafile headers.
You have to open resetlogs after that. One issue I see with
Note that when you configure controlfile autobackup on, then a backup
controlfile will be saved to default location (dbs or database dir under
$ORACLE_HOME) after most physical database structure changes such is adding
a datafile, taking tablespace offline/online etc. This is the behaviour of
Tanel,
Do you mean if I am using current controlfile to recover database, It doesn't
matter the backupset is obsolete or not in the rman catalog repository
database, is that sounds right? So, I just have to restore the old backupset
from tape to disk and issue recover database command? At
Yes, you can lo+ok at note 73974.1on Metalink to find out how to put the
datafiles in different places in the copy database. This note tells you
exactly how to do it, but when you 'switch' that datafiles you have to
repeat the set newname... command and then switch each individual file.
HTH,
19 matches
Mail list logo
