|
Problem IC87882
|
Status: Closed |
TOTAL ELAPSED TIME IN THE DB2BATCH OUTPUT FOR THE SAME STATEMENT EXECUTED MORE THAN ONCE WITHIN DB2BATCH MAY NOT BE ACCURATE. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
For a query executed multiple times via db2batch , the elapsed
time for 2nd run and so on, does not reflect proper total
elapsed time
for the query.
For example:
Input file for db2batch contains the following queries:
Query1: select * from t1 where r1=1
Query2: select * from t1 where r1=1
Query3: select * from t1 where r1=1
............... |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All using db2batch and monitoring the performance of the *
* same statement multiple times within the same batch file. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to fixpack 2 or above. *
**************************************************************** |
| Local Fix: |
You could use dynamic sql snapshot to get the execution
execution time and divide that by the # of executions to get an
average execution time per execution. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Fixed in V10 Fixpack 2 and above. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.11.2012
29.01.2013
29.01.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
