How to Identify Hard Parse Failures Such as Error=923
(Doc ID 1353015.1)
Last updated on NOVEMBER 13, 2020
Applies to:Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 10.2.0.2 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Information in this document applies to any platform.
Hard parse time may be impacted when there are a high number of parse errors.
This may be noted in the ADDM report as follows:
Hard parsing SQL statements that encountered parse errors was consuming
significant database time.
RECOMMENDATION 1: Application Analysis, 62% benefit (2561 seconds)
ACTION: Investigate application logic to eliminate parse errors.
In the AWR report Parse Failures are recorded in two places:
1. Time Model Statistics
2. Instance Activity Stats
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!