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

NLS_STRING_UNITS SESSION VARIABLE NOT FUNCTIONAL IN DPF MODE

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
When connected to a database from any node other than the 
catalog node, the NLS_STRING_UNITS session variable is not 
functional.  Assignments can be made to the session variable, 
but the current value of the session variable has no impact on 
the default string units of the user environment. 
 
For example, when NLS_STRING_UNITS is set to 'CODEUNITS32' the 
default string units when defining a character string should be 
CODEUNITS32.  The CREATE TABLE statement in the scenario below 
demonstrates that CODEUNITS32 is not the default. 
 
SET NLS_STRING_UNITS='CODEUNITS32' 
DB20000I  The SQL command completed successfully. 
 
CREATE TABLE T1 (C1 VARCHAR(10)) 
DB20000I  The SQL command completed successfully. 
 
select colname, typename, typestringunits, stringunitslength, 
length from syscat.columns where tabname = 'T1' 
 
COLNAME              TYPENAME             TYPESTRINGUNITS 
STRINGUNITSLENGTH LENGTH 
--------------------       -------------------- 
---------------              ----------------- 
----------- 
C1                             VARCHAR              OCTETS 
10                           10 
 
   1 record(s) selected. 
 
The column C1 should have the data type VARCHAR(10 CODEUNITS32), 
which means the TYPESTRINGUNITS should be 'CODEUNITS32', the 
STRINGUNITSLENGTH should remain as 10, and the LENGTH should be 
40.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users in a DPF environment                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.5 Fix Pack 7.                          * 
****************************************************************
Local Fix:
As a workaround, the user can manually provide the CODEUNITS32 
keyword when CODEUNITS32 string units are required.  For 
example, when creating a table: 
 
CREATE TABLE T1 (C1 VARCHAR(10 CODEUNITS32))
Solution
First fixed in Version 10.5 Fix Pack 7.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.03.2015
26.01.2016
28.04.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList