PI64508: RECORDS ARE NOT INSERTED TO THE END OF APPEND YES TABLESPACE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Customer has an APPEND YES tablespace defined. Records could
  be inserted to previous pages rather than the end of the table
  space, if meeting any one of the below conditions :
  1. Multiple records are inserted via one insert statement.
  eg. INSERT INTO TABLE(COL) VALUES('XX') FOR N ROWS
  Or
  2. Multiple records are inserted via multiple insert statements
  without commit.
  eg. INSERT STATEMENT LOOP 2000 times without COMMIT
  

Local fix

• Commit more frequently.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 for z/OS user of classic             *
  *                 segmented or Universal table space (UTS)     *
  *                 using APPEND function                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Records are not inserted to the end of  *
  *                      page sets when table is created with    *
  *                      APPEND function.                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When multiple records are inserted via one SQL INSERT statement
  or in a loop, DB2 may optimize the performance by
  utilizing the previous inserted page as the candidate page.
  When the initial candidate page can not hold the new record
  then space search algorithm continues to find available free
  space instead of following APPEND schematic to insert the
  record to the end of page set.  As a result, record is
  inserted to the previous free space.
  

Problem conclusion

• DB2 code is modified to follow APPEND schematic by inserting
  row to the end of page set when the last inserted page
  does not have room for the record within the same insert
  transaction.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UI41880 UI41881

Modules/Macros

• DSNISGPI DSNISUPI
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UI41880

     UP16/11/10 P F611

• RB10 PSY UI41881

     UP16/11/10 P F611

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.