IBM Support

IV95951: WHEN TRYING TO MIGRATE DATADICTIONARY,INTERNAL INDEX IS DELETED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The problem :  when trying to migrate datadictionary, primary
    key
    index(internal index) is deleted unexpectedly.
    
    Client Version : 7607
    
    Steps to replicate.1. On the source Maximo env, add an attribute
    "T1TEST" to the "Asset"
    object from database configuration.
    After that, run "Apply Configuration Changes"(configdb).
    
    2. By migration manager, create a new one, and specify
    "DATADICTIONARY"
    for migration group, and set the condition for where clause of
    each migration object like below:
    
    Package Definition NAme : TESTMM
    Migration GRoups : DATADICTIONARY
    
    Setting of each migration object for DATADICTIONARY
    - DMMAXOBJECTCFG : objectname='ASSET'
    - other than above : 1=2
    
    3. For the distribution target, file path is specified.
    After generating migration package, output as a file.
    (Deploy this package on the migration target env)
    
    Click Common Actions/Manage Targets
    Click New row
    - Target Name : A_FILE
    - TYPE : FILE
    - File Path  : C:\TEMP\MMOUT
    
    4. In Distribution Tab,
    Add A_FILE Target created in the step3
    Save
    
    5. Change status to APPR
    
    6. In the Package Tab, create package with Replace   using
    Create
    button.
    
    ** IMPORTANT :  Need to use Replace processing option.
    
    
    7. In the Package Tab, Distribute the package created in the
    step 6
    using 'Distribute' button
    
    
    o Target Maximo env
    
    1. On the target maximo env, preliminarily set "DM" to
    authorization
    name for the following all object structures:
    From "Select Action" >> "Object Application Authorization".
    
    1) DMPKGDSTTRGT
    2) DMCFGGROUP
    3) DMDEPENDENCY
    4) DMPACKAGEDEF
    5) DMPACKAGE
    6) DMMAPDEF
    7) DMMAPRULES
    8) DMMAXOBJECTCFG
    
    NOTE:
    1) to 7) are used for the migration group"MIGRATION"
    8) is a migration object for the migration target this time.
    
    2. From the migration manager, go to "Select Action" >> "Manage
    Admin
    Mode" >> click "Turn Admin Mode On".
    
    3. Upload the package generated from the source env: from
    "Select
    action" >> "Upload Package".
    
    4. Deploy the package from "Select Action" >>> "Deploy Package"
    
    >>> After the deploy is successfully completed, checked the
    index on
    "ASSET" object that was set as
    migration target from Database Configuration, I noticed that
    internal
    index(primary key index) has been deleted.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users                                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When deploying a MM package, internal indexes on the target  *
    * environment will be deleted if the source package does not   *
    * include an index with a matching name.                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is included in the following release:
                          | Release 7.6.0.9 of Base Services.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV95951

  • Reported component name

    MIGRATION MANAG

  • Reported component ID

    5724R46MI

  • Reported release

    760

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-05-07

  • Closed date

    2017-05-16

  • Last modified date

    2017-05-16

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

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":"760","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
16 May 2017