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 IC84684 Status: Geschlossen

JDBC WRAPPER MAY RETURN SQL1822N WHEN A CONSTRAINT VIOLATION OCCURS.

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
JDBC wrapper can't be able to map constraint violation errors to 
DB2 errors. Users may receive SQL1822N other than detailed DB2 
error when a constraint violation occurs. 
 
For example: 
SELECT * FROM a_jdbc_nickname 
 
c1     c2 
------ ----------- 
     1           1 
     2           2 
 
  2 record(s) selected. 
 
INSERT INTO a_jdbc_nickname values(3, 2) 
DB21034E  The command was processed as an SQL statement because 
it was not a valid Command Line Processor command.  During SQL 
processing it returned: 
SQL1822N  Unexpected error code "23505" received from data 
source "<your_jdbc_server>". Associated text and tokens are 
"ERROR:duplicate key value violates unique cons". 
SQLSTATE=560BD
Problem-Zusammenfassung:
User affected: 
  Users of JDBC wrappers in InfoSphere Federation Server 
Problem description and summay: 
  See error description
Local-Fix:
verfügbare FixPacks:
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

Lösung
Problem was fistly fixed in Version 10, FixPak 1. This 
fix should be applied on the federation Server.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
19.06.2012
01.11.2012
01.11.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.1 FixList
10.5.0.1 FixList