ORA-600 is an internal error generated by the generic kernel code of the Oracle RDBMS software. It is different from other Oracle errors in many ways. The following is a list of these differences. 1. An ORA-600 error may or may not be displayed on the screen.
Therefore, screen output should not be relied on for capturing information on this error. Information on ORA-600 errors are found in the database alert and trace files. We recommend that you check these files frequently for database errors. (See the Alert and Trace Files section for more information.)
2. Each ORA-600 error comes with a list of arguments
They usually enclosed in square brackets and follow the error on the same line for example: ORA-00600 [14000][51202][1][51200][][] Each argument has a specific meaning which can only be interpreted by an Oracle support analyst. The arguments may also change meaning from version to version therefore customers are not advised to memorize them.
3. Every occurrence of an ORA-600 should be reported to Oracle Support.
Unlike other errors, you can not find help text for these errors. Only Oracle technical support should diagnose and take actions to prevent or resolve damage to the database.
4. Each ORA-600 error generates a database trace file.
Possible causes include
time-outs,
file corruption,
failed data checks in memory, hardware, memory, or I/O messages,
incorrectly restored files
Back to top of file
--------------------------------------------------------------------------------How to fix it
Contact Oracle support with the following information: events that led up to the error
the operations that were attempted that led to the error
the conditions of the operating system and database at the time of the error
any unusual circumstances that occurred prior to receiving the ORA-00600 message.
contents of any trace files generated by the error
the relevant portions of the Alert file
Therefore, screen output should not be relied on for capturing information on this error. Information on ORA-600 errors are found in the database alert and trace files. We recommend that you check these files frequently for database errors. (See the Alert and Trace Files section for more information.)
2. Each ORA-600 error comes with a list of arguments
They usually enclosed in square brackets and follow the error on the same line for example: ORA-00600 [14000][51202][1][51200][][] Each argument has a specific meaning which can only be interpreted by an Oracle support analyst. The arguments may also change meaning from version to version therefore customers are not advised to memorize them.
3. Every occurrence of an ORA-600 should be reported to Oracle Support.
Unlike other errors, you can not find help text for these errors. Only Oracle technical support should diagnose and take actions to prevent or resolve damage to the database.
4. Each ORA-600 error generates a database trace file.
Possible causes include
time-outs,
file corruption,
failed data checks in memory, hardware, memory, or I/O messages,
incorrectly restored files
Back to top of file
--------------------------------------------------------------------------------How to fix it
Contact Oracle support with the following information: events that led up to the error
the operations that were attempted that led to the error
the conditions of the operating system and database at the time of the error
any unusual circumstances that occurred prior to receiving the ORA-00600 message.
contents of any trace files generated by the error
the relevant portions of the Alert file
解决方案 »
免费领取超大流量手机卡，每月29元包185G流量+100分钟通话, 中国电信官方发货