PI07211: PRECISION SPECIFIED IS REGISTERED IN COLUMN SCALE OF DB2 CATALOG TABLE SYSIBM.SYSCOLUMNS. OC REPORTS A DIFFERENCE.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The precision specified is registered in column SCALE of DB2
  catalog table SYSIBM.SYSCOLUMNS.  While on lower level of DB2,
  TIMESTAMP data type only supports precision 6 and SCALE column
  of SYSIBM.SYSCOLUMNS always has value '0'.
  Source and Target are of different DB2 level,
  SYSIBM.SYSCOLUMNS.SCALE has different value, hence Compare
  reports the difference.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Object Comparison Tool for  *
  *                 z/OS who compare tables with TIMESTAMP       *
  *                 columns.                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: When comparing tables with TIMESTAMP    *
  *                      columns between a DB2 level prior to    *
  *                      DB2 10 New Function Mode (NFM), with    *
  *                      DB2 10 New Function Mode, Object        *
  *                      Compare incorrectly reports a           *
  *                      difference on the TIMESTAMP column      *
  *                      even though both the TIMESTAMP          *
  *                      columns being compared are defined      *
  *                      with default precision 6.               *
  *                                                              *
  *                      Example of the incorrect report:        *
  *                                                              *
  *                      Compare table source(>table_name<)      *
  *                      and target(>table_name<)                *
  *                        Column >col_name<                     *
  *                        (D)Type changed from TIMESTAMP to     *
  *                          TIMESTAMP(0)                        *
  *                      Table >table_name< will be dropped      *
  *                      Table will be recreated                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When comparing tables with TIMESTAMP columns between a DB2
  level prior to DB2 10 New Function Mode (NFM) with DB2 10
  New Function Mode, Object Compare incorrectly reports a
  difference on the TIMESTAMP column even though both the
  TIMESTAMP columns being compared are defined with default
  precision 6.
  

Problem conclusion

• 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:

  UI16209

Modules/Macros

• ADB2CMT
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RB10 PSY UI16209

     UP14/03/22 P F403

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.