A fix is available
APAR status
Closed as program error.
Error description
ABEND04E rc00C90105 in DSNKINSL:0D44 ( erqual0D44 ) during INSERT causing an index page split . During INSERTing records an INDEX PAGE SPLIT was neccessary. Several key/rids are moved to the newly formatted Index Page. On reordering and adding the records to the page, one key/rid happens to be the last one. However for this record, the final x'18' bytes of it are overwritten with a repeat of d'12' id map entries.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 users using type 2 indexes. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90105 DSNKINSL ERQUAL0D44 * * or * * ABEND04E RC00C90101 DSNKISPL ERQUAL5003 * * or * * less than optimum space utilization * * during INSERT in a data sharing * * environment * **************************************************************** * RECOMMENDATION: * **************************************************************** The DSNKINSL ERQUAL0D44 abend is caused by an incorrect calculation that caused freespace (IPFREESP) to become negative. The calculation occurs during asymmetric index page split. The DSNKISPL ERQUAL5003 abend is an internal inconsistency check. We are trying to split an index page during rollback, but a real split should never occur during rollback. The rollback attempts to re-insert a key that was originally deleted. There was room on the page to rollback the delete, but the space was not in contiguous free space. Split should have reclaimed space and avoided a page split. If multiple applications on different data sharing members, are inserting into the same index locality, the index pages can be split inefficiently causing more pages to be allocated than necessary.
Problem conclusion
Corrected the asymmetric split algorithm to determine the correct number of bytes to put on the old and new pages. Corrected the asymmetric split algorithm to utilize a work area and reclaim space. Corrected the asymmetric split algorithm to split at the optimum location based upon the INSERT pattern. Splitting at the optimum location will utilize space efficiently.
Temporary fix
********* * HIPER * *********
Comments
ž**** PE09/07/22 FIX IN ERROR. SEE APAR PK91830 FOR DESCRIPTION
APAR Information
APAR number
PK62214
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2008-03-06
Closed date
2008-08-28
Last modified date
2009-08-26
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK39357
Modules/Macros
DSNDIP DSNIFOI DSNKDKE2 DSNKDLE DSNKFRMT DSNKINSL DSNKISPL DSNKIXDB DSNKPDGB DSNKREST DSNKRMPD DSNKUNR2 DSNURBT2 DSNURBXA DSN1DIPG
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
R910 PSY UK39357
UP08/09/13 P F809
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":"9.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":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
26 August 2009