RE: Testing an rman backup

I have never understood why you have to connect to the source database and what happens when you do.

One issue I have had to battle with is change control. Even though you are building a copy database on a test/development node you still have to make a connection to the production system , which requires a CC.

I raised a metalink call with Oracle on this matter several years ago (probably v8) but I IIRC the answer was waffle and there was no good reason.

And why oh why is the source database called 'target'

John

-----Original Message-----

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Schauss, Peter Sent: 08 June 2007 19:31
To: oracle-l_at_freelists.org
Subject: Testing an rman backup

Environment: Oracle 10.2.0.2.0 HP-UX B 11.23

I am performing hot backups with rman in nocatalog mode. I would like to test restore procedures on the same node without destroying the existing database. Ideally, this should restore the database as a new instance with data files in different directories. I know that I can do this with the duplicate command, but that command requires rman to connect to the source database. Connecting to the source database, in my opinion, invalidates the test since I need assurance that I can recreate the database from scratch using only the rman backup files, the spfile, and the backup of the control file.

At this point I do not have the luxury of a clean server on which to run this test, but I do have sufficient disk space for a second copy of the instance.

Any suggestions?

Thanks,
Peter Schauss

--

http://www.freelists.org/webpage/oracle-l

--

http://www.freelists.org/webpage/oracle-l Received on Mon Jun 11 2007 - 03:05:56 CDT