標籤:style blog http color os ar strong for 資料
一個客戶的RAC節點硬體發生了變動,主機重啟後資料庫執行個體無法啟動,遠程登陸查看ALERT日誌發現大量報錯:
Writing to the above trace file is disabled for now on...
Errors in file /oracle/app/diag/rdbms/XXXX/XXXX2/trace/XXXX2_ora_184464.trc:
ORA-00600: internal error code, arguments: [4:kgstmLdiToMicroTs], [1], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4:kgstmLdiToMicroTs], [1], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4:kgstmLdiToMicroTs], [1], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4:kgstmLdiToMicroTs], [1], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4:kgstmLdiToMicroTs], [1]
查了MOS,原因是主機的系統時間不對,文檔是ORA-00600: internal error code, arguments: [4:kgstmLdiToEpochTs] (文檔 ID 1334956.1)
抓緊檢查節點主機時間,果然是時間不對--年份不對,月日時分秒都是一致。主機的時間應該是更換硬體後恢複了初始時間1970年。
聯絡客戶連絡人,協調SA調整時間,又折騰一通,終於全部搞定。。
RAC一個節點的資料庫無法啟動:ORA-00600: internal error code, arguments: [4:kgstmLdiToMicroTs], [1], [], [], [], [