RE: Restore old backup to new database name
- From: <Joel.Patterson@xxxxxxxxxxx>
- To: <Joel.Patterson@xxxxxxxxxxx>, <Brandon.Allen@xxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 10 Mar 2010 14:34:45 -0500
Update:
This worked. Next time we will just point the dev server at the
production backup location. Thanks for any help clearing up the fine
points.
Was easier than restore/rename although I appreciate the fine points
given here as well. Thanks also to Robert Freeman for addressing
exactly the rename issue.
Joel Patterson
Database Administrator
904 727-2546
-----Original Message-----
From: Patterson, Joel
Sent: Tuesday, March 09, 2010 3:45 PM
To: 'Allen, Brandon'; oracle-l@xxxxxxxxxxxxx
Subject: RE: Restore old backup to new database name
Ok. This is what my present plan is.
I am FTPing the 2/26/10 backups from test server to production server so
they will reside in both places.
Then I will catalog the production server with the start with clause.
Then I will re-attempt the duplication using the until clause.
The ftp will take a few hours. I'll let you know if this was the
issue.
I appreciate all the input.
Joel Patterson
Database Administrator
904 727-2546
-----Original Message-----
From: Allen, Brandon [mailto:Brandon.Allen@xxxxxxxxxxx]
Sent: Tuesday, March 09, 2010 3:36 PM
To: Patterson, Joel; oracle-l@xxxxxxxxxxxxx
Subject: RE: Restore old backup to new database name
Maybe this is what you're looking for (from
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmdupdb.
htm#i1008888):
"So long as RMAN is able to connect to the primary and auxiliary
instances, the RMAN client can run on any host. All backups and archived
redo logs used for creating and recovering the duplicate database,
however, must be accessible by the server session on the duplicate host.
If the duplicate host is not the same as the target host, then you must
make backups on disk on the target host available to the duplicate host
with the same full path name as in the primary database.
When using disk backups, you can accomplish this goal in any of the
following ways:
*Manually transfer the backups from the primary host to the remote host
to an identical path. For example, if the backups are in /dsk1/bkp on
the target host, then transfer them to /dsk1/bkp on the duplicate host.
*Manually transfer the backups from the primary host to the duplicate
host at a new location. For example, if the backups are in /dsk1/bkp on
the target host, then you might transfer them to /dsk2/dup on the
duplicate host. The new path-in this example, /dsk2/dup-must be
accessible from both the target and duplicate hosts. Run the CATALOG
command to add these copies to the RMAN repository at the duplicate
host.
*Use NFS or shared disks and make sure that the same path is accessible
in the remote host. For example, the NFS mount point for both hosts
could be /home/file_server."
Privileged/Confidential Information may be contained in this message or
attachments hereto. Please advise immediately if you or your employer do
not consent to Internet email for messages of this kind. Opinions,
conclusions and other information in this message that do not relate to
the official business of this company shall be understood as neither
given nor endorsed by it.
--
//www.freelists.org/webpage/oracle-l
Other related posts:
