遇到如下报错(数据库版本为10205),根据mos和baidu搜索,结合现场环境情况使用第三种方法进行了恢复。
ora-00600:internal error code ,arguments:[kccpb_sanity_check_2],[3106],[3104],[0x000000000],[],[],[],[]
ORA-00600: [kccpb_sanity_check_2] During Instance Startup [ID 435436.1]
Cause
ORA-600 [kccpb_sanity_check_2] indicates that the seq# of the last read block is
higher than the seq# of the control file header block. This is indication of
the lost write of the header block during commit of the previous cf
transaction.
kccpb_sanity_check_2 表示最后读取的控制文件块其 seq# 控制序列号大于控制文件头块的 seq# ,这是不应该出现的情况。这说明在最后执行提交的控制文件事务(CF Transaction)中,对于头块的写入丢失了
Solution
1) restore a backup of a controlfile and recover
OR
2) recreate the controlfile
OR
3) restore the database from last good backup and recover
NOTE: If you do not have any special backup of control file to restore and you are using Multiple Control File copies in your pfile/init.ora/spfile you can attempt to mount the database using each control file one by one. If you are able to mount the database with any of these control file copies you can then issue 'alter database backup controlfile to trace' to recreate controlfile.
本文出自 “技术成就梦想!” 博客,转载请与作者联系!