RMAN DUPLICATE DATABASE with SET NEWNAME failed: RMAN-05501 RMAN-05517
(Doc ID 387093.1)
Last updated on SEPTEMBER 30, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.2 to 188.8.131.52 [Release 10.2 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 7-Dec-2015***
For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:
Executing RMAN DUPicate , on same host as Target Database using
SET NEWNAME to redirect datafiles to new location.
SET NEWNAME has been specified for all datafiles for example like
following RMAN script:
This fails with Errors:
Starting DUPicate Db at 11-AUG-2006:14:20:47
Datafile 8 skipped by request
released channel: a1
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-03002: failure of DUPicate Db command at 08/11/2006 14:20:52
RMAN-05501: aborting DUPication of target database
RMAN-05517: temporary file D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\TEMP01.DBF conflicts with file used by target database
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document