Query optimization performance information messages

You can evaluate the structure and performance of the SQL statements in a program using informational messages. These messages are put in the job log by the database manager.

The messages are issued for an SQL program or interactive SQL when running in the debug mode. The database manager could send any of the following messages when appropriate. These messages provide feedback on how a query was run. In some cases, the messages indicate improvements you can make to help the query run faster.

The messages contain message help that provides information about the cause for the message, object name references, and possible user responses.

The time at which the message is sent does not necessarily indicate when the associated function was performed. Some messages are sent altogether at the start of a query run.

Query performance messages Notes
CPI4321 - Access path built for &18 &19  
CPI4322 - Access path built from keyed file &1  
CPI4323 - The query access plan has been rebuilt  
CPI4324 - Temporary file built for file &1  
CPI4325 - Temporary result file built for query  
CPI4325 - Temporary result file built for query  
CPI4326 - &12 &13 processed in join position &10 This message provides the join position of the specified table when an index is used to access the table data. Join position pertains to the order in which the tables are joined.
CPI4327 - File &12 &13 processed in join position &10  
CPI4328 - Access path of file &3 was used by query  
CPI4329 - Arrival sequence access was used for &12 &13  
CPI432A - Query optimizer timed out for file &1  
CPI432B - Subselects processed as join query  
CPI432C - All access paths were considered for file &1  
CPI432D - Additional access path reason codes were used Because of message length restrictions, some of the reason codes used by messages CPI432A and CPI432C are explained in the message help of CPI432D. Use the message help from this message to interpret the information returned from message CPI432A or CPI432C.
CPI432E - Selection fields mapped to different attributes  
CPI432F - Access path suggestion for file &1  
CPI4330 - &6 tasks used for parallel &10 scan of file &1  
CPI4331 - &6 tasks used for parallel index created over file  
CPI4332 - &1 host variables used in query  
CPI4333 - Hashing algorithm used to process join  
CPI4334 - Query implemented as reusable ODP  
CPI4335 - Optimizer debug messages for hash join step &1 follow  
CPI4336 - Group processing generated  
CPI4337 - Temporary hash table build for hash join step &1  
CPI4338 - &1 Access path(s) used for bitmap processing of file &2  
CPI433A - Unable to retrieve query options file  
CPI433B - Unable to update query options file  
CPI433C - Library &1 not found  
CPI433D - Query options used to build the query access plan  
CPI433E - User-defined function &4 found in library &1  
CPI433F - Multiple join classes used to process join  
CPI4340 - Optimizer debug messages for join class step &1 follow  
CPI4341 - Performing distributed query  
CPI4342 - Performing distributed join for query  
CPI4343 - Optimizer debug messages for distributed query step &1 of &2 follow  
CPI4345 - Temporary distributed result file &3 built for query  
CPI4346 - Optimizer debug messages for query join step &1 of &2 follow  
CPI4347 - Query being processed in multiple steps  
CPI4348 - The ODP associated with the cursor was hard closed  
CPI4349 - Fast past refresh of the host variables values is not possible  
CPI434 - Member &3 was opened with fewer open options than were specified  
CPI434E - Query could not be run using SQE  
CPI4350 - Materialized query tables were considered for optimization  
CPI4351 - Additional reason codes for query access plan has been rebuilt  
CPI436A - Database monitor started for job &1, monitor ID &2