A fix is available
APAR status
Closed as program error.
Error description
Table space cluster order is lost during SQL Insert when apar PM75921/UK91122 is applied. The SQL Insert are done so that the table space will maintain cluster order. When finding the candidate page in the index, the code did not correctly check for pseudo deleted rids. Thus a non pseudo deleted rid for a prior page was provided as a candidate page. This incorrect candidate page was full and thus lead to the row being put at the end of the table space and lost of cluster order.
Local fix
Loss of cluster order can lead to DEADLOCK or invalid TIMEOUTS. RC00C90088 and RC00C9008E
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 for z/OS users with segmented * * table spaces (non-UTS) that applied * * APAR PM75921 (PTF UK91122). * **************************************************************** * PROBLEM DESCRIPTION: Cluster order may be compromised for * * segmented table spaces (non-UTS) after * * applying APAR PM75921 (PTF UK91122). * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** After applying APAR PM75921 (PTF UK91122), clustering order for segmented table space (non-UTS) may become compromised, which may lead to deadlocks and timeouts, RC00C90088 and RC00C9008E. While inserting data, the clustering index failed to provide a viable candidate page. Based upon very data dependant factors, a candidate page was returned that was not useable since it was already full. This caused data to be appended to the end of the table space, compromising clustering order.
Problem conclusion
DB2 has been modified so that when the clustering index for a segmented table space (non-UTS) is used to determine the candidate page for insert, it will provide a more viable candidate page.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PM92200
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
A10
Status
CLOSED PER
PE
YesPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2013-07-01
Closed date
2013-09-06
Last modified date
2013-10-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK97362 UK97363
Modules/Macros
DSNKPOSI
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
03 October 2013