How to Use DBMS_SQLDIAG to Generate a Workaround for Wrong Results Issues
(Doc ID 466604.1)
Last updated on SEPTEMBER 20, 2022
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 and later
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
There are four possible problem types for DBMS_SQLDIAG :
This article describes how to use DBMS_SQLDIAG to find workaround for wrong results issues but could be easily modified to deal with other issue types.
This article is not intended to describe how to implement workarounds using the 'SQL Patch' functionality. It is intended to illustrate how DBMS_SQLDIAG can be executed to provide a SQL_Patch that can be used to workaround an issue. For details of how to apply 'SQL Patch' refer to the DBMS_SQLDIAG.ACCEPT_SQL_PATCH procedure. See:
12c Release 1 (12.1)
Chapter 152 DBMS_SQLDIAG
Running the SQL Repair Advisor
Once a workaround has been implemented, the report can potential provide further diagnostics for wrong results problems to assist find the root cause of such problems. Details of how to do this can be found in:
For Support Analyst and DBA's
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