How to use DBMS_SQLDIAG to Diagnose Crash or Error Issues
(Doc ID 1360120.1)
Last updated on JULY 15, 2022
Applies to:Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 220.127.116.11 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
Information in this document applies to any platform.
This article describes how to use DBMS_SQLDIAG to find workarounds for issues where a query causes a session to crash or raise a critical error.
The article is specifically designed to address ora-7445 errors but can be easily modified to deal with other issue types.
For other ways of using DBMS_SQLDIAG see:
This article is not intended to describe how to implement workarounds using the 'SQL Patch' functionality. It is intended to provide potential workaround for critical errors like an ORA-7445 error.
For details of how to apply 'SQL Patch' refer to the DBMS_SQLDIAG.ACCEPT_SQL_PATCH procedure. See:
11g Release 2 (11.2)
Part Number E10577-04
Chapter 137 DBMS_SQLDIAG
Running the SQL Repair Advisor
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
|Example Diagnostic Script|
|Create a Diagnostic Task|
|Execute the Diagnostic Task|
|Generate a Report Output|
|The report output in this example looks like this:|
|Execute the recommendation, when available|
|Verify if implementing the recommendation helps to workaround the problem or not|
|Generate an execution plan for same exact SQL statement to verify use of SQL Patch|
|Cleanup the Diagnostic Task|
|Information about the referenced trace file and related SQL statement|