Maximo Open Forum

 View Only
  • 1.  Service Request Application error while saving new record

    Posted 02-06-2024 23:05
    Edited by Raj kumar 02-06-2024 23:32
      |   view attached

    Dears,

    I'm using Maximo 7.6.x. I'm not able to save new record in service request application. I'm getting below error when I try to save new record.

    Not able to trace why this error is showing. Can someone help me how to resolve this?

    Thanks


    #Administration
    #Analytics
    #Architecture
    #Assets
    #Customizations
    #EndUser
    #EverythingMaximo
    #Infrastructure
    #Integrations
    #Inventory
    #IoT
    #LifeScience/Calibration
    #Linear
    #MaximoApplicationSuite
    #MaximoForAviation
    #MaximoUserGroups
    #Mobility
    #Nuclear
    #Procurement
    #Reporting
    #Scheduling
    #Security
    #ServiceProvider
    #Spatial
    #Transportation
    #Utilities
    #WorkCenters
    #WorkManagement

    ------------------------------
    Raj kumar
    ------------------------------



  • 2.  RE: Service Request Application error while saving new record

    Posted 02-07-2024 11:54

    Hello Raj, The error clearly states it is a database error, meaning the database is not happy with some data inputs, and not Maximo class validation.

    I am not too sure yet of the error code 727, and will check further. However, did you make any backend changes on the database that might require you to reset the sequence?



    ------------------------------
    ken ken
    Kenneth Eregie - Citi-Movers
    ------------------------------



  • 3.  RE: Service Request Application error while saving new record

    Posted 02-09-2024 09:37

    Raj,

    I believe you may be running on a DB2 database and a error -727 and is referencing a table or column that does not exist. My next step would be to look at the SystemOut.log or SystemErr.log during the time of this message as there will be additional SQL error codes that will be more specific to the actual problem and sometimes an indication where in the code or the actual SQL itself that is generating the error.  If you don't have access work with your Administrators to get these files. soon after you recreate the problem as the logs will wrap. 

    Mike



      ------------------------------
      Michael Marsonet
      MRM-EAM Consulting Inc.
      ------------------------------