Fixes are available
APAR status
Closed as program error.
Error description
If the index is a clustering index, when we insert a row, there are the following steps involved: 1. We will perform a scan on the clustering index and try to cluster the row using the clustering index. 2. Once the row is inserted properly, we need to insert the key into index(es). When we insert the key into the clustering index, we will first try to avoid the index probe and try to insert the key directly onto the last index page we read during step 1. 3. We need to lock the next key during the insert, and if the next key is already locked in a mode that's not compatible with the insert, then we will attempt to reprobe from the root again. If the row lock is still not released during the reprobe, the insert will fail with a lock time out error. For the above scenario, DB2 waits as twice as locktimeout value.
Local fix
Not available
Problem summary
Users affected: All Problem Description: As same as Error description. Problem Summary: As same as APAR abstract.
Problem conclusion
Problem was first fixed in Version 9.1 Fix Pack 8 (s090823).
Temporary fix
Comments
APAR Information
APAR number
IZ43462
Reported component name
DB2 UDB WSE SOL
Reported component ID
5765F3502
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-02-08
Closed date
2009-10-04
Last modified date
2009-10-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DB2 UDB WSE SOL
Fixed component ID
5765F3502
Applicable component levels
R810 PSN
UP
R820 PSN
UP
R910 PSN
UP
R950 PSN
UP
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910"}]
Document Information
Modified date:
03 October 2021