Monday

ORA-00600: internal error code , and fixing


     One of the nightmares of Oracle DBA's is the dreaded ORA-00600 error code.

Whenever you see one of this pops up , it is bad news. It is an internal error code which implies that something grave happened , and oracle writed an entry to the trace file.
Your alert.log contains the path to that trace fileTake the information you get from your trace file and the first argument in the square brackets (the internal message number)This error is a bit different than the other simple ORA error codes with an explanation itself on the error. 

Now you have 2 options in your hands:


  1. If you have an oracle support agreement, you can open a service request to oracle, then hand them over what they want for investigation. Generally they send you a tool which packes up the alert log , trace file , and some information regarding the db you are working on and simply pack it for you to send them.
  2. Second , you can try to resolve it by yourself. But you can say how, i dont have anything regarding the error except the internal message number. Now this is where Metalink try to help you. You can head over to My Oracle Support (Metalink) and search for the Error look-up Tool, which will help you identify the reasons behind your dreaded error.


Here is a screenshot of it :




No comments:

Post a Comment