RAC a node database cannot be started: ORA-00600: internal error code, arguments: [4: kg1_lditomicrots], [1], [], [], [], [], [, internalerror

RAC a node database cannot be started: ORA-00600: internal error code, arguments: [4: kg1_lditomicrots], [1], [], [], [], [], [, internalerror

The hardware of a customer's RAC node has changed. After the host is restarted, the database instance cannot be started. A large number of errors are reported when you log on to ALERT remotely:

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: kg1_lditomicrots], [1], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4: kg1_lditomicrots], [1], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4: kg1_lditomicrots], [1], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4: kg1_lditomicrots], [1], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4: kg1_lditomicrots], [1]

Check the MOS because the system time of the host is incorrect. The document isORA-00600: internal error code, arguments: [4: kg1_lditoepochts] (Document ID 1334956.1)

Check the node host time. It turns out that the time is incorrect --Incorrect yearThe values are the same for months, days, minutes, and seconds. The host time should be the initial time after the hardware is changed1970.

Contact the customer contact, coordinate the SA to adjust the time, and make another effort. Finally, all the work is done ..

The ORACLE database has an SQL error ORA-00600 that uses SYS_CONNECT_BY_PATH to summarize some data.

Bug 4401437 connect by query may fail with OERI: qergiStart1/OERI: qesmmCValStat4
This note gives a brief overview of bug 4401437.
The content was last updated on: 03-APR-2009
Click here for details of each of the sections below.

Affects:
Product (Component) Oracle Server (Rdbms)
Range of versions believed to be affected Versions BELOW 11.1
Versions confirmed as being affected
10.2.0.1
10.1.0.4
9.2.0.8

Platforms affected Generic (all/most platforms affected)

Workaround
Add a "no_filtering" hint to the query.

You can bypass this error by adding no_filtering!

If you are not sure, contact the professional ORACLE Database repair team of shita software to help you recover it!

Shita software professional database repair team

ORACLE ora-00600

[Kccpb_sanity_check_2] indicates that seq # of the last read block is
Higher than the seq # of the control file header block. This is indication
The lost write of the header block during commit of the previous cf
Transaction.

Because the database is damaged, the sequence # in the block is incorrect. We recommend that you restore data in the case of backup. Otherwise, you need experts to fix the data. If it is not a production database, we recommend that you recreate it.