One option is to
a. Restore the 4am controlfile to the test server
b. Restore the database
c. Recover the databaes
d. Discover that the RECOVER halts at the archivelogs of 9am when the new datafile was added
e. Isssue, from the SQLPLUS AS SYSDBA command line : ALTER DATABASE CREATE DATAFILE 9 AS '..path_to_the_datafile_to_create'
(e.g. ALTER DATABASE CREATE DATAFILE 9 AS '/u01/app/mytestdb/oradata/datafile9.dbf'; )
f. Continue Recovery
See Oracle Support RMAN-06023 Recover from Missing Datafile that is Never Backed Up [ID 130724.1]
I don't know of a note that shows how DUPLICATE handles this.
Hemant K Chitale
yes it fails with error
RMAN-03002: failure of Duplicate Db command at 06/29/2013 11:23:52
RMAN-03015: error occurred in stored script Memory Script
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20201: datafile not found in the recovery catalog
RMAN-06010: error while looking up datafile: 9
because datafile backup does not exist in catalog as of 4pm, this data file was first back'd up the following day ...
is it possible to edit catalog manually so it thinks data file was back'd up the day before ?