home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT01737 Status: Geschlossen

DB2BATCH CHANGED THE HEADER OUTPUT

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
The issue is described below: 
 
1- DB2BATCH output on  previous DB2 version  in this case "DB2 
v9.7.0.3" 
 
select distinct trim(col1) from t1 fetch first 10 rows only ; 
 
1 
------------------------------ 
0 
0000512 
001 
00103 
00105 
00107 
00108 
00112 
00113 
00118 
 
2-DB2BATCH output  on "DB2 v9.7.0.8" 
 
select distinct trim(col1) from t1 fetch first 10 rows only ; 
 
1 
---------------------------------------------------------------- 
-------------------------------------------------------- 
0 
0000512 
001 
00103 
00105 
00107 
00108 
00112 
00113 
00118 
 
4- If the SELECT is executed on CLP the header output is the 
same on both FPs 
 
- FP3 
$ db2 "select distinct trim(col1) from t1 fetch first 10 rows 
only" 
 
1 
------------------------------ 
0 
0000512 
001 
00103 
00105 
00107 
00108 
00112 
00113 
00118 
 
 
- FP8 
 
db2 "select distinct trim(col1) from t1 fetch first 10 rows 
only" 
 
1 
------------------------------ 
0 
0000512 
001 
00103 
00105 
00107 
00108 
00112 
00113 
00118 
 
In this example the db2batch header size is 30 on v9.7fp3 and on 
v9.7fp8 is 120. On CLP the header size is 30 on both version.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all db2batch users                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2_v101fp5 or later releases.                    * 
****************************************************************
Local-Fix:
As workaround you can use the option "-w" in the db2batch 
command. This option specifies 
the maximum column width of the result set.
Lösung
This problem is fixed in DB2 V10.1 FP5. After fix, db2batch will 
display correct result.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
12.05.2014
13.07.2015
13.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList