High parse activity:<number of> prepares per command, <number of> commands (executes), <number of> prepares

Compared to the total number of statements executed, the number of parses is too high. Before an SQL statement is executed for the first time, the database system analyzes (parses) the SQL command string, whereby it determines the possible access strategies and stores the statement in a compact form in the database, among other actions. After this, the database only needs to access this internal information and then directly execute the statement.

If the statement was created using static SQL and a precompiler, the precompiler ensures that the parse only occurs once for each statement. If dynamic SQL or the CALL interface was used, the developer is responsible for the administration of the parse and execute requests. High amounts of parse activity in production operation may mean the cursor cache was implemented incorrectly. High parse activity is normal the first time a program or subprogram is started.

This cannot be influenced by any specific change to the database.