home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC80588 Status: Geschlossen

CLPPLUS RETURNED JAVA.IO.CHARCONVERSIONEXCEPTION, IF DATABASE CODE PAGE IS
NOT SAME AS LANG ENVIRONMENT VARIABLE.

Produkt:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problembeschreibung:
clpplus may return a java.io.CharConversionException, if 
the database code page is not same as the code page 
implied by the setting of the LANG environment variable 
at the time that DB2 is started. 
 
In the following example, the database is created with 
code page 1208; however, the DB2 server locale of 
Ja_JP implies a Shift JIS code page, not Unicode.  DB2 
formats the value of SQLERRM using Shift JIS, resulting 
in a code page conversion error. 
 
export LANG=Ja_JP 
db2set DB2_COMPATIBILITY_VECTOR=ORA 
db2set DB2COMM=TCPIP 
db2 update dbm cfg using svcename db2test 
db2start 
db2 create db testdb using codeset UTF-8 territory JP 
 
Execute the following pl/sql. 
 
create table TEST ( id NUMBER, name VARCHAR2(10)); 
set serveroutput on; 
DECLARE 
  v_rec test%ROWTYPE; 
BEGIN 
      select * into v_rec from test where id = 100; 
EXCEPTION 
  WHEN Others THEN 
    DBMS_OUTPUT.PUT_LINE('SQLERRM:'||SQLERRM); 
END; 
/ 
drop table TEST; 
quit; 
 
clpplus -nw userid/password@HOSTNAME:PORTNUMBER/DATABASE 
@test.sql 
 
You will see a DB250505E error.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 9.1 fixpack 12.                   * 
****************************************************************
Local-Fix:
Lösung
Problem was first fixed in DB2 UDB Version 9.1 Fix Pack 12.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
25.12.2011
02.08.2012
02.08.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.1.FP12
Problem behoben lt. FixList in der Version
9.1.0.12 FixList