Maximo Open Forum

 View Only

 From last 2 days, Maximo is getting critically slow at a specific period of the day and the slowness disappears by its own.

  • Everything Maximo
Deepa P's profile image
Deepa P posted 02-23-2023 22:59

Hi Team,

From last 2 days, Maximo Production is getting critically slow at a specific period of time and the getting resolved by its own. While it is slow, we tried restarting the JVms in the webspeher application but it did not help. We also deleted all heap dumps file that were generated. We contacted with the DBa to check if there were any long running queries at that specific time but nothing. 

Also, after 15 to 20 mins, when the start center gets loaded, all portlets gets loaded with data(ex: workorders generated that day etc) except for one portlet "current no of users logged in", it shows this error: BMXAA6713E - The MBO fetch operation failed in the mboset with the SQL error code 0. The record could not be retrieved from the database.

The logs are also full of same error"BMXAA6713E - The MBO fetch operation failed in the mboset with the SQL error code 0. The record could not be retrieved from the database.". Can you please suggest what else do we need to check and with which team and what can be the probable cause of the error?

Will a database restart resolve the issue? are there any risks in that? Please help

Steven Shull's profile image
Steven Shull posted 02-28-2023 09:00

The logs should have more details about the error (error code 0 represents multiple things in SQL Server) but error code 0 is typically a closed database connection error which would mean you need to restart the JVM to resolve. This is an issue that's been fixed on a lot of Maximo versions but essentially what happens is something causes a database connection to be closed (SQL Server failover, a long running query that someone killed manually, etc.) and Maximo continues to re-use that connection even though it has become invalid. I worked with the product team (back when I was a user) to get this addressed as part of APAR IJ25026 (https://www.ibm.com/support/pages/apar/IJ25026). 

My guess is the database server is having issues (a blocking query for example), the DBA is identifying the query causing the issue, and then they go and kill the query manually. This improves performance but because Maximo doesn't re-establish these connections on the version you're on, you run into these issues.

Related Content