IJ13150: UPGRADE TO MAXIMO 7.6.1 CREATES HUNDREDS OF COLUMNS INCORRECTLY.

APAR status

• Closed as program error.

Error description

• After upgrade to 7.6.1, Integrity Checker reports 1982 errors
  that were not reported previously. These errors are all of the
  variety:
  
  BMXAA0443E -- Error - BMXAA0494E -- The definition of this
  column does not match the actual column. The native column
  definition does not match the servers metadata. Run the
  Integrity Checker in repair mode.
  BMXAA6841I -- ACTCISPEC.LINKEDTOATTRIBUTE, Maximo definition is
  UPPER(16), Database column is UPPER(16)
  
  Why are these errors being reported? MaxVar VARCHARMULTIPLE is
  set to 2, which means that the native database column should be
  2 times the size of the Maximo-defined length
  maxattribute.length.  But according to the errors, that is not
  the case - columns are the same length as maxattribute.length.
   It appears that 7.6.1 UpdateDB does not take the
  VARCHARMULTIPLE setting into account when it adds/modifies a
  column.  Since this was not an issue previously, this is a
  regression.
  
  STEPS TO REPRODUCE:   On a database that supports a multi-byte
  character set - that is, maxvar VARCHARMULTIPLE is greater than
  1 - upgrade to 7.6.1.
  RESULTS: All text columns that are created or modified by the
  upgrade are now the same length as defined in
  maxattribute.length.
  EXPECTED RESULTS:   If VARCHARMULTIPLE=2, then columns should
  be 2 times the length defined by maxattribute.length.  If
  VARCHARMULTIPLE=3, then columns should be 3 times the length
  defined by maxattribute.length.
  
  PRODUCT VERSION:  7.6.1
  

Local fix

• Use tool varcharmultiplier to correct the lengths of the
  columns.
  
  1. First reset VARCHARMULTIPLIER to 1.
  2. Run varcharmultiplier.bat -m2
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo Users on 761                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The VARCHARMULTIPLE MaxVar was read incorrectly, causing     *
  * problems when setting that MaxVar or when running the        *
  * Integrity Checker.                                           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixpack Release 7.6.1.0 of Base Services, or request   *
  * an interim fix                                               *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  package:
  | release\fix pack\interim fix for Release 7.6.1.0 of Base
  Services
  

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

• MAXIMO
  

Fix information

• Fixed component name

  UPGRADE PROGRAM

• Fixed component ID

  5724R46UP

Applicable component levels

• R761 PSN

     UP