Topic
2 replies Latest Post - ‏2013-05-14T22:44:34Z by swkim90049
Chris_in_NY
Chris_in_NY
46 Posts
ACCEPTED ANSWER

Pinned topic unique constraint (MAXIMO.MAXINTOBJECT_NDX) violated

‏2013-05-12T13:34:01Z |

 

We are Oracle 11G, Maximo 7.5, Weblogic.

When creating an object for using the MIF import tool, I got a unique constraint error.

If I had to guess ,the maxintobject sequence is not correct. We only used the Maximo app for our data updates, so not sure how this has happened. Our current value for maxintobjectseq is 456. 

The last object I tried to create (just now) , that also failed, is in the db with maxintobjectid value of 436. Do other items in the DB use this sequence ? I don't understand with the sequence is 456, but the last object created was 436. 

 

Suggestions on how to resolve?

 

10 May 2013 12:40:01:336 [ERROR] [MXServer] [] BMXAA4211E - Database error number 1 has occurred when operating on MAXINTOBJECT :  Object Structure=BU1_MXINVBAL. Report the error to the owner of the deployment.
psdi.util.MXSystemException: BMXAA4211E - Database error number 1 has occurred when operating on MAXINTOBJECT :  Object Structure=BU1_MXINVBAL. Report the error to the owner of the deployment.
10 May 2013 12:40:09:991 [ERROR] [MXServer] [] ORA-00001: unique constraint (MAXIMO.MAXINTOBJECT_NDX) 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)
10 May 2013 12:40:09:993 [ERROR] [MXServer] [] ORA-00001: unique constraint (MAXIMO.MAXINTOBJECT_NDX) 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)

 

  • Chris_in_NY
    Chris_in_NY
    46 Posts
    ACCEPTED ANSWER

    Re: unique constraint (MAXIMO.MAXINTOBJECT_NDX) violated

    ‏2013-05-13T20:23:44Z  in response to Chris_in_NY

    We found the max value for maxintoobjectid from maximo.maxintobject.

     

    Then set our maxintobjectseq   sequence to this value plus 1, and it resolve the unique constraint issues.

  • swkim90049
    swkim90049
    206 Posts
    ACCEPTED ANSWER

    Re: unique constraint (MAXIMO.MAXINTOBJECT_NDX) violated

    ‏2013-05-14T22:44:34Z  in response to Chris_in_NY

    Yes, the sequencing can be confusing. If you look at the CREATE SEQUENCE statement, do you see a parameter called CACHE? It might say CACHE 20. Oracle will cache the next 20 numbers. I don't know why Maximo delivers the statement by that default, but it can cause some issues when you are trying to sync the next record with Oracle expects to create.

    More details on how to alter the sequence:

    http://www.techonthenet.com/oracle/sequences.php

     

    Updated on 2013-05-15T20:31:07Z at 2013-05-15T20:31:07Z by swkim90049