資料字典不一致造成大量ORA-600和ORA-7445錯誤

測試環境中，由於將資料字典表錯誤的匯入到當前的資料庫SYS使用者下，導致資料字典出現了不一致的狀態，反應出來的結果就是大量的ORA-600和ORA-7445錯誤。

列幾個錯誤資訊，簡單記錄一下這個問題：

Fri Feb 10 16:30:14 CST 2012
Errors in file /u01/app/oracle/admin/orcl10g/udump/orcl10g_ora_8690.trc:
ORA-00600: internal error code, arguments: [16201], [1403], [], [], [], [], [], []
Fri Feb 10 16:30:16 CST 2012
Errors in file /u01/app/oracle/admin/orcl10g/udump/orcl10g_ora_8690.trc:
ORA-00600: internal error code, arguments: [16201], [1403], [], [], [], [], [], []

.
.
.

Fri Feb 10 22:00:05 CST 2012
Errors in file /u01/app/oracle/admin/orcl10g/bdump/orcl10g_j001_22380.trc:
ORA-07445: exception encountered: core dump [kdapblkcntt()+115] [SIGSEGV] [Address not mapped to object] [0x000000188] [] []
Sat Feb 11 06:00:06 CST 2012
Errors in file /u01/app/oracle/admin/orcl10g/bdump/orcl10g_j001_23555.trc:
ORA-07445: exception encountered: core dump [kdapblkcntt()+115] [SIGSEGV] [Address not mapped to object] [0x000000188] [] []

.
.
.

Mon Feb 13 15:17:22 CST 2012
Errors in file /u01/app/oracle/admin/orcl10g/udump/orcl10g_ora_14705.trc:
ORA-00600: internal error code, arguments: [ktsircinfo_num1], [6], [9], [1139], [], [], [], []

.
.
.

Mon Feb 27 17:30:25 CST 2012
Errors in file /u01/app/oracle/admin/orcl10g/udump/orcl10g_ora_889.trc:
ORA-00600: internal error code, arguments: [ktssdrp1], [7], [6], [11], [], [], [], []
Mon Feb 27 17:30:30 CST 2012
ORA-600 signalled during: drop tablespace perfstat including contents cascade constraints...
Mon Feb 27 17:30:43 CST 2012
drop tablespace perfstat including contents cascade constraints

.
.
.

Wed Feb 29 23:07:03 CST 2012
Errors in file /u01/app/oracle/admin/orcl10g/udump/orcl10g_ora_1401.trc:
ORA-00600: internal error code, arguments: [kcfrbd_3], [1], [240841], [1], [186752], [186752], [], []

.
.
.

Mon Mar 12 12:06:58 CST 2012
Errors in file /u01/app/oracle/admin/orcl10g/udump/orcl10g_ora_22193.trc:
ORA-00600: internal error code, arguments: [kzdugt], [], [], [], [], [], [], []

這些錯誤中，有個別錯誤在MOS中就沒有任何記錄，而另外一些，雖然存在記錄，但是都和當前的錯誤現象不符。且所有的錯誤都是在資料字典不一致後出現的，因此可以確定，這些錯誤都與資料字典不一致有關。

一般情況下，資料庫不會產生這種異常，如果真是由於匯入或者直接修改導致資料字典的異常，那麼推薦採用exp匯出，重建imp匯入的方式來解決問題。

最後還要強調一次，資料字典的修改是非常危險的，無論是有意為之還是無心之過。