PH70559: ENHANCED LOB INDEX VALIDATION TO CHECK FOR AUXILIARY TABLE EXISTENCE BEFORE ADDING TO INSTANCE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When adding a LOB index using the saveForLater feature, the
  system did not validate whether the required pre-conditions were
  satisfied. The base table must be updated in advance to include
  the new LOB column and the explicit auxiliary table DDL (CREATE
  AUXILIARY TABLE statement). This fix adds a validation check to
  verify the auxiliary table exists in the base table definition.
  If the pre-condition is not met, a descriptive error message is
  returned guiding users to use the Apply All option instead.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the IBM Unified Management Server   *
  *                 for z/OS and the following experiences:      *
  *                 - Db2 Devops Experience for z/OS             *
  ****************************************************************
  * PROBLEM DESCRIPTION: Discrepancy in HomeApplicationID        *
  *                      assignment. When creating an            *
  *                      explicitly defined LOB index via the    *
  *                      API, the requested homeApplicationID    *
  *                      is correctly specified in the request   *
  *                      and reflected in the API response.      *
  *                      However, the actual homeApplicationID   *
  *                      assigned in the instance YAML file      *
  *                      differs                                 *
  *                      , indicating a mismatch                 *
  ****************************************************************
  Discrepancy in HomeApplicationID assignment. When creating an
  explicitly defined LOB index via the API, the requested
  homeApplicationID is correctly specified in the request and
  reflected in the API response. However, the actual
  homeApplicationID assigned in the instance YAML file differs
  , indicating a mismatch
  

Problem conclusion

• Apply the PTF provided by this APAR
  

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:

Modules/Macros

• IZPDB2SD IZPDISCP IZPHLOSD IZPIMSSD IZPMNFST IZPSERVE IZPSYSSD
  IZPUI
  

Fix information

• Fixed component name

  UNIFIED MGMT SV

• Fixed component ID

  5698UM100

Applicable component levels

• R120 PSY UO07245

     UP26/04/09 P F604

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.