Email: service@parnassusdata.com 7 x 24 online support!

    You are here

    • You are here:
    • Home > Blogs > PDSERVICE's blog > Oracle ORA-10877: error signaled in parallel recovery slave ORA-600:[3680] During Recovery Of An RMAN Restored DB

Oracle ORA-10877: error signaled in parallel recovery slave ORA-600:[3680] During Recovery Of An RMAN Restored DB

Oracle ORA-10877: error signaled in parallel recovery slave ORA-600:[3680] During Recovery Of An RMAN Restored DB

 

 

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

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

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

 

ORA-10877: error signaled in parallel recovery slave

ORA-00600: 内部错误代码, 参数: [], [], [], [], [], [], [], [], [], [], [], []

 

ORA-01112

oerr ora 1112
01112, 00000, "media recovery not started"
// *Cause: An attempt to continue media recovery is being made but media
// recovery was not started.
// *Action: None.

 

 

适用于:

Oracle Database – Enterprise Edition – 版本11.2.0.4 及以上
本文信息适用于任何平台。

症状

控制文件和数据文件从一个RMAN备份中被还原

在SQL * Plus(并行和串行)恢复,而RMAN 在序列17051不断失败,显示 ORA-600 [3680]

该归档日志的Dump validate没有返回任何问题Dump validate of this archivelog returned no issues

SQL> alter system dump logfile ‘E:\ORACLE\ORADATA\ICD\ARCHIVE\ARCH_1_17051_821234673.DBF’ validate;
System altered.

======

RMAN 和 SQL 恢复(并行和非并行)都失败并显示相同错误

1) RMAN 恢复:
RMAN> run
2> {
3> set until sequence 17073;
4> recover database;
5>}

RMAN-03002: failure of recover command at 12/21/2014 08:37:59
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile ‘E:\ORACLE\ORADATA\ICD\ARCHI
VE\ARCH_1_17051_821234673.DBF’
ORA-10877: error signaled in parallel recovery slave

相关alert.log 条目:

Media Recovery Start
started logmerger process
Parallel Media Recovery started with 64 slaves
ORA-279 signalled during: alter database recover if needed
start until cancel using backup controlfile

alter database recover logfile ‘E:\ORACLE\ORADATA\ICD\ARCHIVE\ARCH_1_17050_821234673.DBF’
Media Recovery Log E:\ORACLE\ORADATA\ICD\ARCHIVE\ARCH_1_17050_821234673.DBF
Sun Dec 21 08:37:57 2014
ORA-279 signalled during: alter database recover logfile ‘E:\ORACLE\ORADATA\ICD\ARCHIVE\ARCH_1_17050_821234673.DBF’…
alter database recover logfile ‘E:\ORACLE\ORADATA\ICD\ARCHIVE\ARCH_1_17051_821234673.DBF’
Media Recovery Log E:\ORACLE\ORADATA\ICD\ARCHIVE\ARCH_1_17051_821234673.DBF
Sun Dec 21 08:37:57 2014
Errors in file D:\ORACLE\diag\rdbms\icd\icd\trace\icd_pr00_16380.trc (incident=1616729):
ORA-00600: internal error code, arguments: [3680], [], [], [], [], [], [], [], [], [], [], []
Incident details in: D:\ORACLE\diag\rdbms\icd\icd\incident\incdir_1616729\icd_pr00_16380_i1616729.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Recovery interrupted!
Media Recovery failed with error 600
Errors in file D:\ORACLE\diag\rdbms\icd\icd\trace\icd_pr00_16380.trc:
ORA-00283: recovery session canceled due to errors
ORA-00600: internal error code, arguments: [3680], [], [], [], [], [], [], [], [], [], [], []
ORA-10877 signalled during: alter database recover logfile ‘E:\ORACLE\ORADATA\ICD\ARCHIVE\ARCH_1_17051_821234673.DBF’.

2) SQL 恢复:
SQL> recover database noparallel using backup controlfile until cancel;
ORA-279: change 9120881074788 generated at 12/19/2014 04:11:08 needed for thread 1
ORA-289: suggestion : E:\ORACLE\ORADATA\ICD\ARCHIVE\ARCH_1_17050_821234673.DBF
ORA-280: change 9120881074788 for thread 1 is in sequence #17050

Specify log: {=suggested | filename | AUTO | CANCEL}

ORA-279: change 9120881093340 generated at 12/19/2014 05:14:56 needed for thread 1
ORA-289: suggestion : E:\ORACLE\ORADATA\ICD\ARCHIVE\ARCH_1_17051_821234673.DBF
ORA-280: change 9120881093340 for thread 1 is in sequence #17051 ORA-278: log file
‘E:\ORACLE\ORADATA\ICD\ARCHIVE\ARCH_1_17050_821234673.DBF’ no longer needed for this recovery

Specify log: {=suggested | filename | AUTO | CANCEL}
ORA-283: recovery session canceled due to errors
ORA-600: internal error code, arguments: [3680], [], [], [], [], [], [],

ORA-1112: media recovery not started

 

 

原因

在控制文件中似乎有不一致性,阻止恢复继续应用所需的重做

重做日志成功验证,所以这不是一个损坏的重做
ORA-600 [3680] 是一个控制文件问题
解决方案

=> 重建控制文件并继续恢复