IBM Support

IZ61692: UPGRADE NOT REMOVING MAXVARS CAUSING MIGRATION MANGER TO FAIL DEPLOYMENT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Client would prefer not to have to remove maxvars as a
    workaround everytime they run upgrade. Failure to do so caused
    Migration manger deployment to fail.
    
    IBM Developers have confirmed that the following varname entries
    could
    be removed from the MAXVARS and MAXVARTYPE applications and they
    have
    provided MSD with the following instructions. After executing
    proposed
    actions the user was able to Deploy DATA DICTIONARY
    successfully.
    
    MAXVARS
    
    This maxvar is from a release 4.0.1 fix pack to identify the fix
    version
    for support... it can be deleted.
    
    MX401F03 Maximo 4.0.1 Fix Pack identifier
    
    These nine maxvars are from release 4.1.1 fixes, and a few 4.1
    fixes, to
    enable changes from the documented function for client
    complaints. They
    can be deleted.
    
    SPECIALBUILD024653 see issue 024653 rel 4.1.1p04
    
    EQDRILLDOWN see 013943, 014748 rel 4.1 p01
    
    LOCDRILLDOWN see 013943, 014748 rel 4.1 p01
    
    USEEQMETER4PMDUE see 019950 rel 4.1.1 p03, 4.1 p03
    
    
    PMEQMETERDATETOL see 025002 rel 4.1.1 p04 , 4.1 p03
    
    ACTLABORINFUTURE see 023686 rel 4.1.1 p07
    
    ISSUE033223 see 033223 rel 4.1.1p05
    
    REVOKEOLDGROUP see 033425 rel 4.1.1 p06
    
    DEFAULTREPORTEDBY see 63924, 035356 rel 4.1.1 p07
    
    
    
    MXINTDOMAIN
    
    The following entries exist in the MAXVARTYPE table but not in
    MAXVARS:
    
    MAXVARTYPE
    
    DBMXAMITE
    
    ITSFW
    
    MEAUPGRADEINSTALL
    
    MXINTDOMAIN and MEAUPGRADEINSTALL are MEA related and has been
    fixed in
    the fixpack.
    
    I don't think we have to worry about the values in maxvartype
    since
    Migration Manager only complained about those maxvars that were
    not in
    maxvartype. It doesn't complain if there are not values in
    maxvars.
    
    Maxvartype has a defaultvalue column, so in standard usage there
    should
    be one or zero maxvar entries per varname and per SYSTEM, ORG,
    or SITE
    based upon vartype; and no extra orgs or sites or varnames..
    
    However, I doubt that Migration Manager actually checks for
    anything
    except for maxvars without a maxvartype by varname.
    
    ITSFW is used directly (not standard usage) but is only used in
    the
    context of Software Contracts in Asset Catalog, so I suspect
    that it is
    really part of IT Asset manager, and additional code is there.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: users of migration manager                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: legacy maxvars remain from maximo 4.x   *
    *                      and before.  databases upgraded from    *
    *                      thse versions may contain these maxvars *
    *                      that are not defined in MaxVarType as   *
    *                      other maxvars are.  this causes         *
    *                      migration manager to fail.              *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    *                                                              *
    *                                                              *
    *                                                              *
    ****************************************************************
    migration manager fails due to extraneous data
    

Problem conclusion

  • Add MaxVarType definitions for the orphan/extraneous maxvars
    
    The fix for this APAR is contained in the following maintenance
    package:
    
      | release\fix pack | REL 7.1.1.6 - BS
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ61692

  • Reported component name

    MAXIMO SYS CONF

  • Reported component ID

    5724R46S1

  • Reported release

    711

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2009-09-24

  • Closed date

    2009-11-13

  • Last modified date

    2009-11-13

  • 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

    MAXIMO SYS CONF

  • Fixed component ID

    5724R46S1

Applicable component levels

  • R711 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"711","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
13 November 2009