DB2 FOR LUW / DB2FORLUW / 970 - DB2

A very small hole in the serialization between invalidating and 
dropping logic exists which can result an unexpected reference 
of 
 NULL pointer value. 
 
Due to the timing hole DB2 might trap with following stack : 
 
0B95ECF4 6F326CA0 35B99F00 0B95F4B0 0B95EE50 6E3282D4 offset: 
00000090 in 
<__VInfreq_?sqlra_inval_many_vars@@YAHPAUsqlrr_cb@@PAUsqlr_rpc_a 
pm_request@@@Z> <sqlra_dyn_invalid.C:-1> 
0B95ED18 6E350D3C 35B99F00 0B95F4B0 00000000 74696E49 offset: 
0000004E in 
<?sqlra_event_inval_soft.@@YAHPAUsqlrr_cb@@PAUsqlr_rpc_apm_reque 
st@@@Z> <sqlra_events.C:752> 
0B95EE50 6E3282FB 35B99F00 0B95F4B0 00000300 00000000 offset: 
00000213 in 
<?sqlra_execute_event@@YAHPAUsqlrr_cb@@PAUsqlr_rpc_apm_request@@ 
@Z> <sqlra_broadcast_event.C:281> 
0B95EF84 6E32807A 35B99F00 0B95F4B0 0B95F536 2D1D3EA0 offset: 
000000DA in 
<?sqlra_broadcast_request@@YAHPAUsqlrr_cb@@PAUsqlr_rpc_apm_reque 
st@@@Z> <sqlra_broadcast_event.C:158> 
0B95F88C 6E2FC7BC 35B99F00 2D1D3F22 00000012 2D1D3EA0 offset: 
0000041A in <?sqlra_drop_pkg@@YAHPAUsqlrr_cb@@PAEF1F11HH@Z> 
<NotFound:-1> 
0B95F8D8 6D520338 0B95F918 1D48001E 0000800D 00000000 offset: 
000000F4 in <_anonBlockTaskProcessor> <abcTaskProcessors.C:138> 
0B95F950 6D521DC0 2750D110 00000000 00000000 00000000 offset: 
00000122 in 
<?taskProcessorDriver@ABPAgent@@AAEHPAVABPTaskProContext@@@Z> 
<abpAgent.C:287> 
0B95F970 6D521AA3 2750D110 6D820DBA 7B20A400 7B725D60 offset: 
000001B3 in <?main@ABPAgent@@QAEXPAVABPTaskProContext@@@Z> 
<abpAgent.C:764> 
0B95F998 6D5259FE 7B725D60 00000000 6EB45283 001072AB offset: 
00000048 in 
<?abpAgentEntryPoint@@YAXPAVsqeAgent@@PAVABPTaskProContext@@@Z> 
<abpExternals.C:915> 
0B95FA50 6D838295 7B725D60 00000000 0B95FA70 7B72B634 offset: 
000002C9 in <?sqleIndCoordProcessRequest@@YAXPAVsqeAgent@@@Z> 
<sqleicgt.C:547> 
0B95FCD4 6D7DA3DA 6CD0DB00 00000000 00064DC0 35EC67A0 offset: 
00000092 in <?RunEDU@sqeAgent@@EAEXXZ> <sqle_agent.C:4442> 
... 
...

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* This is an issue in one of  the DB2's  internal  logic       * 
* which  missed  serialization  and due to that it  caused the * 
* issue as described in the Error Description section          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 7 or higher to avoid     * 
* experiencing this issue.                                     * 
****************************************************************

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
 

First fixed in DB2 Version 9.7 Fix Pack 7

not known / see Local fix

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

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

15.06.2012
13.11.2012
13.11.2012

9.7.FP7