遇到如下報錯(數據庫版本為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.

總結

以上是生活随笔為你收集整理的oracle 00600 kccpb,ora-00600 [kccpb_sanity_check_2] 错误处理的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。