|
Problem IC68898
|
Status: Closed |
Running runstats immediately after connecting to a database might lead to segmentation faults. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
If RUNSTATS is executed immediately after connecting to a
database, subsequent operations may trap with a segmentation
fault. The subsequent operation can be any operation, including
another RUNSTATS. For the problem to occur, the RUNSTATS
operation must be on a table without any indexes. It does not
matter if the runstats command specified an INDEX clause or not.
Sample callstacks that can experience the problem:
sqlr_audit
sqlr_audit_context
sqlrrcom_dps
sqlrrcom
sqlrr_commit
and
sqlr_audit
sqlr_audit_checking
sqlrr_check_auth
sqlrrsta
sqlrr_runstats_DA |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 LUW on all supported platforms. *
****************************************************************
* PROBLEM DESCRIPTION: *
* WITH ACTIVE DATABASE LEVEL AUDIT, PERFORMING RUNSTATS *
* RIGHTAFTER DATABASE BECOMES ACTIVE MAY TRAP. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 LUW Version 9.7 Fix Pack 3 *
**************************************************************** |
| Local Fix: |
Execute any SQL statement (e.g. "values 1") before running
RUNSTATS. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 first fixed in Version 9.7 Fix Pack 3 |
| Workaround |
The problem will not occur if:
(1) the table has at least one index,
or
(2) after CONNECT to database, if any SQL statement (e.g.
VALUES(1))
has been executed before the RUNSTATS command. |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC69478
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.05.2010
12.10.2010
16.11.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
