PK94220: COLUMN (D)FIELD OWNERTYPE CHANGED FROM<GARBAGE> TO <GARBAGE> RESULTS IN TABLE BEING DROPPED AND RECREATED - NO IGNORE AVAIL

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The DB2 Object Comparison Tool for z/OS issues a message:
  Compare table source(aaaaaaa.aaaaaaaaaaaaaaaa) and
  target(aaaaaaa.aaaaaaaaaaaaaa
    Column aaaaaaaaaaaaa
      (D)Field OWNERTYPE changed from '        ;        0     346
  CB  ﾪH       }
                                   to '    )
  ;        0
    Tables have identical column lists
    Table aaaaaaa.aaaaaaaaaaaaaaaa will be dropped
    Table will be recreated
  even when the SYSTABLES OWNER and OWNERTYPE IGNORE's are
  specified. SYSCOLUMNS does not have an OWNERTYPE IGNORE
  available.
  

Local fix

• None as manually coding an IGNORE of:
    SYSCOLUMNS:OWNERTYPE
  results in the job ending RC12 and the message:
  GOCC007E - Invalid field name in IGNORES file record n
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Object Comparison Tool.         *
  ****************************************************************
  * PROBLEM DESCRIPTION: Object Comparison reports OWNERTYPE     *
  *                      change under column name while there    *
  *                      is no such change. The table is         *
  *                      dropped/recreated.                      *
  *                                                              *
  *                      Specifying OWNERTYPE in the IGNORE data *
  *                      set does not help. Additional problem:  *
  *                      message "ADBDICT:Key already exists".   *
  ****************************************************************
  * RECOMMENDATION: Apply The PTF.                               *
  ****************************************************************
  Object Comparison reports incorrectly OWNERTYPE change and
  drops/recreates the table. Additional problem: message
  "ADBDICT:Key already exists".
  

Problem conclusion

• Both problems have been fixed.
  

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

•    GOC2CMP  GOC2CMR  GOC2CMS  GOC2CMT
  

Fix information

• Fixed component name

  DB2 OBJECT COMP

• Fixed component ID

  5697G6400

Applicable component levels

• R720 PSY UK50282

     UP09/09/26 P F909

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.