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 IC67880 Status: Closed

USING COMMAND EDITOR TO EXPORT DATA OF DECIMAL TYPE TO A FILE MIGHT
CREATE INCORRECT OUTPUT.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Using Command Editor to export data of DECIMAL type to a file 
creates incorrect output if the thousands separator for numeric 
fields on the client is the apostrophe ("'") character. 
 
Here is how to reproduce the problem on Windows XP. 
 
1) 
In your database create a table like this: 
 
 create table tab1(col1 decimal(4)); 
 insert into tab1 values (1234); 
 
2) 
In Control Panel, go to Regional and Language Options, select 
the Regional Options tab, and select from the drop down list box 
a setting for which the thousands separator is an apostrophe, 
such as "Italian (Switzerland)" . 
Then click the "OK" button to apply the change. 
 
3) 
Start Command Editor, connect to the database and run this SQL 
statement: 
 
 select * from tab1; 
 
The result appears as: 
 
 1'234 
 
with an apostrophe as the thousands delimiter. 
 
4) 
Select the menu option: 
 
 Selected -> Export... 
 
select the directory and file name to which to save the file, 
and click OK. 
After that the file contains: 
 
+1 
 
which is incorrect. 
 
 
If you do the same actions but having set Regional Options to a 
setting for which the thousands delimiter is a comma (","), such 
as "English (United Kingdom)", then the result of the query 
appears as: 
 
 1,234 
 
with a comma as the thousands delimiter, and after the export 
the resulting file contains 
 
+1234 
 
which is correct.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of Command Editor with DB2 for Linux, UNIX and Windows * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* .                                                            * 
****************************************************************
Local Fix:
As a possible workaround, you can do either of the following: 
 
1) Before doing the export, set the Regional Options to a 
setting for which the thousands delimiter is not the apostrophe 
character. Then after doing the export you can set Regional 
Options back. 
 
2) Instead of using Command Editor, run the EXPORT command using 
CLP (Command Line Processor).
available fix packs:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in Version 9.7 Fix Pack 3
Workaround
As a possible workaround, you can do either of the following: 
 
 
1) Before doing the export, set the Regional Options to a 
 
setting for which the thousands delimiter is not the apostrophe 
character. Then after doing the export you can set Regional 
Options back. 
 
2) Instead of using Command Editor, run the EXPORT command 
 
using 
CLP (Command Line Processor).
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC67994 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.04.2010
27.01.2011
27.01.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList