Understanding and Avoiding ORA-600  Errors
(Doc ID 386347.1)
Last updated on APRIL 06, 2020
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 to 10.2.0.1 [Release 8.1.7 to 10.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
This article has been written to provide a method of determining an indication of minimum time duration for ORA-600  to be encountered when long running batchjobs are submitted to the database. It is recommended for use when ORA-600  is seen in the alert log and questions are being raised about how long a batchjob can be run for without some code change being required.
The article does not cover how to identify the offending code that is causing the error (typically this would be reported in the customer trace file) but it does provide a simple PLSQL example and highlights specific areas in the trace file to show why the internal error is raised.
If ORA-000  is encountered and it is considered that there are no batchjobs that run for longer than the duration identified the error is still almost certainly to be due to application design.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document