A customer's RAC node hardware has changed, the host restarts after the database instance cannot start, remote login to view alert log found a large number of errors:
Writing to the above trace file is disabled
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]
Checked MoS, because the host's system time is incorrect, the document is ora-00600:internal error code, arguments: [4:kgstmlditoepochts] (document ID 1334956.1)
Seize the node host time, sure enough, is the wrong time-the year is not the same as the day of the month. The host's time should be to replace the hardware after recovering the initial time of 1970 .
Contact Customer contact, coordination SA adjustment time, and toss a pass, finally all done.
RAC a node database could not be started: ora-00600:internal error code, arguments: [4:kgstmlditomicrots], [1], [], [], [], [