ORA-00600 internal error code, arguments

Cause: This is the generic internal error number for Oracle program exceptions. It indicates that a process has encountered a low-level, unexpected condition. Causes of this message include:

1. timeouts (timeout) 2. file Upload uption (the file is too old) 3. failed data checks in memory Retrieval failed) 4. hardware, memory, or I/O errors (hardware, memory, or disk error) 5. incorrectly restored files (incorrect reconstruction file) The first argument is the internal message number. other arguments are various numbers, names, and character strings. the numbers may change meanings between different versions of Oracle.

Action taken: Report this error to Oracle Customer Support after gathering the following information: 1. events that led up to the error 2.the operations that were attempted that led to the error 3.the conditions of the operating system and databases at the time of the error 4.any unusual circumstances that occurred before fixing the ORA-00600 message 5. contents of any trace files generated by the error 6.the relevant portions of the Alter files Note: The cause of this message may manifest itself as different errors at different times. be aware of the history of errors that occurred before this internal error.

This problem is hard to solve. I have encountered many such problems recently and have not solved them yet. I am bored. Maybe oracle is making money by this problem.

Cause: this error is usually an internal ORACLE error and is only useful for OSS and ORACLE development. ORA-600 errors are often accompanied by a State dump of the trace file (system and process state) where system state storage will include information about the current object held by oracle rdbms, the Process status dump displays the objects held by the special process. When the process meets an error condition, it is often because some information is taken from a block held by the process, if we know the blocks held by these error processes, it is easy to track the source of the problem.

Solution: in general, this error cannot be solved. We only need to improve the system to solve this internal problem, such as adding hardware devices and adjusting system performance, using OPS (of course, OPS is not a good solution in a sense. The first variable of the ORA-600 error is used to mark the location of the error in the Code (the first variable in each part of the code is different), from the second to the fifth variables display additional information, tell the OSS code where an error occurs.

Suggestion:
1. Ask your user
When an error occurs, does the front-end receive an error message?
If so, this is an important auxiliary diagnostic information.

2. It is best to replace the NIC to eliminate this suspicion.

3. Check the background process trace file to see if an exception is recorded.

4. database version?

If you encounter this problem again today, check the trc file and the following message is displayed:

ORA-00600: internal error code, arguments: [12333], [187], [186], [232], [], [], [], [], []
Current SQL statement for this session:
Insert Into doc_researchreport (sys_id, sys_control5, reportTypeName, investSuggest) values (: 1,: 2,: 3,: 4)

It may be because there is a problem with inserting records or the transaction waits too long and times out. I really don't know how to solve it...

On the internet found a lot of netizens encountered this problem (ora-00600 error is really everywhere ):

He encountered this problem when upgrading a Test Library, because the host name was modified through the hostname command, resulting in an instance crash in the Oracle 10201 for Linux X86-64 environment, A ORA-600 (keltnfy-ldmInit) error occurs in the alert file.

ORA-00600: internal error code, arguments: [keltnfy-ldmInit], [46], [1], [], [], [], [], [], []

Description of Doc ID: Note: 5486074.8 in meatlink of Oracle: this error message is displayed when Oracle cannot determine the host name or network address.

Oracle fixed this bug in 10.2.0.4 and 11.1.0.6. On metalink of Oracle, this error may occur before 10.2.0.4.

However, the test shows that Oracle9i does not cause errors due to the modification of the hostname.