IV27355: MIGRATION MANAGER CHANGE PACKAGE FAILS MIGRATING OBJECTS WITH MULTILANGUAGE SUPPORT

APAR status

• Closed as program error.

Error description

• Migration Manager change package fails migrating objects with
  multilanguage support when transLanguage="DE is set in the
  DDMETADATA_1.xml.
  
  When creating Migration packages of type change, object
  structures containing references to language tables are not
  correctly migrated. I have stepped onto this error with domains
  (MAXDOMAIN/L_MAXDOMAIN) and object attributes
  (MAXATTRIBUTECFG/L_MAXATTRCFG).
  
  BS 7117 + TSRM 7.2.1.0 (Base Language = ENG ; Second Language =
  GERMAN) + any other second languages
  
  Steps to replicate used by L2 support to reproduce the problem
  
  ===============================================================
  I tested the same scenario in my maxdemo BS 7118 + TSRM 7.2.1.1
  but also in BS 7117 + TSRM 7.2.1.0 with base language = Eng and
  German as a second language.
  
  1. Login into Maximo as MAXADMIN and set the user profile to
  GERMAN.
  
  2. Make sure to restart the server
  
  3. Log back into with German profile and Create a change
  package definition containing the DATADICTIONARY
     migration group.
  
  4. Activated the change package definition
  5. Created a new ALN domain
  
  6. Distributed, download the package
  
  As I used the same environment as source and target:
  I Removed the package defintion
  I Removed the new domain
  
  To implement the package:
  - Uploaded the previously downloaded package
  - Deployed the package and at this stage the package will fail
  to deploy in Target and will display the following error in the
  log.
  
  MXAA4211E - Database error number 1 has occurred when operating
  on L_MAXDOMAIN Sprache=DE Eigentümer-ID=1.117. ORA-00001: unique
  constraint (MAXIMO.L_MAXDOMAIN_NDX1) violated.
  
  One or more values in the INSERT statement, UPDATE statement, or
  foreign key update caused by a DELETE statement are not valid
  because the primary key, unique constraint or unique index
  identified by "2" constrains table "MAXIMO.L_MAXDOMAIN" from
  having duplicate values for the index key.. SQLCODE=-803,
  SQLSTATE=23505, DRIVER=3.53.70.
  
  Apparently this issue is not present using snapshot packages (I
  have verified this with domains). Also when the references to
  the language tables are removed from the package contents, the
  migration was successful.
  

Local fix

• It's been suggested the creation of the package has to
  be done in Base Language and not secondary language to avoid the
  error message that they are getting.
  
  Reason:
  This is because when the superuser is set as "DE" and login in
  German and create the package in German in source and implement
  in Target in German. There seems to be a duplication in
  Language table because you have main table maxattribute and
  child l_maxattribute the description in maxattribute table is in
  user language. If it is german than description in German. Also
  L_ table will have German description , hence duplication so the
  superuser has to be set against the Base Language to create the
  package and implement it.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users who switch their Maxadmin user to a    *
  *                 secondary language.                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: If you switch your  Maxadmin user to a  *
  *                      secondary language, the Migration       *
  *                      Manager exports certain xml files  with *
  *                      a mismatch in the base an transLanguage *
  *                      language.                               *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  *                                                              *
  *                                                              *
  *                                                              *
  ****************************************************************
  MIGRATION MANAGER CHANGE PACKAGE FAILS MIGRATING OBJECTS WITH
  MULTILANGUAGE SUPPORT
  

Problem conclusion

• The Migration Manager switched user internally to the Maxadmin
  user when it should have user the logged in user. The fix was
  to make sure the Migration Manager does not switch user to
  Maxadmin.
  
  
  
  
  
  The fix for this APAR is contained in the following maintenance
  package:
  
    | release\fix pack | Release 7.1.1.12
  

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

  SYSTEM CONFIG

• Fixed component ID

  5724R46S1

Applicable component levels

• R711 PSY

     UP