Skip to end of metadata
Go to start of metadata

Use

 Parse activities <percentage>%, <number of> prepares, <number of> commands


Explanation

 The number of parse activities in the total number of executed statements is high.

Before an SQL statement is executed for the first time, it has to be analyzed (parsed) first. To do this, the database system determines the possible access strategies and saves the SQL statement to the database in a compact form. When the statement is executed again, only this internal information is accessed, and the statement is executed directly.

In applications that are based on ODBC and use the PREPARE statement, the developer is responsible for the number of parse or EXECUTE requests.

If the SQLDBC or JDBC interface is used, and the parse info cache is active, the corresponding interface is responsible for optimizing the parse requests.

 

User Response

A high level of parse activity when the database is running can indicate a missing statement cache implementation in your application, or a deactivated parse info cache in the JDBC interface.

Note:

A high level of parse activity is normal when programs or program components are started for the first time.

 

More Information

Relevant  DB-Analyzer Files
Helpful with ...
DBAN_SHARED_SQL.csv Provides statistics about shared SQL (hit rates of the prepare cache, command cache, cleanup, unload) 
SAP Note
Helpful with ...
  
Expert Sessions (Link to trainings)
Content / Helpful with ...
  
Documentation (Links)
 
  • No labels