|
Problem IC84684
|
Status: Closed |
JDBC WRAPPER MAY RETURN SQL1822N WHEN A CONSTRAINT VIOLATION OCCURS. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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 Summary: |
User affected:
Users of JDBC wrappers in InfoSphere Federation Server
Problem description and summay:
See error description |
| 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 |
Problem was fistly fixed in Version 10, FixPak 1. This
fix should be applied on the federation Server. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 19.06.2012
01.11.2012
01.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
|
 |
| 10.5.0.1
|
|
