Translate into your own language

Tuesday, May 24, 2016

How to Troubleshoot ORA-00600 Internal error in Oracle

ORA-00600 and ORA-07445 Troubleshooting are an integral part of Oracle Database Administrator's life. In some cases these error could crash database instance's or in others does very minor impact.

So, I would suggest to start working on ORA-00600 and ORA-07445 immediately, you notice them. My agenda for this post is to explain the approach for solving ORA-00600 and ORA-07445 Internal error, which would be more helpful rather than solving one or two issues.

What is ORA-00600 and ORA-07445 Internal error ?

As we know, basic code of database is written in C and C++ Language. When a function in C call another function but got some unexpected results and which is not handled by Oracle Code, then DBA encounter ORA-00600 or ORA-07445 Internal error. On further discussion in this article, we will also see which function is failed and case these errors.

Troubleshooting ORA-00600 

1. Getting Error Detail from Alter log and Trace file:

Whenever, this error arise, it is written in to database alert log files with trace file having details about this error. So, first task is to find trace file from alter log holding about this error.
Oracle 11g Alter log entry with error ORA-00600 and trace files path

Wed May 25 15:41:47 2016
Errors in file /u01/app/oracle/diag/rdbms/remotedba/remotedba1/trace/remotedba1_pr00_19608.trc (incident=222458):
ORA-00600: internal error code, arguments: [1433], [60], [], [], [], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/remotedba/remotedba1/incident/incdir_222458/remotedba1_pr00_19608_i222458.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.

In case of Oracle 10g, Just A small difference, Instead of Incident file detail you will see trace file path. Open the trace/incident files and you will find description about this error. Though, it's not very human readable.


2. Login to https://support.oracle.com to Troubleshoot:

If, you need an accurate solution of this error, then you can only find at https://support.oracle.com. So, first of all, you must have an Oracle Support user ID and Password.

Login to support.oracle.com

Search for Article "153788.1" in knowledge base. This will open an article "ORA-600/ORA-7445/ORA-700 Error Look-up Tool [Article ID 153788.1]" This looks like this.



3. Search Error in this tool:

In the above screen choose error code DBA is facing in alter log files (ORA-600 or ORA-7445). Next is filling "Error Code First Argument". Whatever you are getting in fist [] after ORA-600 or ORA 7445 is called as first argument.

E.g. ORA-00600: internal error code, arguments: [1433]

In this error 1433 is the first argument.

You just need to copy first argument in "Error Code First Argument" box. Here, I am taking ORA-00600: internal error code, arguments: [1433] as an test case. Choose Oracle version database is running on from "Oracle RDBMS Version" drop box. Here, I am choosing 11.2.0.3. After filling all this information. Click "Look-up Error". This will search Oracle knowledge base for matching documents.



Document 138413.1 is the matching document with given error in Alert log file. This document has all details about bug, affected versions, workaround or fix for it. Click on the link for the document and see the details.

In this case, below are the details.

    a. Bug number: 12899768

    b. Fixed in versions: 11.2.0.2.8, 11.2.0.2.BP18, 11.2.0.3.BP11, 12.1.0.0

    c. Workaround: Increase _messages init.ora parameter to a large value.

Apply the suggested solution and your problem is solved.

No comments:

Post a Comment