Oracle 在运行”Adcfgclone.pl dbTier”时快速克隆失败: ORA-01194 和RC-00118

如果自己搞不定可以找诗檀软件专业ORACLE数据库修复团队成员帮您恢复!

诗檀软件专业数据库修复团队

服务热线 ： 13764045638 QQ号:47079569 邮箱：service@parnassusdata.com

[oracle@ocm_rac01 ~]$ oerr ora 1194
01194, 00000, "file %s needs more recovery to be consistent"
// *Cause: An incomplete recovery session was started, but an insufficient
// number of logs were applied to make the file consistent. The
// reported file was not closed cleanly when it was last opened by
// the database. It must be recovered to a time when it was not being
// updated. The most likely cause of this error is forgetting to
// restore the file from a backup before doing incomplete recovery.
// *Action: Either apply more logs until the file is consistent or restore
// the file from an older backup and repeat recovery.

症状

在11.5.10.2，当运行”perl adcfgclone.pl dbTier”，发生以下错误：

…
Connected to an idle instance.
ORACLE instance started.

Total System Global Area 581506616 bytes
Fixed Size 452152 bytes
Variable Size 402653184 bytes
Database Buffers 167772160 bytes
Redo Buffers 10629120 bytes

Control file created.

alter database open resetlogs
*
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: ‘/u1/TEST/testora/testdata/system01.dbf’

alter tablespace TEMP add tempfile ‘/u1/TEST/testora/testdata/temp01.dbf’ REUSE
*
ERROR at line 1:
ORA-01109: database not open

alter tablespace TEMP add tempfile ‘$RDBMS ORACLE_HOME/data/temp02.dbf’ REUSE
*
ERROR at line 1:
ORA-01109: database not open

ALTER DATABASE RENAME GLOBAL_NAME TO “TEST.zexsa.com”
*
ERROR at line 1:
ORA-01109: database not open

——————-ADX Database Utility Finished—————

RC-00118: Error occurred during creation of database
Raised by oracle.apps.ad.clone.ApplyDatabase

StackTrace:
java.lang.Exception: Control file creation failed
at oracle.apps.ad.clone.ApplyDatabase.<init>(ApplyDatabase.java:658)
…

原因

使用”shutdown abort”，源数据库被关闭，导致一些”*.dbf” 文件不一致。

解决方案

请按照以下解决方案之一（在一个完全损坏或非业务关键的实例中）：
解决方案 1

启动mount;
SQL> recover database using backup controlfile until cancel;
— type CANCEL
SQL> alter database open resetlogs;

重试克隆。如果SQL 命令或重新尝试克隆无法恢复数据库，那么你必须按照解决方案2。该问题没有其他解决方案。

解决方案2
1. 正常关闭源数据库。
2. 将数据库文件从源数据库重新复制到目标数据库并重试克隆进程。

参考

NOTE:230672.1 - Cloning Oracle Applications Release 11i with Rapid Clone