|
Problem IC89412
|
Status: Closed |
READ STABILITY ISOLATION IS NOT ENFORCED UNDER CERTAIN SQL ACCESS PLANS |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
In SQL access plans where a table is accessed at least twice,
the DB2 server might not retain locks required to preserve read
stability during the entire SQL execution. Locks might be
released for rows that satisfy matching criteria on the first
access, and requested and held later only as the rows are
retrieved by the application.
Symptoms might include lost updates, duplicate row retrievals
across applications, and inconsistent results within a
transaction. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 9.7.0.8. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 |
The problem if first fixed in DB2 version 9.7.0.8. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC89415 IC89416 IC89934
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.01.2013
25.03.2013
26.03.2013 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.0.8
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.8
|
 |
