Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Help with Restore and Recovery of 11g DB

674757Feb 17 2010 — edited Feb 19 2010
Hello All,

Can you fine folks help me shed some light on RMAN when it comes to DB recovery? Here's my scenario, I am practicing my RMAN skills on a test database and performed the following tasks:

(1) Installed Redhat 5 - 64 bit and Oracle (11.1.0.7) 64 bit on test.

(2) I took Prod’s full RMAN backup from 3am Feb 17th (same day), and copied it over to test. I also copied the backup control files (autobackup) to my test host /ORACLE_HOME/dbs folder (Same folders and mountpoint as production).

(3) I copied the archivelogs generated from 3am to 10am to the test host. Test and Production are identical in file and folder layout, and not using ASM. So no change to the control file will have to be made since the archive logs and RMAN backup are in the same mount point or folders; in test as they are in Production.

(4) On the test host, and at the RMAN prompt, I set the DB ID (same as production).
(5) RMAN> Startup nomount.
(6) RMAN> restore control file from autobackup (restored fine to the three mount-points)
(7) RMAN> alter system mount (ok) Database mounted.
(8) RMAN> restore database (worked fine). All DB files where copied from the RMAN backup to the proper folders on test as they are in production. So far so good.

My next step is obviously to recover my database (test and prod are both in ARCHIVELOG MODE). I copied prod’s Archive logs to test, in the same folder as production, so the inti.ora file will find them and the control files won’t have any issues either. I execute a recover database command from RMAN and it seems to have applied all the logs I copied over. It did look for the next log seq# which was 4301. I had copied 4290 – 4300 to the archive log dest area. It seemed to apply those but was looking or looked like if failed because it did not find 4301. Now, it seems that the only way to open this database is with the ‘RESETLOGS’ option. My question is why? What if I want to copy over log seq# 4301 – 4310 later that day, I will not be able to apply them because my archivelog seq numbers have now been reset. Why does OPEN NORESTLOGS not work? Is it because I don’t have test configured as a true “standby” database and just a quick clone job?

Am I missing something?

Thanks,
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Mar 19 2010
Added on Feb 17 2010
7 comments
2,085 views