Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Mailing Lists -> Oracle-L -> Re: rman duplicate fails to identify file
Tricia,
One sure thing that will cause duplication to fail (especially when =
going
off tape media manager layer, which is not the case here) is difference =
in file ownership.
For instance, you backed up source database as user ORAPRD. On the =
auxiliary
(duplicate) node you are restoring these files as user ORADEV.
Two other things to consider are: difference in Oracle versions and OS=20 versions between source and auxiliary nodes.
Cheers,
Slava Zayarny
Oracle DBA
From: Tricia McKellar <tricia_mckellar_at_ncsu.edu> Subject: rman duplicate fails to identify file Date: Wed, 6 Apr 2005 17:38:44 -0400
Hello,
I'm having trouble duplicating a db to another host with a different=20
path structure (oracle 9.2.0.6 on solaris). I'm able to connect to=20
both db's and the file rename parameters in the initDUP.ora seem to be=20
working--rman seems to know to rename
/prod/oradata/vsid/ifs_lobs01.dbf
TO
/dup/oradata/vsid5/ifs_lobs01.dbf
but rman seems to get stuck on the backup pieces. The backup files do=20 exist. I've been rman'ing to disk only (not tape). I've tried copying=20 the backup pieces to the dup host, but it still gets stuck. Ideas?
###
...
restoring datafile 00034 to /dup/oradata/vsid5/ifs_lobs13.dbf
restoring datafile 00035 to /dup/oradata/vsid5/ifs_lobs14.dbf
RMAN-00571: ==3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
RMAN-00571: ==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
Thanks,
Tricia
-- http://www.freelists.org/webpage/oracle-lReceived on Thu Apr 07 2005 - 09:17:34 CDT