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

"DB2FODC -PERF FULL" ON WINDOWS WITH A NON-ENGLISH LANGUAGE
ENVIRONMENT MAY FAIL TO COLLECT SNAPSHOT DATA

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Diagnostic data collection with 'db2fodc -perf full' on Windows 
OS may fail to collect snapshot data. 
 
You will notice errors in the snapshot output file like, 
dbsnap.<dbname>.<iteration>.<timestamp>: 
 
get monitor switches ,72.out 
SQL0104N  An unexpected token "," was found following 
"SWITCHES".  Expected 
tokens may include:  "GLOBAL".  SQLSTATE=42601 
 
get snapshot for all on SAMPLE ,72.out 
SQL0104N  An unexpected token "," was found following 
"<identifier>". 
Expected tokens may include:  "GLOBAL".  SQLSTATE=42601 
 
This happens only on Windows platform when the regional settings 
are set to a non-english locale for which the TIME decimal 
delimiter for the sub seconds is set to a comma "," instead of a 
decimal point ".", for example on German environment. 
 
You can check your reginal settings from Windows (start -> 
control panel -> Reginal and Language Options -> Customize -> 
Decimal Symbol) 
 
You can also verify if you are affected, by running "echo 
%TIME%", in a command windows: 
 
C:\SQLLIB95\BIN>echo %TIME% 
10:38:15,42
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL USERS ON WINDOWS PLATFORM                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See problem description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1.                      * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
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
First fixed in DB2 Version 10.1 Fix Pack 1.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.06.2012
02.11.2012
02.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList