DB2 FOR LUW / DB2FORLUW / A10 - DB2

If the package is invalidated, an implicit rebind may be driven 
later when the package is loaded. 
It is possible that a recoverable error happens during the 
compilation phase of the implicit rebind in which case the 
instance 
will trap with segmentation violation.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users running on DB2 for LUW version 10.1 fix pack 2.    * 
* Where operations trigger implicit rebind.                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 version 10.1 fix pack 3 or refer to local fix. * 
****************************************************************

several work arounds: 
1. Pre-emptively prevent the implicit rebind with an explicit 
rebind. 
2. Ensure that the sql compilation will succeed during the 
implicit rebind. For example, do not purposefully attempt an 
implicit rebind knowing that the dependent object to rebind the 
package does not exist. 
 
With the fix, proper SQLCODE will be returned instead.

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
 

This Problem is first fixed in DB2 version 10.1 fix pack 3

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC95352 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

24.05.2013
27.09.2013
27.09.2013