DB2 FOR LUW / DB2FORLUW / 970 - DB2

DB2 may spend a considerable amount of time compiling queries 
when the application or queries have REOPT ONCE set. 
 
If you have REOPT ONCE enabled and notice that compile time is a 
significant component of the execution time of a statement then 
this APAR may be applicable to your environment. REOPT ONCE may 
be enabled using any of the following methods: 
- the REOPT ONCE keyword to the BIND or REBIND commands 
- setting the CLI/ODBC configuration keyword SQL_ATTR_REOPT to 
SQL_REOPT_ONCE 
- the <REOPT VALUE='ONCE'/> component of an optimization profile 
 
You can use db2batch, the dynamic SQL snapshot monitor, or some 
other tool to measure the performance of compiling and executing 
your REOPT ONCE queries to determine whether the compile time of 
REOPT ONCE is significant portion of your performance.

Users affected: All

Turning off REOPT ONCE will reduce the query compilation cost 
for the affected statements but may also lead to poor plan 
choices.

DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem was first fixed in Version 9.7 Fix Pack 1

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

08.07.2009
15.12.2009
15.12.2009

9.7.FP1