How to get plan signature tracing for ORA-12850
(Doc ID 2180844.1)
Last updated on NOVEMBER 07, 2023
Applies to:
Oracle Database Backup Service - Version N/A and laterOracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.
Purpose
ORA-12850 errors are usually caused by the worker getting a plan signature different from that of the QC. These are typically, although not always, QRY OPTIMIZER bugs. This note provides the recommended tracing needed in order to see if there is a signature-plan mismatch and diagnose the cause of ORA-12850.
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 |
| <Internal_Only> |
| RESULTS |
| </Internal_Only> |
| References |