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 IC62094 Status: Closed

SQL0508N ERROR ON SQLSETPOS() AFTER COMMIT WHEN USING
SQL_CONCUR_LOCK WITH PATCH2=73

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When a commit occurs, cursors with hold become unpositioned. 
If this occurs, a fetch must be done again before issuing a 
positional update. 
 
In a CLI application, when PATCH2=73 is set and SQL_CONCUR_LOCK 
is being used, SQLSetPos() will encounter a SQL0508N error 
after a commit.  This is because a fetch is not currently being 
driven by the CLI layer to reposition the cursor before the 
positinal update.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW v9.7 CLI based applications                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When a commit occurs, cursors with hold become unpositioned. * 
*                                                              * 
* If this occurs, a fetch must be done again before issuing a  * 
*                                                              * 
* positional update.                                           * 
*                                                              * 
*                                                              * 
*                                                              * 
* In a CLI application, when PATCH2=73 is set and              * 
* SQL_CONCUR_LOCK                                              * 
* is being used, SQLSetPos() will encounter a SQL0508N error   * 
*                                                              * 
* after a commit.  This is because a fetch is not currently    * 
* being                                                        * 
* driven by the CLI layer to reposition the cursor before the  * 
*                                                              * 
* positinal update.                                            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW v9.7 Fixpak 1                             * 
****************************************************************
Local Fix:
Avoid issuing a commit before calling SQLSetPos()
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Solution
First Fixed in DB2 LUW v9.7 Fixpak 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.07.2009
09.02.2010
09.02.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.1 FixList