IZ94652: MIGRATION MANAGER ISSUE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Customer is migrating MEA Interface using MM and reporting
    fallowing error:
    Error:
    
    
    Could not export configuration records to the staging table for
    package
    AGNVLDTN_usib-ddbx-ora18_cmms010d_MAXIMO_DEV_20110113085035.
    
    
    
    Error Details:
    
    psdi.util.MXApplicationException: BMXAA5324E - Could not extract
    or
    write xml document to staging table record for migration object
    DMMAXIFACEOUT for package
    AGNVLDTN_usib-ddbx-ora18_cmms010d_MAXIMO_DEV_20110113085035.
    
                    BMXAA4216E - Unknown Object.
    
    
    
                    at
    psdi.dm.pkg.DMPackage.writeMosToXML(DMPackage.java:287)
    
                    at
    psdi.dm.DMPackageDef.extractRecordsForMos(DMPackageDef.java:586)
    
                    at
    psdi.dm.DMPackageDef.extractRecordsForCfgGroup(DMPackageDef.java
    :531)
    
                    at
    psdi.dm.DMPackageDef.loadCFGDATAGrpsForPkg(DMPackageDef.java:364
    )
    
                    at
    psdi.dm.DMPackageDef.loadStagingForPkg(DMPackageDef.java:1254)
    
                    at
    psdi.dm.DMPackageDef.createPackage(DMPackageDef.java:231)
    
                    at
    psdi.dm.DMPackageDef.extractPkgData(DMPackageDef.java:186)
    
                    at
    psdi.webclient.beans.dm.DMPackageBean.continueCreatePackage(DMPa
    ckageBea
    n.java:235)
    
                    at
    sun.reflect.NativeMethodAccessorImpl.invoke0(Native
    Method)
    
                    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
    Impl.jav
    a:39)
    
                    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    Accessor
    Impl.java:25)
    
                    at
    java.lang.reflect.Method.invoke(Method.java:585)
    
                    at
    psdi.webclient.system.session.AsyncProcess.run(AsyncProcess.java
    :95)
    
                    at java.lang.Thread.run(Thread.java:595)
    
    Caused by: psdi.util.MXSystemException: BMXAA4216E - Unknown
    Object.
    
    
    
                    at
    psdi.iface.app.ifaceproc.MaxIfaceCondition.init(MaxIfaceConditio
    n.java:1
    25)
    
                    at psdi.mbo.Mbo.initialize(Mbo.java:875)
    
                    at
    psdi.mbo.MboSet.generateMboInstance(MboSet.java:2001)
    
                    at
    psdi.mbo.MboSet.getDiscardableMbo(MboSet.java:1962)
    
                    at psdi.mbo.MboSet.getMbo(MboSet.java:1800)
    
                    at
    psdi.iface.mos.MOSStAXStructure.createStructure(MOSStAXStructure
    .java:44
    6)
    
                    at
    psdi.iface.mos.MOSStAXStructure.createStructure(MOSStAXStructure
    .java:47
    3)
    
                    at
    psdi.iface.mos.MOSStAXStructure.createXML(MOSStAXStructure.java:
    724)
    
                    at
    psdi.iface.mos.StAXStructure.serializeMboSet(StAXStructure.java:
    230)
    
                    at
    psdi.dm.pkg.DMPackage.writeMosToXML(DMPackage.java:268)
    
                    ... 13 more
    
    Caused by: java.lang.NullPointerException:
    
                    at
    psdi.iface.app.ifaceproc.MaxCondDetail.checkCompareType(MaxCondD
    etail.ja
    va:700)
    
                    at
    psdi.iface.app.ifaceproc.MaxCondDetail.init(MaxCondDetail.java:1
    77)
    
                    at psdi.mbo.Mbo.initialize(Mbo.java:875)
    
                    at
    psdi.mbo.MboSet.generateMboInstance(MboSet.java:2001)
    
                    at
    psdi.mbo.MboSet.fetchMbosActual(MboSet.java:2611)
    
                    at psdi.mbo.MboSet.fetchMbos(MboSet.java:2550)
    
                    at psdi.mbo.MboSet.getMbo(MboSet.java:1843)
    
                    at psdi.mbo.MboSet.isEmpty(MboSet.java:3829)
    
                    at
    psdi.iface.app.ifaceproc.MaxIfaceCondition.init(MaxIfaceConditio
    n.java:9
    0)
    
                    ... 22 more
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All user who is using Migration Manger to    *
    *                 move INtegration Rules from one system to    *
    *                 another                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Validation for retain MBo does not take *
    *                      MM Object Structure Configuration. IT   *
    *                      works mostly for use where hierarachy   *
    *                      is of objects is different. Code have   *
    *                      to acomodat all cases                   *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    *                                                              *
    *                                                              *
    *                                                              *
    ****************************************************************
    Validation for retain MBo does not take MM Object Structure
    Configuration. IT works mostly for use where hierarachy is of
    objects is different. Coe have to acomodat all cases
    

Problem conclusion

  • The cachk in question is actually duplicate chack. Some check
    but correcly is performend in other place. So this caide can be
    removed
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ94652

  • Reported component name

    MAXIMO ARCHIVIN

  • Reported component ID

    5724Y9000

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-02-08

  • Closed date

    2011-03-03

  • Last modified date

    2011-03-03

  • 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 ARCHIVIN

  • Fixed component ID

    5724Y9000

Applicable component levels

  • R710 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IBM Maximo Archiving with Optim Data Growth Solution

Software version:

710

Reference #:

IZ94652

Modified date:

2011-03-03

Translate my page

Machine Translation

Content navigation