Maximo Open Forum

 View Only

  • 1.  ORA-12899 :value too large for column MAXIMO.SERVERSESSION.RELOADCACHE (acttual:1028 maximum :1024) .

    Posted 11-25-2021 02:49
    Dear Experts,

       Please note that , In our production environment some times users are getting below error while routing the work flow and some time saving the record.


      ORA-12899 :value too large for column MAXIMO.SERVERSESSION.RELOADCACHE (acttual:1028 maximum :1024) .


     Our production environment is cluster environment.  So can we increase the length of the reloadcache  to 2048 , So that it will allow more text for caching .

     Can it be  any issue  in the caching mechanism  ? 

    As per my knowledge reloadcache frequently get updated in cluster environment to synch the other members.  

     

     Thanks
    Alok
    #Administration

    ------------------------------
    Alok Pattnaik
    Praxis Solutions
    ------------------------------


  • 2.  RE: ORA-12899 :value too large for column MAXIMO.SERVERSESSION.RELOADCACHE (acttual:1028 maximum :1024) .

    Posted 11-26-2021 10:43
    I'm assuming you don't have custom code that would trigger cache reloads, that the problem you are seeing is from supportable use of the product. As such, I would raise and work through a Support Case with IBM about this, in an effort to "make it better for the next guy."

    If you should end up having to make the column bigger on your own, you won't be able to do it through the UI, because SERVERSESSION is flagged as Internal. That would mean you have to turn to SQL or DBC scripting to change it.

    ------------------------------
    Jason Uppenborn
    Bentley Systems
    ------------------------------

    Original Message


  • 3.  RE: ORA-12899 :value too large for column MAXIMO.SERVERSESSION.RELOADCACHE (acttual:1028 maximum :1024) .

    Posted 11-26-2021 12:42
    Alok,

    This typically happens when you are trying to make numerous changes to the system configuration at once, for example updating or creating multiple system properties.  You may want to look at what records are getting updated that need to be synchronized and see if it is possible to perform those actions separately.  Not a great solution, but apart from manually increasing the column size as Jason Uppenborn noted, that is your best approach.

    Jason

    ------------------------------
    Jason VenHuizen
    Sharptree
    ------------------------------

    Original Message


Related Content