Parse activities <percentage>%, <number of> prepares, <number of> commands
The number of parse activities in the total number of statements executed is very high.
Before an SQL statement is executed for the first time, it has to be analyzed (parsed) first. When doing this, the database system determines the possible access strategies, and saves the statement to the database instance in a compact form. When the statement is executed again, only this internal information is accessed, and the statement executed directly.
For static SQL statements, the C/C++ precompiler makes sure that the parse activity is performed only once. In applications that are based on ODBC or the C/C++ precompiler, and that use the PREPARE statement, the developer is responsible for the number or parse or EXECUTE requests.
If the JDBC interface is used, and the parse info cache is active, the JDBC interface is responsible for the optimization of the parse requests. However, you must keep the number of PREPARE statements as small as possible here as well.
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.
A high level of parse activity is normal when programs or program parts are started for the first time.