Look at the troubleshooting steps in IBM's technote: Maximo Mobile - How to setup preloaded database to improve lookup download performance?
For a preloaded database, you can see exactly where time is being spent. You can even download and view the mobile DB. For most customers, assets & locations are the most significant bottlenecks in performance. This is due to the amount of related data being downloaded, both in volumes of records (assets and locations tend to have the most amount of lookup records) and the amount of related data being retrieved from those objects (meters, asset status, parent/child hierarchy, etc.).
Once you know where time is being spent, test the API requests yourself and try to remove pieces of the oslc.select to try and narrow down the problem area. You can try and build this using the schema (/maximo/oslc/graphite/mobile/schema) but if you're on at least 9.0 (ideally a patch of 9.0, as there were issues with the initial release) you can hit /maximo/oslc/graphite/mobile/requests and get the URL for the request automatically from Maximo Mobile without needing to build it by hand using data in the schema.
Without knowing your exact version, there are various defects that have been accepted around performance. More recently for example we found an issue with the pluscduedate_np in the asset lookup datasource impacting the download of assets when none were calibrated (Known Issue: DT455130). This doesn't have a fix yet but was a significant impact we found for one of our customers. There are many other issues though that have been reported and fixed so you may see improvements by getting to a later patch level.
------------------------------
Steven Shull
Principal Maximo Solutions Engineer
Naviam
Cincinnati OH
------------------------------
Original Message:
Sent: Mon November 10, 2025 05:34 AM
From: Prathamesh Kulkarni
Subject: MAS Mobile DB Generation Process taking hour and hour to complete
Hi Mark,
Thanks for responding.
After elevating logger (SQL - INFO, Graphite- DEBUG, Cron - DEBUG), logs are rolling fine. Did not find any poor query with SQL warnings (BMXAA6720W). Memory on JVM is sufficient.
Problem is - there are no error in log file. DB generation process keeps on running and running. I can see size of DB increasing roughly 1 MB /30 mins..(slower at times).
Is the cron running and creating DB for unwanted records? That my guess looking at SQL logs. If true, what would be best approach to eliminate data from DB generation (thinking few options, disable download true on Mobile app xmls, in saved queries make 1=0 which are not required (e.g. ITEM, Inventory are not required for us).
------------------------------
Prathamesh Kulkarni
Original Message:
Sent: Mon November 10, 2025 04:37 AM
From: Mark Robbins
Subject: MAS Mobile DB Generation Process taking hour and hour to complete
Hi Prathamesh,
Have you checked the JVM logs to see what they are saying?
in particular:
- Are there slow SQL warnings (BMXAA6720W) when the SQL Logger is set to WARN?
- Does the available memory log entry indicate that the JVM is running low on memory?
- Are there repeated errors in the logs?
------------------------------
Mark Robbins
Technical Design Authority / IBM Champion 2017 - 2025
Cohesive (previously Vetasi Limited)
https://www.linkedin.com/pulse/maximo-support-advice-from-non-ibm-engineer-article-mark-robbins/
Original Message:
Sent: Sun November 09, 2025 09:06 AM
From: Prathamesh Kulkarni
Subject: MAS Mobile DB Generation Process taking hour and hour to complete
Hi,
Mobile DB Generation cron that prepare preload database is taking hours to complete, sometimes more than 24 hrs. Yes, there is huge location and asset data in Maximo schema but only 80k locations are required on mobile device which are restricted thru saved queries in object structure, still DB generation process is time consuming.
In Cron parameter, Thread count - 4, Pagination - 2000.
Any insight to it would be much appreciated.!
------------------------------
Prathamesh Kulkarni
------------------------------