如何恢复数据库在没有控制文件的情况下？

ALLSTARS_ORACLE

有这样一个场景如下：
只有一个RMAN 备份，这个备份中只包含数据文件，没有控制文件。
我把数据文件抽取出来后，这时候重建控制文件打开数据库报错：

SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/u01/oradata/epdbstby/system01.dbf'

由于控制文件是新建的，执行恢复报错：
SQL> recover datafile 1;
ORA-00283: recovery session canceled due to errors
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done

我理解的应该是控制文件记录的与数据文件头不一致导致的。

那么问题来了，这种情况下如何把数据库打开？请高手指点

ALLSTARS_ORACLE

alter database open resetlogs
RESETLOGS is being done without consistancy checks. This may result
in a corrupted database. The database should be recreated.
RESETLOGS after incomplete recovery UNTIL CHANGE 223908
Archived Log entry 1 added for thread 1 sequence 1 ID 0x536aedc1 dest 1:
Resetting resetlogs activation ID 1399516609 (0x536aedc1)
Tue May 12 09:35:11 2015
Setting recovery target incarnation to 2
Initializing SCN for created control file
Database SCN compatibility initialized to 1
Tue May 12 09:35:11 2015
Assigning activation ID 1399520692 (0x536afdb4)
LGWR: STARTING ARCH PROCESSES
Tue May 12 09:35:11 2015
ARC0 started with pid=18, OS id=31769
ARC0: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
Thread 1 opened at log sequence 1
  Current log# 1 seq# 1 mem# 0: /u01/oradata/epdbstby/redo01.log
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Tue May 12 09:35:12 2015
SMON: enabling cache recovery
Tue May 12 09:35:12 2015
ARC1 started with pid=19, OS id=31773
Tue May 12 09:35:12 2015
ARC2 started with pid=20, OS id=31777
ARC1: Archival started
ARC2: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
Tue May 12 09:35:12 2015
ARC3 started with pid=21, OS id=31781
ARC2: Becoming the heartbeat ARCH
Errors in file /u01/app/oracle/diag/rdbms/epdbstby/epdbstby/trace/epdbstby_ora_31763.trc  (incident=104297):
ORA-00600: internal error code, arguments: [2662], [0], [223915], [0], [224176], [4194655], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/epdbstby/epdbstby/incident/incdir_104297/epdbstby_ora_31763_i104297.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file /u01/app/oracle/diag/rdbms/epdbstby/epdbstby/trace/epdbstby_ora_31763.trc:
ORA-00704: bootstrap process failure
ORA-00600: internal error code, arguments: [2662], [0], [223915], [0], [224176], [4194655], [], [], [], [], [], []
Errors in file /u01/app/oracle/diag/rdbms/epdbstby/epdbstby/trace/epdbstby_ora_31763.trc:
ORA-00704: bootstrap process failure
ORA-00600: internal error code, arguments: [2662], [0], [223915], [0], [224176], [4194655], [], [], [], [], [], []
Error 704 happened during db open, shutting down database
USER (ospid: 31763): terminating the instance due to error 704
Instance terminated by USER, pid = 31763
ORA-1092 signalled during: alter database open resetlogs...
opiodr aborting process unknown ospid (31763) as a result of ORA-1092
Tue May 12 09:35:14 2015
ORA-1092 : opitsk aborting process