| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IC87843 | Status: Closed |
DRDA HAS EXTRA SQLCARD WITH DB2_DEFERRED_PREPARE_SEMANTICS=YES | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
A delete statement in java returned 3 sqlca messages.
Here is a snippet of java program.
System.out.println("executeUpdate() = " +
stmt.executeUpdate());
sqlwarn = stmt.getWarnings();
while (sqlwarn != null) {
System.out.println("Warning description:
" + sqlwarn.getMessage());
sqlwarn = sqlwarn.getNextWarning();
}
$ db2set
DB2_DEFERRED_PREPARE_SEMANTICS=YES
DB2COMM=TCPIP
$ ~/sqllib/java/jdk64/bin/java delete
jdbc:db2://192.168.1.161:60000/sample db2inst1 db2inst1
executeUpdate() = 0
Warning description: DB2 SQL Warning: SQLCODE=0, SQLSTATE=01504,
SQLERRMC=null, DRIVER=4.12.55
Warning description: DB2 SQL Warning: SQLCODE=0, SQLSTATE=01504,
SQLERRMC=null, DRIVER=4.12.55
Warning description: DB2 SQL Warning: SQLCODE=100,
SQLSTATE=02000, SQLERRMC=null, DRIVER=4.12.55
If unset DB2_DEFERRED_PREPARE_SEMANTICS, sqlca messages return 2
entries.
2 entries are expected behavior.
$ db2set
DB2COMM=TCPIP
$ ~/sqllib/java/jdk64/bin/java delete
jdbc:db2://192.168.1.161:60000/sample db2inst1 db2inst1
executeUpdate() = 0
Warning description: DB2 SQL Warning: SQLCODE=0, SQLSTATE=01504,
SQLERRMC=null, DRIVER=4.12.55
Warning description: DB2 SQL Warning: SQLCODE=100,
SQLSTATE=02000, SQLERRMC=null, DRIVER=4.12.55
DRDA has extra SQLCARD with DB2_DEFERRED_PREPARE_SEMANTICS=YES
Therefore getNextWarning() get extra SQLCARD.
This is not JCC issue, DB2 engine issue. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 UDB version 10.1 fixpack 2. * **************************************************************** | |
| Local Fix: | |
| available fix packs: | |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows | |
| Solution | |
Problem was first fixed in DB2 UDB Version 10.1 FixPack 2 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.11.2012 31.12.2012 31.12.2012 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.2 |
|
| 10.5.0.2 |
|