|
Problem IC71723
|
Status: Closed |
SIGSEGV IN SQLRA_UNCONCENTRATE_STATEMENT() WHEN STATEMENT CONCEN TRATOR IS DISABLED AND STATEMENT IS ISSUED IN 2 CONNECTIONS |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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 |
| Problem Summary: |
****************************************************************
* 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 *
**************************************************************** |
| Local Fix: |
- 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. |
| available fix packs: |
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
|
| Solution |
Problem was the first fixed in Version 9.7 FixPak 4 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC73635
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.10.2010
12.05.2011
12.05.2011 |
| 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.4
|
 |
