Normally, the ORA-600 error will be displayed with a set of arguments. For example,
ORA-00600: internal error code, arguments: [12333], [0], [101], [2], [], [], [], []
1) You can then log in to metalink and use the ORA-600/ORA-7445 Troubleshooter
2) You have to provide the first argument of the error in this case it is 12333. Optionally you can choose your database version and submit.
3) Then the metalink reports the cause of the error, impact (any data corruption) and also it provides suggestions
4) But the better approach would be to raise a service request with oracle, because it is an internal error and only oracle technicians can interpret the trace files
Well, I have seen only two ORA-00600 errors this year, which needed no Oracle support.
On the first instance, a DBA ran a create database script on an already running instance. Then the instance started throwing ORA-00600 for few queries. They bounced the instance and the issue was solved. Not sure if bouncing an instance would be a right approach. What happens if the database refuse to come up? Luckily we did not face that issue.
On the second occasion, a java program calling a hierarchical query went in a nested loop causing ORA-00600. The java program was later identified and fixed, thus resolving the ora-00600 error.
Of-course, we logged an service request with oracle on both occasions.
Every ORA-00600 is a different issue, though the error looks same. The better approach would be to contact metalink support always.
Addendum on 27 March 2008 :
Since there are lot of people are hitting this page, I though it might be useful to give the URL of the ORA-600/ORA-7445 Troubleshooter (You need metalink access) :
You can also refer to the following notes on metalink
Note:146580.1 Additional ORA-600 related information.
Note:211909.1 Additional ORA-7445 related
Posted by Mani Balasubramanian
Posted by Mani Balasubramanian
Posted by Mani Balasubramanian