My Oracle Support Banner

How to Find the Offending SQL from a ORA-600 or ORA-7445 Trace File (Doc ID 154170.1)

Last updated on JANUARY 21, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 8.1.7.0 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 23-Jan-2014***

NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.

Purpose

This article describes how to find the SQL statement that was active at the time an internal (ORA-600) error or ORA-7445 error was reported.

Troubleshooting Steps

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
Purpose
Troubleshooting Steps
 Scope and Application
 How to Find the Offending SQL from a Trace File
 --- Step 1: Find the SQL
 --- Step 2: Find values of the bind variables
 Examples
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.