Resolve ORA-00600 Internal Errors

For more information and videos, see https://blogs.oracle.com/database/post/ora-00600.

Follow these step-by-step instructions for everything you need to do to resolve ORA-00600.

ORA-00600 indicates that an Oracle Database process encountered an unexpected internal condition. In many cases, the error is associated with an Oracle Database software issue.

The effect of an ORA-00600 error varies. An occurrence might simply be recorded in the logs without noticeably affecting the database, while more serious occurrences can affect database availability.

For additional information about ORA-00600, see the Oracle Database blog about ORA-00600 errors.

Understand ORA-00600 Errors

When Oracle Database reports an ORA-00600 error, the error message contains one or more arguments enclosed in square brackets.

The arguments provide information that can help diagnose the problem:

• The first argument typically identifies the internal function or assertion associated with the error. It can help narrow the investigation to known issues. However, a commonly used function can be associated with several different causes.
• The remaining arguments contain internal values that can assist Oracle Support and engineering teams with diagnosis.

When an ORA-00600 error occurs, Oracle Database records it in the database instance alert.log. The alert log also identifies an associated trace file.

The trace file contains additional diagnostic information, including call-stack details, that might be necessary to determine the cause of the error.

Depending on the error, additional environmental and configuration information might also be required, including:

• Database configuration
• Operating system information

The general troubleshooting workflow is:

1. Use Oracle Autonomous Health Framework (AHF) to create an ORA-00600 Service Request Data Collection (SRDC).
2. Upload the diagnostic collection to the My Oracle Support ORA-00600 troubleshooting tool and review its recommendations.
3. If the problem cannot be resolved, create a Service Request (SR) and attach the diagnostic collection.

Generate an ORA-00600 Diagnostic Collection

Log in to the host where the ORA-00600 error occurred.

As the Oracle software owner, run:

tfactl diagcollect -srdc ORA-00600

AHF prompts you for information about the occurrence, including:

• Date and time of the ORA-00600 error
• Database name

If you do not know the exact time of the error, press Enter at the time prompt. AHF can search for recent occurrences.

AHF searches the selected database for matching ORA-00600 events and displays the events it finds.

For example:

$ tfactl diagcollect -srdc ORA-00600

Enter the time of the ORA-00600 [YYYY-MM-DD HH24:MI:SS,<RETURN>=ALL] :
Enter the Database Name [Required for this SRDC] : cdb19

1. Feb/11/2024 10:15:56 PST: [cdb19] ORA-00600: internal error code, arguments: [ktsircinfo_num1], [7], [1024], [1921], [], [], [], [], [], [], [], []

2. Feb/11/2024 06:14:48 PST: [cdb19] ORA-00600: internal error code, arguments: [ktsircinfo_num1], [7], [1024], [1921], [], [], [], [], [], [], [], []

Please choose the event : 1-2 [1]
Selected value is : 1 ( Feb/11/2024 10:15:56 )

Select the event that you want to investigate.

AHF determines the diagnostic components required for the SRDC and begins collecting information from the relevant files and services.

A typical collection can include components such as:

OS
DATABASE
NOCHMOS
ASM
SOSREPORT

AHF searches the diagnostic files around the time of the selected event and collects relevant information, including applicable ADR incident files and other diagnostic data.

After collection is complete, AHF displays a collection summary similar to the following:

.---------------------------------------.
|           Collection Summary          |
+-------------+-----------+------+------+
| Host        | Status    | Size | Time |
+-------------+-----------+------+------+
| mymachine   | Completed | 53MB | 155s |
'-------------+-----------+------+------'

AHF packages the diagnostic information into a ZIP file.

For troubleshooting an error on a particular database node, use the diagnostic package generated for the node on which the problem occurred.

Analyze the Diagnostic Collection in My Oracle Support

After generating the SRDC package, use the My Oracle Support ORA-00600 troubleshooting tool to analyze the error.

1. Sign in to My Oracle Support.
2. Search for ORA-00600, or open the ORA-00600 troubleshooting tool.
3. Proceed through the troubleshooting workflow.
4. Select the option to upload a TFA diagnostic package.
5. Select the ZIP file generated by AHF.
6. Upload the diagnostic package.
7. Continue to the next step after the upload completes.

The troubleshooting tool analyzes the diagnostic collection and compares information from the logs with known Oracle Database problems.

Based on the analysis, the tool can recommend a relevant My Oracle Support Knowledge document.

The recommended document can provide:

• Troubleshooting instructions
• Known issues associated with the ORA-00600
• Related Oracle Database bugs
• Information that can help determine which Database Release Update (RU) contains a fix

Review the recommendations and determine whether one of the identified solutions resolves the problem.

Create a Service Request

If the My Oracle Support troubleshooting tool does not identify a suitable solution, or if additional assistance is required, create a Service Request with Oracle Support.

1. In the troubleshooting tool, select Create SR.

2. Provide the requested information, such as:

   • Product
   • Product version
   • Support Identifier
   • Operating system
   • SR severity
3. Select Create SR.

My Oracle Support creates a Service Request and assigns an SR number.

The AHF diagnostic collection that you previously uploaded is associated with the Service Request, allowing Oracle Support to continue the investigation using the diagnostic information already collected.