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

SQL_INVALID_HANDLE RETURNED WHEN USING DBMS_SQL MODULE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
SQL_INVALID_HANDLE returned when using DBMS_SQL module 
repeatadly. 
This error can be cleared with Instance recycle. 
 
If the application does a loop like: 
 
LOOP 
        DBMS_SQL.OPEN_CURSOR 
        ........................ 
        DBMS_SQL.CLOSE_CURSOR 
END LOOP 
 
It should be changed to keep one cursor opened until the end, 
 
and all cursors should be closed before exit. 
 
 
This applies to error scenarios when exception is thrown, the 
example of the flow is: 
 
DBMS_SQL.OPEN_CURSOR ( <any cursor: let's call is c1> ) 
LOOP 
        DBMS_SQL.OPEN_CURSOR 
        ........................ 
        DBMS_SQL.CLOSE_CURSOR 
END LOOP 
DBMS_SQL.CLOSE_CURSOR (c1)
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* db2 luw                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* SQL_INVALID_HANDLE returned when using DBMS_SQL module       * 
* repeatadly.                                                  * 
* This error can be cleared with Instance recycle.             * 
*                                                              * 
* If the application does a loop like:                         * 
*                                                              * 
* LOOP                                                         * 
*         DBMS_SQL.OPEN_CURSOR                                 * 
*         ........................                             * 
*         DBMS_SQL.CLOSE_CURSOR                                * 
* END LOOP                                                     * 
*                                                              * 
* It should be changed to keep one cursor opened until the     * 
* end,                                                         * 
*                                                              * 
* and all cursors should be closed before exit.                * 
*                                                              * 
*                                                              * 
* This applies to error scenarios when exception is thrown,    * 
* the                                                          * 
* example of the flow is:                                      * 
*                                                              * 
* DBMS_SQL.OPEN_CURSOR ( <any cursor: let's call is c1> )      * 
* LOOP                                                         * 
*         DBMS_SQL.OPEN_CURSOR                                 * 
*         ........................                             * 
*         DBMS_SQL.CLOSE_CURSOR                                * 
* END LOOP                                                     * 
* DBMS_SQL.CLOSE_CURSOR (c1)                                   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* apply fp5                                                    * 
****************************************************************
Local Fix:
available fix packs:
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
fixed in fp5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
18.04.2011
06.02.2012
06.02.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList