DB2 FOR LUW / DB2FORLUW / 970 - DB2

A segmentation fault trap can be generated in 
sqlra_unconcentrate_statement() function call when a statement 
with literals was previously concentrated in the dynamic SQL 
cache. 
 
  Statement concentrate function can be dynamically enabled by 
the following a database configuration paramenter or other 
statement attributes like JDBC driver property ; 
 
      DB CFG parameter STMT_CONC = LITERALS 
      JDBC property statementConcentrator = 
DB2BaseDataSource.STATEMENT_CONCENTRATOR_WITH_LITERALS 
 
  If statement concentrator is now disabled (either for the 
database or the statement) and this same statement (with the 
same literal values) is now issued concurrently by 2 (or more 
connections), then the segmentation fault can occur in one of 
the DB2 agents. 
 
  The following is a sample stack trace on this issue. 
 
      sqlra_unconcentrate_statement 
      sqlra_get_var 
      sqlrr_execute_immediate 
      sqlrr_execimmd 
      sqljs_ddm_excsqlimm

**************************************************************** 
* USERS AFFECTED:                                              * 
* statement concentrator user                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* SIGSEGV comes up in sqlra_unconcentrate_statement() when the * 
* corresponding statements are simultaneously unconcentrated   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2 Version 9.7 FixPak 4                          * 
****************************************************************

- Disable statement concentrator, recycle database, and do not 
use statement concentrator. 
  or 
  - Do not disable statement concentrator with an active 
database when it has been enabled, if there is a possibility of 
the same statement being issued from multiple connections 
concurrently.

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
 

Problem was the first fixed in Version 9.7 FixPak 4

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC73635 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

06.10.2010
12.05.2011
12.05.2011

9.7.