DB2 - Problembeschreibung
Problem IC87882 | Status: Geschlossen |
TOTAL ELAPSED TIME IN THE DB2BATCH OUTPUT FOR THE SAME STATEMENT EXECUTED MORE THAN ONCE WITHIN DB2BATCH MAY NOT BE ACCURATE. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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. | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows | |
Lösung | |
Fixed in V10 Fixpack 2 and above. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 04.11.2012 29.01.2013 29.01.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.2 | |
10.5.0.2 |