|
Problem IC83691
|
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 / 950 - 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 Users using db2batch to monitor multiple instances of *
* the same statement *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* 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. *
**************************************************************** |
| 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. |
| Solution |
Problem fixed in V95 Fixpack 10 and above. |
| Workaround |
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. |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC83894 IC87882
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.05.2012
28.08.2012
28.08.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP10
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.10
|
 |
