R12.2.6 installation failed with - Unable to rename database

报错信息：

日志信息：/data/ebsdb/VIS/12.1.0/appsutil/log/VIS_ebstest/12222150.log

Phase 3 Rename Database

Executing command: sh -c "ORACLE_SID=ORCLVIS;export ORACLE_SID;ORACLE_HOME=/data/ebsdb/VIS/12.1.0;export ORACLE_HOME; /data/ebsdb/VIS/12.1.0/bin/rman target / nocatalog @/data/e
bsdb/VIS/12.1.0/appsutil/out/VIS_ebstest/restore-rac3.rman > /data/ebsdb/VIS/12.1.0/appsutil/out/VIS_ebstest/restore-rac3.log"

Unable to rename database

    RW-50010: Error: - script has returned an error:   1
RW-50004: Error code received when running external process.  Check log file for details.
Running Database Install Driver for VIS instance

日志信息：/data/ebsdb/VIS/12.1.0/appsutil/out/VIS_ebstest/restore-rac3.log

Unable to rename database

    RW-50010: Error: - script has returned an error:   1
RW-50004: Error code received when running external process.  Check log file for details.
Running Database Install Driver for VIS instance

RMAN> #
2> # $Header: restore-rac3.rman 120.6 2013/03/15 16:42:00 rledezma noship $
3> #
4> # This shell script was originally built to reset the first node of
5> # a RAC database in Rapid Clone in 12.1 after an RMAN database restore
6> # procedure.  RI evolved to restore a single instance from an RMAN backup
7> # as well, so now it's used here too.
8> #
9> #
10> host "echo 'In the above output, if RMAN-03002 and RMAN-06054 errors are present, they can be safely ignored.' >> /data/ebsdb/VIS/12.1.0/appsutil/out/VIS_ebstest/restore-sin
gle2.log";
11> alter database open resetlogs;
12> shutdown normal
13> startup mount pfile=/data/ebsdb/VIS/12.1.0s/RMANinit.ora
14> exit
host command complete

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of sql statement command at 12/22/2016 22:19:00
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: '/u01/R122_EBS/data/sys1.dbf'

Recovery Manager complete.

从上可以看出数据文件被恢复到/u01，但是环境中并没有该目录。

报错原因：安装介质部分受损　

v100053-01_2of2.zip
官网介质的md5值： 		md5	54d720a36bd0b89ec70241cbae937dae
本次安装介质的md5值：	md5 7d5cbdfbe03e0e929a8c4c8c50c0851d