如果自己搞不定可以找诗檀软件专业ORACLE数据库修复团队成员帮您恢复!
诗檀软件专业数据库修复团队
服务热线 : 13764045638 QQ号:47079569 邮箱:service@parnassusdata.com
适用于:
Oracle Database – Enterprise Edition – 版本 11.2.0.3 到 11.2.0.3 [Release 11.2]
本文信息适用于任何平台。
症状
闪回数据库到Guaranteed Restore Point (GRP)失败显示以下:
Flashback Restore Start
Wed Apr 22 17:13:45 2015
RFS[2]: Assigned to RFS process 10617306
RFS[2]: Database mount ID mismatch [0x7c9d3b45:0x7e106bfd] (2090679109:2115005437)
RFS[2]: Not using real application clusters
Wed Apr 22 17:13:58 2015
Flashback Restore Complete <<=======
Errors in file /usr2/oracle/sunoptp/diag/rdbms/sunopt_dr/sunopt/trace/sunopt_ora_26738752.trc (incident=328195):
ORA-00600: internal error code, arguments: [krhahws_02], [], [], [], [], [], [], [], [], [], [], []
Problem appears to match that described in Note 14556461.8
However, even after setting disk_asynch_io to false, flashback db to guaranteed restore point still fails with the below:
SQL> FLASHBACK DATABASE TO RESTORE POINT sunopt_dr;
FLASHBACK DATABASE TO RESTORE POINT sunopt_dr
*
ERROR at line 1:
ORA-01122: database file 6 failed verification check
ORA-01110: data file 6: ‘/u02/oradata/sunoptp/sunopt/data/ADD1201.dbf’
ORA-01207: file is more recent than control file – old control file
原因
数据库有只读表空间,且使用参数 READ_ONLY_OPEN_DELAYED=TRUE被mount
解决方案
1) 使用以下参数重新mount数据库:
disk_asynch_io = TRUE
read_only_open_delayed = FALSE
2) Then open with resetlogs as the database has already been flashed back
SQL> alter database open resetlogs;
3) 一旦数据库被打开,使用以下参数重新mount数据库,然后闪回到GRP以确保闪回进程整体完成:
disk_asynch_io = FALSE
read_only_open_delayed = FALSE
参考
BUG:14556461 – ORA-600 [KRHAHWS_02] WHEN USING FLASHBACK DATABASE
NOTE:14556461.8 – Bug 14556461 – ORA-600 [krhahws_02] when using flashback database
NOTE:67512.1 – Init.ora Parameter “READ_ONLY_OPEN_DELAYED” Reference Note
NOTE:1493350.1 – Master Note: Overview of Oracle Tablespace Management
Comment