ORA-600[qesmmCChgWAReq2] Generated by a JOIN Query
(Doc ID 2359255.1)
Last updated on OCTOBER 09, 2023
Applies to:
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and laterOracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
A complex query with a JOIN for multiple tables fails with an ORA-600[qesmmCChgWAReq2] error.
The Call Stack Trace in the associated incident trace file shows:
- Changing the query to use UNION instead of JOIN does not generate the error.
- Each session that raises the error has this in common:
session cursor with flag FETCH=1;
This means that the query is blocked on retrieving data from an INDEX.
- Analyzing the tables to check for table/index mismatches and/or corruptions (i.e. analyze table ... validate structure cascade;) doesn't raise any error, but hangs.
- Rebuilding online the indexes of the tables involved does not resolve the problem.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |