PH32375: INSERT ROW FAILS WITH SQLCODE161 AFTER PH27335/UI71890 HAS BEEN APPLIED 21/01/28 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• INSERT row attempts into an object view now fail with :
  
  DSNT408I SQLCODE = -161, ERROR:  THE INSERT OR UPDATE IS NOT
  ALLOWED BECAUSE A RESULTING ROW DOES NOT SATISFY THE VIEW
  DEFINITION
  
  once PH27335/UI71890 has been applied. Only views that have the
  WITH CHECK OPTION clause, referring to a specific table are
  affected.
  

Local fix

• REORG the tablespace involved
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Db2 12 for z/OS users who use direct                     *
  * row access path, to access a row in a table                  *
  * that is in a segmented tablespace and have                   *
  * applied PH27335/UI71890.                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The application received an incorrect                        *
  * SQLCODE161 when inserting a row over a                       *
  * view with the check option and                               *
  * PH27335/UI71890 was previously applied                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply corrective PTF when available                          *
  ****************************************************************
  After PH27335/UI71890 is applied, when all the following
  conditions are met, the application may get an incorrect
  SQLCODE-161:
  1.When an application executes a SQL statement/query going
  through the direct row access path. This SQL statement/query
  could be a select statement using RID built-in function or an
  insert or a merge statement that involves the symmetric view
  validation.
  2.The table is in a segmented tablespace.
  3.There is another data sharing member who happened to perform
  an insert operation, which caused the segment number of the
  last segment change and this change hasn't been written into
  DASD yet. The current data sharing member may pick up an
  out-dated segmented TS limit.
  PH27335/UI71890 added checking to return the correct result for
  a DELETE or a SELECT statement that used a specific RID after
  a mass delete or truncate table. However, the symmetric view
  validation case should be excluded from this checking because
  there is no need to recheck the page's legitimacy after an
  insert operation.
  

Problem conclusion

• Db2 has been fixed to perform the necessary checking correctly,
  and return the correct result when inserting a row over a view.
  

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:

  UI73320

Modules/Macros

• DSNIADR
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RC10 PSY UI73320

     UP21/01/08 P F101 {

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.