合 【MOS】How to Identify Hard Parse Failures Such as Error=923 (Doc ID 1353015.1)

GOAL

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:

FINDING 2: 62% impact (2561 seconds)
------------------------------------
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

SOLUTION

Failed parses are not stored in the data dictionary and therefore cannot be identified through querying the data dictionary.

As of Oracle10g, event 10035 can be set to report SQLs that fail during PARSE operations.

Syntax:

Another way to get the SQL_ID producing lot of hard parses, use the ASH tables and the column IN_HARD_PARSE:

后续精彩内容已被站长无情隐藏，请输入验证码解锁本文！

验证码：

获取验证码： 请先关注本站微信公众号，然后回复“验证码”，获取验证码。在微信里搜索“AiDBA”或者“dbaup6”或者微信扫描右侧二维码都可以关注本站微信公众号。