home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC87922 Status: Closed

CORRUPTED TEXT IN THE OUTPUT FILE GENERATED BY 'DB2' CLP COMMAND
WHEN BOTH (-L AND -Z) OPTIONS POINT TO THE SAME FILE.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
If '-l' (Log commands in history file) and '-z' (Save all output 
to output file) options are used with 'db2' CLP command and both 
options point to the same file then text recorded in the output 
file gets corrupted. 
 
Example: 
 
$ db2 -z out.txt -l out.txt list command options 
 
Content of the out.txt file is: 
---------- 
  Command Line Processor Option Settin05/23/2012 04:06:52 
DB20000I The LIST COMMAND OPTIONS command completed 
successfully. 
 ect to backend (DB2BQTRY) = 60 
 Request queue wait time (seconds) (DB2RQTIME) = 5 
---------- 
 
Correct content should be: 
 
---------- 
06/19/2012 04:09:34 list command options 
06/19/2012 04:09:34 DB20000I  The LIST COMMAND OPTIONS command 
completed successfully. 
 
 
      Command Line Processor Option Settings 
 
 Backend process wait time (seconds)        (DB2BQTIME) = 1 
 No. of retries to connect to backend        (DB2BQTRY) = 60 
 Request queue wait time (seconds)          (DB2RQTIME) = 5 
----------
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 2.                      * 
****************************************************************
Local Fix:
Use different file names with -l and -z options. Also, as a 
work-around, you could use this command on LU platform to get 
similar output: db2 -tvf t.sql | tee out.txt
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
Problem was first fixed in DB2 Version 10.1 Fix Pack 2.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.11.2012
18.01.2013
18.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 FixList
10.5.0.2 FixList