IBM Support

IJ06964: UNABLE TO IMPORT MXINTOBJECT RECORDS THAT CONTAIN HASLD AND LANGCODE ATTRIBUTES

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • PROBLEM:
While attempting to import an XML or flat file containing
MXINTOBJECT records that contain MAXINTOBJCOLS subrecords using
MIF, an error is reported in the log and the import fails:

[5/17/18 14:03:03:222 EDT] 0000045a SystemOut O 17 May 2018
14:03:03:222 [ERROR] [MAXIMO] [CID-UIASYNC-106405] ORA-00001:
unique constraint (MAXIMO.MAXINTOBJCOLS_NDX1) violated

java.sql.SQLIntegrityConstraintViolationException: ORA-00001:
unique constraint (MAXIMO.MAXINTOBJCOLS_NDX1) violated

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:879)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:192)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
at
oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedState
ment.java:207)
at
oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPrepar
edStatement.java:1044)
at
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleSt
atement.java:1329)
at
oracle.jdbc.driver.OraclePreparedStatement.executeInternal(Oracl
ePreparedStatement.java:3584)
at
oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OracleP
reparedStatement.java:3665)
at
oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(
OraclePreparedStatementWrapper.java:1352)
at psdi.mbo.MboSet.insertMbo(MboSet.java:8383)
at psdi.mbo.MboSet.saveTransaction(MboSet.java:7779)
at
psdi.txn.MXTransactionImpl.saveTransaction(MXTransactionImpl.jav
a:221)
at psdi.txn.MXTransactionImpl.save(MXTransactionImpl.java:156)
at psdi.iface.mos.MosProcessImpl.save(MosProcessImpl.java:2357)
at
psdi.iface.mos.MosProcessImpl.processExternalData(MosProcessImpl
.java:364)
at
psdi.iface.mos.MosProcessImpl.processObjectStructureService(MosP
rocessImpl.java:223)
at
psdi.iface.mic.MicService.processObjectStructureData(MicService.
java:2282)
at
psdi.iface.mic.MicService.processObjectStructureService(MicServi
ce.java:2004)
at
psdi.iface.mic.MicService.processObjectStructureService(MicServi
ce.java:1730)
at
psdi.iface.load.ObjectStructureLoader.processData(ObjectStructur
eLoader.java:137)
at
psdi.iface.load.ObjStrInboundXMLSplitter.splitPerformed(ObjStrIn
boundXMLSplitter.java:105)
at
psdi.iface.stax.EventStAXSplitter.fireSplitEvent(EventStAXSplitt
er.java:480)
at
psdi.iface.stax.EventStAXSplitter.populateRepeatBlocks(EventStAX
Splitter.java:432)
at
psdi.iface.stax.EventStAXSplitter.traverseToRepeatBlock(EventStA
XSplitter.java:321)
at
psdi.iface.stax.EventStAXSplitter.split(EventStAXSplitter.java:1
13)
at
psdi.iface.load.XmlFileLoaderImpl.processObjectStructureXMLData(
XmlFileLoaderImpl.java:159)
at
psdi.iface.app.common.MaxIfaceLoad.importData(MaxIfaceLoad.java:
219)
at
psdi.webclient.beans.intobject.ImportBean.loadImport(ImportBean.
java:361)
at
psdi.webclient.beans.intobject.ImportBean.importdata(ImportBean.
java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
Impl.java:94)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
AccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:619)
at
psdi.webclient.system.session.AsyncProcess.run(AsyncProcess.java
:171)
at java.lang.Thread.run(Thread.java:853)

This is caused by two MAXINTOBJCOLS database inserts occurring
for the same integration object transaction as seen below:

[5/17/18 14:03:03:206 EDT] 0000045a SystemOut O 17 May 2018
14:03:03:206 [INFO] [MAXIMO] [CID-UIASYNC-106405] BMXAA6719I -
USER = (MAXADMIN) SPID = (The database session identifier
(spid) could not be retrieved for logging.) app (null) object
(MAXINTOBJCOLS) : insert into maxintobjcols
(maxintobjcolsid,changeby,changedate,objectname,intobjfldtype,na
me,intobjectname) values (?,?,?,?,?,?,?)
[5/17/18 14:03:03:206 EDT] 0000045a SystemOut O 17 May 2018
14:03:03:206 [INFO] [MAXIMO] [CID-UIASYNC-106405] BMXAA6721I -
Bind value for MAXINTOBJCOLSID = 7053
[5/17/18 14:03:03:206 EDT] 0000045a SystemOut O 17 May 2018
14:03:03:206 [INFO] [MAXIMO] [CID-UIASYNC-106405] BMXAA6721I -
Bind value for CHANGEBY = MAXADMIN
[5/17/18 14:03:03:206 EDT] 0000045a SystemOut O 17 May 2018
14:03:03:206 [INFO] [MAXIMO] [CID-UIASYNC-106405] BMXAA6721I -
Bind value for CHANGEDATE = 2018-05-17 14:03:02.567
[5/17/18 14:03:03:222 EDT] 0000045a SystemOut O 17 May 2018
14:03:03:222 [INFO] [MAXIMO] [CID-UIASYNC-106405] BMXAA6721I -
Bind value for OBJECTNAME = CI
[5/17/18 14:03:03:222 EDT] 0000045a SystemOut O 17 May 2018
14:03:03:222 [INFO] [MAXIMO] [CID-UIASYNC-106405] BMXAA6721I -
Bind value for INTOBJFLDTYPE = EXCLUDE
[5/17/18 14:03:03:222 EDT] 0000045a SystemOut O 17 May 2018
14:03:03:222 [INFO] [MAXIMO] [CID-UIASYNC-106405] BMXAA6721I -
Bind value for NAME = HASLD
[5/17/18 14:03:03:222 EDT] 0000045a SystemOut O 17 May 2018
14:03:03:222 [INFO] [MAXIMO] [CID-UIASYNC-106405] BMXAA6721I -
Bind value for INTOBJECTNAME = TESTOBJECT2
[5/17/18 14:03:03:222 EDT] 0000045a SystemOut O 17 May 2018
14:03:03:222 [INFO] [MAXIMO] [CID-UIASYNC-106405] BMXAA6719I -
USER = (MAXADMIN) SPID = (The database session identifier
(spid) could not be retrieved for logging.) app (null) object
(MAXINTOBJCOLS) : insert into maxintobjcols
(maxintobjcolsid,changeby,changedate,objectname,intobjfldtype,na
me,intobjectname) values (?,?,?,?,?,?,?)
[5/17/18 14:03:03:222 EDT] 0000045a SystemOut O 17 May 2018
14:03:03:222 [INFO] [MAXIMO] [CID-UIASYNC-106405] BMXAA6721I -
Bind value for MAXINTOBJCOLSID = 7052
[5/17/18 14:03:03:222 EDT] 0000045a SystemOut O 17 May 2018
14:03:03:222 [INFO] [MAXIMO] [CID-UIASYNC-106405] BMXAA6721I -
Bind value for CHANGEBY = MAXADMIN
[5/17/18 14:03:03:222 EDT] 0000045a SystemOut O 17 May 2018
14:03:03:222 [INFO] [MAXIMO] [CID-UIASYNC-106405] BMXAA6721I -
Bind value for CHANGEDATE = 2018-05-17 14:01:53.0
[5/17/18 14:03:03:222 EDT] 0000045a SystemOut O 17 May 2018
14:03:03:222 [INFO] [MAXIMO] [CID-UIASYNC-106405] BMXAA6721I -
Bind value for OBJECTNAME = CI
[5/17/18 14:03:03:222 EDT] 0000045a SystemOut O 17 May 2018
14:03:03:222 [INFO] [MAXIMO] [CID-UIASYNC-106405] BMXAA6721I -
Bind value for INTOBJFLDTYPE = EXCLUDE
[5/17/18 14:03:03:222 EDT] 0000045a SystemOut O 17 May 2018
14:03:03:222 [INFO] [MAXIMO] [CID-UIASYNC-106405] BMXAA6721I -
Bind value for NAME = HASLD
[5/17/18 14:03:03:222 EDT] 0000045a SystemOut O 17 May 2018
14:03:03:222 [INFO] [MAXIMO] [CID-UIASYNC-106405] BMXAA6721I -
Bind value for INTOBJECTNAME = TESTOBJECT2

PERFORMANCE ISSUE:  NO

STEPS TO REPRODUCE:
Navigate to the Integration object structures application
Create a new object structure named TESTOBJECT2.
Ensure it is consumed by INTEGRATION.
Set the source object to CI.
Save the new object structure.
Enable application import and export the the Object Structure
applicaiton using the documentation here:
http://www-01.ibm.com/support/docview.wss?uid=swg21507924

Now, export the new object stucture you created above called
TESTOBJECT2.
Next, delete the object structure created above.
Import the new file created from the export above using
application import option in the Object Structure application.

RESULTS:
The error is presented:

[5/17/18 14:03:03:222 EDT] 0000045a SystemOut O 17 May 2018
14:03:03:222 [ERROR] [MAXIMO] [CID-UIASYNC-106405] ORA-00001:
unique constraint (MAXIMO.MAXINTOBJCOLS_NDX1) violated

java.sql.SQLIntegrityConstraintViolationException: ORA-00001:
unique constraint (MAXIMO.MAXINTOBJCOLS_NDX1) violated

EXPECTED RESULTS:

The exported data should be able to be imported without
modification to the file before import.

PRODUCT VERSION:

Version Tivoli's process automation engine 7.6.0.8 Build
20170512-0100 DB Build V7608-63
IBM TPAE Integration Framework 7.6.0.8 Build 20170510-2330 DB
Build V7608-43

Local fix

  • Remove all column references to HASLD and LANGCODE from the
import file as this will be added automatically by the
processing class during the import.

Problem summary

  • ****************************************************************
* USERS AFFECTED:                                              *
* MAXIMO                                                       *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* UNABLE TO IMPORT MXINTOBJECT RECORDS THAT CONTAIN HASLD AND  *
* LANGCODE ATTRIBUTES                                          *
****************************************************************

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
package: release\fix pack for Release 7.6.1.3 Product

Temporary fix

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    IJ06964
    • 

  • Reported component name
    INTEGRATION
    • 

  • Reported component ID
    5724R46I1
    • 

  • Reported release
    760
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2018-06-08
    • 

  • Closed date
    2021-01-28
    • 

  • Last modified date
    2021-01-28
    • 





    

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

  • Fixed component ID
    5724R46I1
    • 



Applicable component levels


    








      
              
                            

              

              [{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"760"}]
              

                                                                    

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            29 January 2021
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback