RMAN DUPLICATE ERRORS WITH RMAN-5565 - SPFILE NO FOUND (Doc ID 874202.1)

---

APPLIES TO: Oracle Database - Enterprise Edition - Version 11.2.0.2 to 11.2.0.2 [Release 11.2] Oracle Database Cloud Schema Service - Version N/A and later Oracle Database Exadata Express Cloud Service - Version N/A and later Oracle Database Exadata Cloud Machine - Version N/A and later Oracle Database Cloud Exadata Service - Version N/A and later Information in this document applies to any platform. SYMPTOMS An attempt to perform a duplicate using 11GR2 feature of not connecting to a catalog or target can result in the following error: DUPLICATE DATABASE TO dupdb UNTIL TIME "TO_DATE('06/23/2009 14:45:00', 'MM/DD/YYYY HH24:MI:SS')" SPFILE BACKUP LOCATION '/recovery_area' NOFILENAMECHECK; Starting Duplicate Db at 2009/06/23 15:52:31 RMAN-571: =========================================================== RMAN-569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-571: =========================================================== RMAN-3002: failure of Duplicate Db command at 06/23/2009 15:52:31 RMAN-5565: SPFILE backup created before TO_DATE('06/23/2009 14:45:00', 'MM/DD/YYYY HH24:MI:SS') not found in /recovery_area OR RMAN-03002: failure of Duplicate Db command RMAN-05579: CONTROLFILE backup not found in '/recovery_area' CAUSE The problem is caused due to Unpublished BUG 8626638. The backup location is directory off the root path. BACKUP LOCATION '/recovery_area' It is only specific to directory from the root mount point. SOLUTION There are two potential workarounds: Append a backslash at the end of the path ( i.e BACKUP LOCATION '/recovery_area/') Select a location to store the files which has not be created directly off the root mount point.