|
Problem IT01737
|
Status: Closed |
DB2BATCH CHANGED THE HEADER OUTPUT |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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. |
| Solution |
This problem is fixed in DB2 V10.1 FP5. After fix, db2batch will
display correct result. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.05.2014
13.07.2015
13.07.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
