一个客户的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-0
一个客户的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调整时间,又折腾一通,终于全部搞定。。