DB2 FOR LUW / DB2FORLUW / 970 - DB2

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.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 9.7 fix pack 7.                   * 
****************************************************************

DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem was first fixed in DB2 UDB Version 9.7 Fix Pack 7.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC87843 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

16.04.2012
05.11.2012
05.11.2012

9.7.FP7