Rman Database Clone Terminated Unsuccessful Ora-01667 (Doc ID 403214.1)

Symptoms

RMAN duplicate fails opening the clone database:

RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-10039: error encountered while polling for RPC completion on channel clone_default
RMAN-10006: error running SQL statement: select act from x$ksusex where sid=:1 and serial=:2
RMAN-10002: ORACLE error: ORA-03113: end-of-file on communication channel
RMAN-03002: failure of Duplicate Db command at 12/13/2006 13:03:25
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01092: ORACLE instance terminated.
Disconnection forced

.

Cause

Bug 4771560 OPEN RESETLOGS TERMINATES WITH ORA-1667

ORA-01667: cannot add any more tablespaces: limit of 'n' exceeded
           where n being maxdatafiles attribute in the control file.


From the bug:

This problem was discovered during RMAN DUPLICATE when MAXDATAFILES was set
to the actual number of datafiles.
.
The database code will expand the controlfile during file add and increase
MAXDATAFILES if DB_FILES parameter allows it, but the recovery/open process
won't, and will raise an ORA-1667 trying to add a tablespace, and no slots
are available.

.

Solution

Option a)
---------
Recreate the controlfile with a higher value for MAXDATAFILES  and
follow Note 360962.1 (Manual Completion of a Failed RMAN Duplicate)to complete the duplicate process.


Option b)
---------
If RMAN Duplicated failed at end, when the 'resetlogs' are already done,
we need to recreate control file with NORESETLOGS option pointing to redo log files location in auxiliary database.

Steps to resolve the issue:

1. In the control file recreation, use NORESETLOGS & mention auxiliary redo log files location.

    CREATE CONTROLFILE REUSE SET DATABASE 'XXX' NORESETLOGS ARCHIVELOG... etc

2. Recover & open auxiliary database.

    recover database;
    alter database open;

Thanks
Srini