IBM Support

IV00145: CREATION OF NEW ROUTES STOPS NOT POSSIBLE CAUSINGDATABASE ERROR "NUMBER 1 HAS OCCURRED WHEN OPERATING ON ROUTE_STOP.."

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Problem title:
    
    Creation of New Routes stops not possible
    
    Problem description:
    
    When any user creates a new route with multiple route stops they
    receive an error ORA-0001: unique constraint ROUTE_STOP_NDX1
    violated.
    
    Steps to reproduce:
    
    See below how to reproduce and the analyses from IBM Tivoli
    Developer in Brazil as follows:
    
    1)Go to Planning/Routes and create a new record and
    2)Have multiple locations have route stops and try to save .
    3)The following error is displayed BMXAA4211E - Database error
    number 1 has occurred when operating on ROUTE_STOP Site=HOP-8809
    Route=G1119 Stop Added to Route=0.
    ORA-00001: unique constraint (MAXIMO.ROUTE_STOP_NDX1) violated
    Note1: If you enter location one at a time and save,the problem
    is NOT happening.
    
    Note2!:This core Maximo issue is possible to reproduce on OOTB
    Maximo and looks like this problem was introduced by a recent
    cumulative hot fix pack delivered by IBM support.
    Not sure which of the latest cum. fix packs this is caused
    by,however should explain from the below explanation as follows:
    
    The exact piece of code causing the error shows as
    follows(Brazil Lab comments added):
    
    To make things easier for development, this is the exact piece
    of code causing the error (my comments added as "ADDED BRAZIL
    LAB COMMENTS" ):
    
    Class: psdi.app.route.RouteStopSet, Method: getNextRouteStopId
    
     int getNextRouteStopId() throws MXException, RemoteException
     {
      //Fix for Issue 10-20810 - We want the orginal set, the the
    current set as the current set might be filtered.
      RouteStopSet fullSet = (RouteStopSet)
    this.getOwner().getMboSet("$myrouteSet", "route_stop",
    this.getRelationship());
    
    ADDED BRAZIL LAB COMMENTS  //ACA: this line is trying to
    retrieve the list of route stops, but we haven't saved the
    record yet, so the mbo's are in memory only, not database
    
    
      if (fullSet.count()==0)
    
    ADDED BRAZIL LAB COMMENTS //ACA: since the records are not in
    the database, the query will always return 0
       return 1; // issue 07-22218
    
    ADDED BRAZIL LAB COMMENTS //ACA: this method is used to return
    the value for the field ROUTE_STOP.ROUTESTOPID when adding a new
    record. Since the MboSet is always returning empty, all the
    ROUTESTOPIDs will be populated with 1 generating the error
    
      nextRouteStopId = nextRouteStopId==-1 ?
    (int)fullSet.max("routestopid")+1 : fullSet.nextRouteStopId+1;
      fullSet.close();
      return nextRouteStopId;
     }
    
    This results is the following exception:
    
    BMXAA4211E-Database error number 1 has occurred when operating
    on ROUTE_STOP Site=BEDFORD Route=TST2 Stop Added to
    Route=1.Ora-00001:unique constraint (MAXIMO.ROUTE_STOP_NDX1)
    violoated
    
    Environment:
    
    App ServerWeblogic Application Server 9.2.3.0
    DatabaseOracle 10.2.0.4
    VersionIBM Maximo Adapter for Primavera 7.1.1.0-20100809-2208
    Build
    20091209-1102 DB Build V7120-24
    Oil And Gas 7.1.1.0-20100921-0955 Build 20091211-0646 DB Build
    V7120-
    16 HFDB Build HF7120-02
    Scheduler 7.1.1.0-20110204-1026 Build 20100219-1725 DB Build
    V7110-33
    Base Services 7.1.1.6-LA20110307-1220 Build 20091208-1415 DB
    Build
    V7116-173 HFDB Build HF7116-22
    Maximo Calibration 7.1.2.0 Build 20100315-1032 DB Build V7130-13
    WMS 2.2.1.0 Build WMS_221_BUILD_2011_03_23_BUILD21 DB Build
    V220-68
    Common PMP 7.1.1.6 Build 20091130D DB Build V7116-05
    
    Business impact ( BusImpact ):
    
    To allow creation of a new route ,the user needs to save record
    after insertion of each route stop. Big overhead at creation of
    big routes
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: maximo                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: CREATION OF NEW ROUTES STOPS NOT        *
    *                      POSSIBLE CAUSING DATABASE ERROR "NUMBER *
    *                      1 HAS OCCURRED WHEN OPERATING ON        *
    *                      ROUTE_STOP Site=BEDFORD Route=TST2 Stop *
    *                      Added to                                *
    *                                                              *
    *                      Route=1.Ora-00001:unique constraint     *
    *                      (MAXIMO.ROUTE_STOP_NDX1)                *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    *                                                              *
    *                                                              *
    *                                                              *
    ****************************************************************
    CREATION OF NEW ROUTES STOPS NOT POSSIBLE CAUSING DATABASE
    ERROR "NUMBER 1 HAS OCCURRED WHEN OPERATING ON ROUTE_STOP
    Site=BEDFORD Route=TST2 Stop Added to
    
    Route=1.Ora-00001:unique constraint (MAXIMO.ROUTE_STOP_NDX1)
    

Problem conclusion

  • <This is caused by 10-20810 that was checked to HF 7116. It has
    been reported several times. The problem is corrected in REL
    7119, HF7118, and HF7116.  The clients can take HF7116 or HF
    7118 under 11-13322. .>
    
    
    
    
    
    The fix for this APAR is contained in the following maintenance
    package:
    
      | release\fix pack | REL 7.1.1.9 - BS
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV00145

  • Reported component name

    MAXIMO PLANNING

  • Reported component ID

    5724R46PL

  • Reported release

    711

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2011-05-10

  • Closed date

    2011-05-13

  • Last modified date

    2011-05-13

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

  • Fixed component ID

    5724R46PL

Applicable component levels

  • R711 PSY

       UP

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

Document Information

Modified date:
13 May 2011