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

DRDA HAS EXTRA SQLCARD WITH DB2_DEFERRED_PREPARE_SEMANTICS=YES

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 10.1 fixpack 2.                   * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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 first fixed in DB2 UDB Version 10.1 FixPack 2
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
04.11.2012
31.12.2012
31.12.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.2 FixList
10.5.0.2 FixList