PM33635: NO LOAD OR REFRESH AFTER DROP MATERIALIZED QUERY TABLE ( MQT) FFA10 PM47082

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The DB2 Object Comparison Tool for z/OS does not LOAD or REFRESH
  a MATERIALIZED QUERY TABLE effected by a change.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Object Comparison Tool for  *
  *                 z/OS who use Materialized Query Tables       *
  *                 ( MQT ).                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: The DB2 Object Comparison Tool does not *
  *                      include the comparison of columns,      *
  *                      UNLOAD/RELOAD, and the refresh of       *
  *                      materialized query tables.              *
  *                                                              *
  *                      The function regarding MQT objects to   *
  *                      be refreshed when they are built or     *
  *                      rebuilt has been added. Previously, a   *
  *                      MQT object would need to be refreshed   *
  *                      outside of the product. Now, there      *
  *                      will be a SQL REFRESH command that      *
  *                      needs to follow the LOAD.               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The DB2 Object Comparison Tool has been changed to compare the
  columns of MQTs and report differences.  It will UNLOAD the
  records of a user managed MQT and RELOAD the records if the
  new table is a user managed MQT.  If the new table is a system
  managed MQT, the records of the user managed MQT will be
  unloaded only.  The system managed MQT will be refreshed.
  

Problem conclusion

• MQT support has been expanded.
  Note: If a MQT will be refreshed, the CHECK and COPY utilities
  must be selected. If not, a SQLCODEN904 will occur.
  
  The necessary REFRESH statements for new or changed MQT objects
  will now be generated in DB2 Object Compare. The point in the
  apply process where this is done is immediately before the
  RUNSTATS (if RUNSTATS is requested). If JCL is generated, the
  statements are put into their own data set as the ALTER, CREATE
  and DROP statements are currently.  A new template (GOCREFRN)
  under the DB2 Object Compare category will allow users to
  control this data set name.  Also, the RESTART instructions
  will instruct users on how to restart from a failure in this
  new REFRESH step.  If multiple JCL jobs are generated, the
  refresh is contained in a new separate job.  When generating
  JCL to separate jobs, the numbering of the RUNSTATS job has
  been changed to be prefaced T87 instead of T82 and the new
  REFRESH job is prefaced with T85.  For Work Statement Lists
  ( WSL ), the REFRESH statements will immediately precede the
  RUNSTATS (if present).
  

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

•    GOCGAJOB GOCGCMP  GOCRSTR  GOC2CMF  GOC2CMP
  GOC2CMR  GOC2CMS  GOC2CMT
  

Fix information

• Fixed component name

  DB2 OBJECT COMP

• Fixed component ID

  5697G6400

Applicable component levels

• R720 PSY UK71429

     UP11/09/02 P F109

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.