{"id":112,"date":"2015-05-27T16:34:53","date_gmt":"2015-05-27T16:34:53","guid":{"rendered":"https:\/\/dbadave.co.uk\/?p=112"},"modified":"2016-02-09T22:50:56","modified_gmt":"2016-02-09T22:50:56","slug":"ora-00600-kdsgrp1-in-database-alert-log","status":"publish","type":"post","link":"https:\/\/dbadave.co.uk\/ora-00600-kdsgrp1-in-database-alert-log\/","title":{"rendered":"ORA-00600 [kdsgrp1] In Database Alert Log"},"content":{"rendered":"

ORA-00600 [kdsgrp1]<\/strong><\/em><\/h2>\n

One of my clients has a database job that runs weekly\u00a0in the early hours of the morning. I have a cron job configured on their server to check the database alert log for errors on a regular basis and email me with any that it finds.<\/p>\n

This morning when I checked my emails there was one from that job reporting the following:<\/p>\n

Errors in file \/u01\/app\/oracle\/10.2\/rdbms\/log\/<SID>_ora_194248.trc:<\/em><\/p>\n

ORA-00600: internal error code, arguments: [kdsgrp1], [], [], [], [], [], [], [] Wed May 27 03:17:28 2015<\/em><\/p>\n

ORA-00600 errors are internal Oracle errors and on the Oracle support site they have a tool where you can enter the arguments for the error (in this case kdsgrp1) and see if there is anything on the Oracle support site about it.<\/p>\n

I duly did this and it returned a whole range of known bugs and issues. The one that looked likely to be most relevant for my situation was one that said the “error is thrown when a fetch operation fails to find the expected row.”<\/p>\n

It also said this could be caused by any of the following:<\/p>\n