IV90215: MIGRATION MANAGER ERROR OCCURS WHEN SAME AS COLUMNS REFERENCED

APAR status

• Closed as program error.

Error description

• When Migrating Table Changes to Target Environment using
  Migration Manager an Error occurs complaining about SAME AS
  columns being referenced by IFACE Tables
  
  PROBLEM:
  When trying to use Migration Manager to migrate base tables to
  the target environment the client is seeing the following error
  if he has a related IFACE table that already exists on the
  target environment that has an attribute with a Same as value
  to a base table attribute that does not exist on the base table
  being migrated.
  
  BMXAA8875E - The attribute cannot be deleted because it is used
  as a Same as Attribute by the ASSETUSERCUST_IFACE object
  XYZLIMIT attribute. Before you delete the attribute, delete all
  attributes that use the Same as Attribute.
  
  We should not have to change IFACE tables before migrating an
   underlying table.  IFACE tables are usually regenerated
  afterwards from
  the EXTERNAL Systems application.  Migration manager should not
  check  SAME AS for IFACE tables.
  
  PERFORMANCE ISSUE: N
  
  STEPS TO REPRODUCE:
  The issue occurs when using Migration Manager so 2 environments
  are needed.
  
  On the Target environment:
  Add a new attribute to a base table such as Asset.  Then create
  an Integration Iface table based on the Asset table and then
  add this same new attribute to the Iface table (if it doesn't
  already exist) and in Database Configuration add values for the
  Sameas Object and Sameas Attribute to point the Iface attribute
  to the new attribute on the base Asset table.
  
  On the Source environment:
  Use an Asset object that does not have the new attribute that
  was added to Asset in the Target environment.
  Create a new Migration Manager package that contains the
  DATADICTIONARY Migration Group with the database information
  for the Asset object.  Create your Migration Package and save
  it and then Distribute it with a Type of file.
  
  Back on Target Environment:
  Copy the Migration Manager package created on the Source
  environment to the Target environment.  In Migration Manager,
  Upload the package and then Deploy the package.  When you try
  to deploy the package it will fail with an error similar to the
  one above.
  
  CURRENT ERRONEOUS RESULT:
  Starting in version 7.6 Migration Manager checks SAME AS for
  IFACE tables.
  This behavior was not in 7.5.x
  
  EXPECTED RESULT:
  Migration Manager should not check SAME AS for IFACE tables.
  
  
  ENVIRONMENT (SYSTEM INFO):
     Tivoli's process automation engine 7.6.0.4 Build
  20160316-1020 DB Build
  V7604-37,
  
  IBM TPAE Integration Framework 7.6.0.4 Build 20160313-2330 DB
  Build
  V7604-22,
  
  IBM Maximo Asset Management Scheduler 7.6.2.1 Build
  20160316-1020 DB
  Build V7621-18,
  
  IBM Maximo Spatial Asset Management 7.6.0.0 Build 20160311-0241
  DB
  Build V7600-61,
  
  TRM RulesManager SE 5.6.0.2 Build 1065 DB Build V510-01,
  
  IBM Maximo for Utilities 7.5.0.1-20160415-1806 Build
  20120710-0136 DB
  Build V7501-14 HFDB Build HF75
  

Local fix

• Delete the sameas attributes on IFACE tables on the Target
  environment before migrating the base tables.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Maximo Users                                             *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When Migrating Table Changes to Target Environment using     *
  * Migration Manager an Error occurs complaining about SAME AS  *
  * columns being referenced by IFACE Tables                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to latest release                                    *
  ****************************************************************
  PROBLEM:
  When trying to use Migration Manager to migrate base tables to
  the target environment the client is seeing the following error
  if he has a related IFACE table that already exists on the
  target environment that has an attribute with a Same as value to
  a base table attribute that does not exist on the base table
  being migrated.
  
  BMXAA8875E - The attribute cannot be deleted because it is used
  as a Same as Attribute by the ASSETUSERCUST_IFACE object
  XYZLIMIT attribute. Before you delete the attribute, delete all
  attributes that use the Same as Attribute.
  
  We should not have to change IFACE tables before migrating an
  underlying table.  IFACE tables are usually regenerated
  afterwards from the EXTERNAL Systems application.  Migration
  manager should not check SAME AS for IFACE tables.
  
  STEPS TO REPRODUCE:
  The issue occurs when using Migration Manager so 2 environments
  are needed.
  
  On the Target environment:
  Add a new attribute to a base table such as Asset.  Then create
  an Integration Iface table based on the Asset table and then add
  this same new attribute to the Iface table (if it doesn't
  already exist) and in Database Configuration add values for the
  Sameas Object and Sameas Attribute to point the Iface attribute
  to the new attribute on the base Asset table.
  
  On the Source environment:
  Use an Asset object that does not have the new attribute that
  was added to Asset in the Target environment. Create a new
  Migration Manager package that contains the DATADICTIONARY
  Migration Group with the database information for the Asset
  object.  Create your Migration Package and save it and then
  Distribute it with a Type of file.
  
  Back on Target Environment:
  Copy the Migration Manager package created on the Source
  environment to the Target environment.  In Migration Manager,
  Upload the package and then Deploy the package.  When you try to
  deploy the package it will fail with an error similar to the one
  above.
  
  CURRENT ERRONEOUS RESULT:
  Starting in version 7.6 Migration Manager checks SAME AS for
  IFACE tables. This behavior was not in 7.5.x
  
  EXPECTED RESULT:
  Migration Manager should not check SAME AS for IFACE tables.
  

Problem conclusion

• SAME AS columns being referenced by IFACE Tables does not
  restrict the deletion of table columns.
  
  The fix for this APAR is contained in the following maintenance
  package:
  	 | release\fix pack | Fix Pack Release 7.6.0.8 TPAE
  

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

  MIGRATION MANAG

• Fixed component ID

  5724R46MI

Applicable component levels

• R760 PSY

     UP