Generally whenever you got ORA-00600 error on your screen or in the alert log or in trace files they indicate that something inconsistency happened with your oracle database software. This is raised from the kernel code of the Oracle RDBMS software when an unexpected condition is met. This mean exception encountered in the RDBMS kernel code.
A typical form of ORA-00600 error in the alert log is like below,
Errors in file /var/opt/dumpfile/udump/orastdby_ora_15862.trc:
ORA-00600: internal error code, arguments: [15160], [], [], [], [], [], [], []
Sat Nov 15 17:49:27 2008
•Whenever an ORA-600 error is raised a trace file is generated and an entry written to the alert.log with details of the trace file location.
•The trace file contains vital information about what led to the error condition.
•The trace file will be written to either USER_DUMP_DEST (if the error was caught in a user process) or BACKGROUND_DUMP_DEST (if the error was caught in a background process like PMON or SMON). In the above example we see trace file is generated in udump directory which indicates the error was caught in a user process.
•Besides with ORA-00600 we see a list of arguments in square brackets. The first argument tells us from where in the code the error was caught and thus it is the key information in identifying the problem. This argument is either a number or a character string.
•Subsequent arguments are used to supply further information eg. values of internal variables etc.
Related Documents
ORA-00600 internal error code, kmgs_pre_process_request_6
What is Alert Log?
No comments:
Post a Comment