DB2 - Problembeschreibung
Problem IC67661 | Status: Geschlossen |
CLI KEYWORD TRACESTMTONLY=1 CAUSES CLI TRACE TO NOT DISPLAY RETURN CALL TO SQLEXECUTEOLEDB() | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 | |
Problembeschreibung: | |
In a full CLI trace, a call to SQLExecuteOLEDB() should look similar to the following: SQLExecuteOLEDB( hStmt=2:1, ulNumBindings=0, rgpBindings=<NULL pointer>, rgParamInfo=<NULL pointer>, pRowData=<NULL pointer> ) ---> Time elapsed - +2.100000E-005 seconds ( Package="SYSSH200 ", Section=4 ) ( Requested Cursor Attributes=3 ) ( Reply Cursor Attributes=524298 ) ( Actual Cursor Attributes=524299 ) SQLExecuteOLEDB( pColCount=1, pRowsAffected=-1 ) <--- SQL_SUCCESS Time elapsed - +1.448000E-003 seconds When TRACESTMTONLY=1 is set in the CLI configuration only a single call like the following will be displayed SQLExecuteOLEDB( pszSqlStr="SELECT * FROM sysibm.sysdummy1 " ) ---> Time elapsed - 0 seconds This fix will enable displaying the return call to SQLExecuteOLEDB() in the <--- direction to be displayed | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * DB2 LUW v9.1 * **************************************************************** * PROBLEM DESCRIPTION: * * CLI KEYWORD TRACESTMTONLY=1 CAUSES CLI TRACE TO NOT DISPLAY * * RETURN CALL TO SQLEXECUTEOLEDB() * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 LUW v9.1 Fixpack 10 to obtain fix * **************************************************************** | |
Local-Fix: | |
Use TRACESTMTONLY=0 in order to see the return call to SQLExecuteOLEDB() | |
verfügbare FixPacks: | |
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows | |
Lösung | |
First fixed in DB2 LUW v9.1 Fixpack 10 | |
Workaround | |
Use TRACESTMTONLY=0 in order to see the return call to SQLExecuteOLEDB() | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 06.04.2010 16.06.2011 16.06.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.1.FP10 | |
Problem behoben lt. FixList in der Version | |
9.1.0.10 |