PH34964: OBJECT COMPARE REPORTING DIFFERENCE WHEN USING DDL AS TARGET

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Object Compare Reporting Difference When using DDL as Target -
  LONG VARCHAR vs VARCHAR
  
  When running an object compare using DDL as target as opposed
  to the catalog as target, the results are different. The
  source has a table that has a column with a type of
  Longvarchar and the target has the same column with a type
  varchar.
  If the target is a DDL file, OC reports the difference and
  generates drops and creates for the tables and indexes.
  When the target is the catalog, OC does not report the
  difference.
  
  Although the syntax LONG VARCHAR is allowed for compatibility
  with previous releases of Db2, its use is not encouraged.
  VARCHAR(integer) is the recommended syntax.  OC should not find
  a difference
  
  For example:
  
  Compare source DDL with long varchar to catalog  (Correct):
  
  Compare table source(T1.table) and target(T1.table)
    (W)LONGVAR/LONGVARG columns(1) processed as VARCHAR/VARG
    No changes to Table
  
  
  Compare source DDL with long varchar to target DDL
  
  Compare table source(T1.table) and target(T1.table)
    Column COL1
      (D)Type changed from VARCHAR(100) to LONG VARCHAR
    Tables have identical column lists
    Table T1.table will be dropped
    Table will be recreated
    Table data will not be converted
    Not eligible for FORMAT INTERNAL processing
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Db2 Object Comparison Tool for      *
  *                 z/OS                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: Comparing a column of type LONGVAR to   *
  *                      the same column of type VARCHAR results *
  *                      in a drop and recreate of the table.    *
  ****************************************************************
  Compare treats column types LONGVAR and VARCHAR as different,
  but Db2 treats them the same. Comparing DDL to DDL for a column
  of type LONGVAR with a column of type VARCHAR results in a drop
  and create of the table. In this case, no difference should be
  recognized. Instead, when the only difference recognized is
  LONGVAR and VARCHAR column types for one column, Compare should
  report a message similar to the following example:
  
  Compare table source(>schema.name<) and target(>schema.name<)
    (W)LONGVAR/LONGVARG columns(1) processed as VARCHAR/VARG
       No changes to Table
  

Problem conclusion

• The problem has been resolved.
  

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:

  UI76109

Modules/Macros

• ADB2CMT
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RC10 PSY UI76109

     UP21/07/02 P F106

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.