IBM Support

IJ01006: IN MIIGRATION MANAGER TOOL, THE CLASSIFICATIONS ARE NOT REPLICATED THE SAME WAY BETWEEN ENVIRONMENTS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In Miigration Manager tool, the classifications are not
    replicated the same way between environments.
    The issue is when migrating classifications from source
    environment to target environment.
    
    The classstructureid field is not replicated from source
    environment to target environment:
    
    It is essential to keep the same classstructureid between
    environments.
    
    The classstructureid is assigned by the target environment
    itself, no matter what the migration packet dictates.
    
    Let's say you  are working on two developments :
    
    1) The first day you begin with development 1:   You created a
    classification, and the system assigned the id 1001 to the
    classstructureid field.
    
    2) The second day you begin with development 2:  You created a
    classification, and the system assigned the id 1002 to the
    classstructureid field.
    
    Now, if you migrate classification 1002 first, the target
    system will
    assign 1001 to that classification.
    
    In other words, it does not matter what the source packet
    dictates, the
    target system will always assigns a classstructureid of its own.
    
    
    
    Please help us to solve this issue so classifications are
    replicated
    without differences between environments.
    
    
    
    
    
    
    
    
    
    
    
    
    
    Steps to replicate the issue
    1- We are using our lab  environment to replicate the issue,
    for example :
    sccd1.lab.com is the source environment
    sccd2.lab.com is the target environment
    
    2- We have created random classifications (BE0200 and BE0201)
    in sccd1.lab.com:
    
    3- We are going to migrate only classifications BE0200 and
    BE0201. At this moment
    classifications BE0100 and BE0101 are not going to be migrated.
    
    4- Following we created the packages with the classifications
    we need to migrate and  we deployed the packets in the target
    environment sccd2.lab.com.
    
    5- Now We have  classifications BE0200 and BE0201 migrated to
    sccd2.lab.com.
    
    If   we  check  the  classifications in  the  database, We get
    the  following values  for  the
    classstructureid:
    At source environment sccd1.lab.com
    At target environment sccd2.lab.com
    The classtructureid value is different for the same
    classification between environments.
    It seems that the target system assigns a classtructureid value
    of its own.
    it does not follow what the packet dictates.
    The issue propagates to other objects.
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users who use the Migration Manager to migrate               *
    * classifications                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * The classstructureid on the target system is always newly    *
    * generated via Migration Manager to migrate classification    *
    * data. It does not take the classstructureid on the source    *
    * system.                                                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The classstructureid is always generated for Classstructure
    records.  This is the default behavior. For the Migration
    Manager to migrate the same classstructureid, a new property
    called mxe.dm.sameClassstructureid is introduced in maximo 7610.
    Out of box, the default is 0.
    
    User will need to turn the property value to 1 for the desired
    functionality.
    

Problem conclusion

  • This is fixed in code with a system property
    mxe.dm.sameClassstructureid.
    
    The fix for this APAR is contained in the following maintenance
    package:
    	 | release\fix pack | Interim Fix for Release 7.6.0.10 Product
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ01006

  • Reported component name

    MIGRATION MANAG

  • Reported component ID

    5724R46MI

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-10-25

  • Closed date

    2017-11-29

  • Last modified date

    2017-11-29

  • 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

    MIGRATION MANAG

  • Fixed component ID

    5724R46MI

Applicable component levels

  • R760 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCLJ96","label":"Migration Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"750","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
29 November 2017