ORA-07445 and ORA-00600 are internal error checking methods

Source: Internet
Author: User
Tags metalink

ORA-07445 and ORA-00600 are internal system errors, generally caused by bugs, to solve or avoid these errors generally need to be checked on metalink. Metalink even has a dedicated tool for finding these two errors.

Unlike Common Errors, ORA-07445 and ORA-00600 are the generic name for a series of errors that may lead to thousands of causes, how to quickly and accurately identify the cause of the error is the difficulty to solve this problem.
When a ORA-07445 or ORA-00600 error occurs, a trace file is generally generated, and the path and name of the file can be found in the alert file.
This article mainly talks about how to find key information in the trace file.

 

1. ORA-07445

The most important thing to find out the ORA-007445 is to find the name of the function (the function here refers to the function that develops ORALCE), and then search for the cause and solution of the error according to the function name.
The ORA-07445 is followed by several [] strings, and the first string to be [] is the name of the function we need.
The error of ORA-07445 generally has two kinds:
1) ORA-07445: exception encountered: core dump [lnxmin () + 252] [SIGSEGV] [Address not mapped to object] [0x000000002] [] []
This situation is very simple. The first string enclosed by [] is lnxmin, which is the name of the function that causes the error. We can check this information.

2) ORA-07445: exception encountered: core dump [0000000100E84B7C] [SIGSEGV] [Address not mapped to object] [0x0000004F0] [] []
This situation is troublesome, because Oracle does not tell us the name of the function with an error. The limit 000100e84b7c may be an address and cannot be used as a keyword for query.
Now we have to start with the trace file. Call Stack trace in the first part of the trace file can find useful information.
By comparing multiple trace files, we can find that the call stack trace generally contains the following content:
----- Call stack trace -----
Calling call entry argument values in hex
Location Type Point (? Means dubious value)
----------------------------------------------------------------------------
Ksedmp () + 328 call ksedst () + 0 ffffffff7fff3bd0?
000000000? 000000000?
00000003e?
Ffffffff7fff4468?
1031d56c8?
Ssexhd () + 604 call ksedmp () + 0 000000000? 000103400?
0001035d9? 000102c00?
1035d9000? 1035d9c28?
Sigacthandler () + 44 ptr_call 0000000000000000 1035e1000?
Ffffffff7fff5400?
000000000? 000000001?
1035DEDD8? 00000000B?
Qsmkzii_init_qsmksi PTR_CALL 0000000000000000 limit B?
Nline () + 624 FFFFFFFF7FFF5400?
FFFFFFFF7FFF5120?
00000000B? 00038001C?
1035DC458?
Qsmkzss_setup_summa CALL qsmkzii_init_qsmksi ffffff7cd12908?
Ry () + 480 nline () + 0 000103000?
FFFFFFFF7CD93650?
000000000?
FFFFFFFF7CD93650?
103258100?
......

Among them, the three functions ksedmp, ssexhd, sigacthandler in each ORA-07445 [0000000100E84B7C] similar trace files exist, this is oracle Exception Processing, generally don't worry.
The fourth row of the first column of the stack is the information we need: qsmkzii_init_qsmksinline. This is the name of the function with an error.
In metalink, you can find out the cause of the Error Based on the function name, and check whether there are appropriate options to solve the problem and avoid the error.
If no useful information is available according to the function name in the fourth row, you can try the information in the fifth row as the function name. If no useful information can be found, this error message is not found on metalink.

2. ORA-00600
Finding the key information of a ORA-00600 is a little simpler than a ORA-07445, which is equivalent to the first case of a ORA-07445.
After the ORA-00600 is generally followed by several [] string, usually the first string to be [] is the parameter we need.
The error message for the ORA-00600 exists both from the alert file and the trace file, but we recommend that you look at the trace file for more information.
A trace file for a ORA-00600 is similar to the following:
* ** Session ID: (22.3813) 09:57:13. 167
* ** 09:57:13. 167
Ksedmp: internal or fatal error
ORA-00600: Internal error code, arguments: [ttcgcshnd-1], [0], [], [], [], [], [], [], []
Current SQL statement for this session:
Select value from nls_instance_parameters where parameter = 'nls _ date_format'
----- Call stack trace -----
Calling call entry argument values in hex
Location Type Point (? Means dubious value)
----------------------------------------------------------------------------
Ksedmp () + 328 call ksedst () + 0 ffffffff7fff9660?
000000000? 000000000?
00000003e?
Ffffffff7fff9ef8?
1031c9458?
Kgerinv () + 184 ptr_call 0000000000000000 000000000? 000103400?
0001035cd? 000102c00?
1035cd000? 1035cd328?
Kgeasnmierr () + 28 call kgerinv () + 0 1035cd588? 1036ede38?
0000013c8? 000000001?
1035cf694? 1035ce958?
Ttcgcshnd () + 248 call kgeasnmierr () + 0 1035cd588? 1036ede38?
1033a2758? 000000001?
000000000? 000000000?
Ttcc2u () + 784 call ttcgcshnd () + 0 1035cd588? 102da4880?

In the above information, ttcgcshnd-1 is the first parameter we are looking for, is also the keyword of the query.

3. Other useful information in Trace
Trace files in both ORA-00600 and ORA-07445 contain some other useful information.
In the process state section of the trace file, you can view the session information when an error occurs, including the host name, the user executed, and the tool used for execution.
This information may not be easy to find. The search method is to find the process state from the trace file, and then find the place where the first "session" (keyword) appears from the process state, this part of information contains the important information we need.

Check the keyword "HOST" to obtain the Client IP address.

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.