Maximo

 View Only

 MAS Maximo Mobile DB generation Java heap space error

Levente Molnár's profile image
Levente Molnár posted Wed November 19, 2025 10:43 AM

Hi Everyone!

We have upgraded Maximo 7.6 environment to MAS 9.0.9 and since the upgrade Maximo Mobile DB generation is not working. Crontaks is running 1 hour and failing with Java heap space error. See attached pic and logs.

We have tried to recreate the cron task, reload, change the parameters but nothing helped. We tried to change maximo.mobile.db.gen.dir and mxe.int.globaldir system properties but nothing helped.

If you have ever faced this kind of issue don't hesitate to contact me! Thank you in advance!

Cheers,

Levi

Attachments  View in library
Crontask_20251114.png 186 KB
nonprod2-test1-all-6bb4fd447b-4779l-all.txt 22.82 MB
Kiran Kumar Upputuri's profile image
Kiran Kumar Upputuri posted Mon December 15, 2025 04:09 AM

Hi Levente,

Can you check the below link, it might help you.
https://www.ibm.com/support/pages/java-heap-space-error-when-syncing-maximo-mobile

Regards,

Kiran Kumar

Steven Shull's profile image
Steven Shull posted Tue December 16, 2025 08:19 AM

I appreciate you providing the logs because there are different causes of this error. You are getting the issue with table domains, which there are two defects for:

Known Issue: DT447659
&
Known Issue: DT365902

To support table domain specifications, they created a new non-persistent object that tries to build out the values for any table domain specifications. The problem is if the table domain is against a large object (such as workorder), it can literally be creating millions of entries in a single MboSet. There was an earlier defect because it used to occur for any table domain attribute, even if it was not valid on any asset or SR classification which were the only two places that supported entering specifications at the time (now Work Order does as well). 

I haven't reviewed the changes made in dt447659 to know how it was changed but it is listed as fixed in the 9.0.17 patch (IBM Maximo Application Suite - Manage Operator patch 9.0.17)

Levente Molnár's profile image
Levente Molnár posted Tue December 16, 2025 11:48 AM

Hi Everyone,

Thanks for the tips but I've already solved this issue.

The solution was: set mxe.map.geometry.enableautolocate system property to FALSE. Perform live refresh and then run the cron task again to see if the Out Of Memory issue went away.

Regards,

Levi

Related Content