home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC67480 Status: Closed

CLI KEYWORD TRACESTMTONLY=1 CAUSES CLI TRACE TO NOT DISPLAY RETURN CALL
TO SQLEXECUTEOLEDB()

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
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 Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW v9.7                                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* CLI KEYWORD TRACESTMTONLY=1 CAUSES CLI TRACE TO NOT          * 
* DISPLAYRETURN CALL TO SQLEXECUTEOLEDB()                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW v9.7 Fixpak 3                             * 
****************************************************************
Local Fix:
Use TRACESTMTONLY=0 in order to see the return call to 
SQLExecuteOLEDB()
available fix packs:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
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

Solution
First fixed in DB2 LUW v9.7 Fixpak 3
Workaround
Use TRACESTMTONLY=0 in order to see the return call to 
SQLExecuteOLEDB()
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.03.2010
27.09.2010
27.09.2010
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList