PK71059: DB2 OBJECT COMPARE ALLOW USER TO CHANGE ENCODING SCHEME.

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• DB2 OBJECT COMPARE ALLOW USER TO CHANGE THE ENCODING
  SCHEME.
  

Local fix

• APPLY PTF
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users  of  Change  Management and            *
  *                 Object Compare Ver 7.2 who update            *
  *                 encoding schemes.                            *
  ****************************************************************
  * PROBLEM DESCRIPTION: Change of the encoding scheme was not   *
  *                      supported in Object Compare.            *
  ****************************************************************
  * RECOMMENDATION: Apply The PTF.                               *
  ****************************************************************
  Change of the encoding scheme was not supported in Object
  Compare.
  

Problem conclusion

Temporary fix

Comments

• Object Compare will  process changes to encoding  scheme in the
  database, tablespace and table.  The tablespace encoding scheme
  change will  be propagated to all  tables from that  tablespace
  and  return code will be set to 4.    For new tables and tables
  found only in catalog but kept because Suppress DROP of objects
  was specified, following warning message will be generated :
   Warning : Encoding scheme will be changed to match the encoding
             scheme from the tablespace.
  
  For tables which exist in catalog and are updated following
  warning message will be generated :
   (W)Encoding scheme  of the table  was not changed but is
      different than encoding scheme  of the tablespace  in
      which the table was created.  The tablespace encoding
      scheme will be propagated to the table. Therefore the
      table will have the encoding scheme  changed from the
      <target_encoding_scheme> to <source_encoding_scheme>.
  
  If the table encoding scheme change is different then the
  encoding scheme of the tablespace the return code is set
  to 16 and following error message is generated:
   (E)Encoding scheme  of the table should be  changed from
      <target_encoding_scheme>  to <source_encoding_scheme>
      but the new value  is different than  encoding scheme
      of the tablespace in which the table was created. The
      change was ignored.
      Please include the same encoding schema update for the
      tablespace in the source and rerun.
  
  If there were changes to encoding scheme from tablespace and/or
  table, a general warning message about possible implications is
  generated at the end of the OC report and return code is set to
  4.
  

APAR Information

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

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

  UK45542

Modules/Macros

•    GOC2CMF  GOC2CMP  GOC2CMR  GOC2CMS  GOC2CMT
  

Fix information

• Fixed component name

  DB2 OBJECT COMP

• Fixed component ID

  5697G6400

Applicable component levels

• R720 PSY UK45542

     UP09/04/10 P F904

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.