|
Problem IT34111
|
Status: Closed |
INSERTS MAY INTERMITTENTLY RETURN SQL0289N WHILE TABLE SPACE EXTENT MOVEMENT IS IN-PROGRESS
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
Error Description
=================
There are a number of concurrency issues when running extent
movement (ALTER TABLESPACE ? [REDUCE MAX|LOWER HIGH WATER MARK])
while doing a large number of inserts. This can result inserts
intermittently failing with SQL0289N. This APAR addresses a
number of issues including:
* Extent mover using wrong order of operations for getting the
extent movement lock and setting the SQLB_MOVE_IN_PROGRESS
(0x80000) table space state.
* Extent mover not releasing the extent movement lock between
batches of extents.
* Extent mover mishandling SQLP_LTIMEOUT_STMT_RB while
requesting the extent movement lock.
* Inserts not allowed to extend table space while
SQLB_EM_STARTED table space state is set.
* Inserts not waiting long enough for locks to extent table
space while extent movement is running. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.1.4.6 or higher *
**************************************************************** |
| Local Fix: |
Do not run extent movement while inserting a significant amount
of data. |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.1.4.6 or higher *
**************************************************************** |
| Comment |
Upgrade to Db2 11.1.4.6 or higher |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.09.2020
31.03.2021
31.03.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
