IBM Support

Collecting Data: Preloaded DB

Troubleshooting


Problem

This document describes the process for collecting data for problems with the Maximo Mobile preloaded database. Gathering this MustGather information before contacting IBM support helps us understand the problem and saves time in the investigation. This MustGather will provide guidance on where and how to collect information to assist with troubleshooting issues.



Collect Data
 
Describe the problem:
Include the full error message and description of the problem. Identify where the problem is occuring and then gather the corresponding data.
Server side: There is a problem with generating the preloaded database from the mobileDBGeneration cron task
1. In the Maximo Cron Task Setup Application select the MobileDbGeneration cron task.
2. Select the problem mobileDBGeneration and click on the history tab. Take a screenshot ensureing the Run Time error column is included.
3. Collect the Maximo server logs. For Maximo,gather the systemout.log, for MAS, use the mustGather.

Client side: The error occurs on the mobile device when downloading the preloaded DB
1. Capture a screenshot of the data sync page where the preloaded database is downloaded.
2. Gather the mobile device log. Select the navigator (9 dot menu) > Help and Support > Log data. Select the share log icon in the upper right.
 
Documentation

This is the main topic in the IBM documentation for the Maximo Mobile preloaded database.
https://www.ibm.com/docs/en/masv-and-l/maximo-manage/continuous-delivery?topic=mobile-preloaded-data-devices

Technote on how to setup a preloaded database
Maximo Mobile - How to setup preloaded database to improve lookup download performance?

This document contains Lookup and Supporting Data queries which are used for the preloaded database
Maximo Mobile application object structures and query information
 
Troubleshooting

Additional information may be required to investigate preloaded database issues.
 
  • Server Debug logging:
    1. In the Maximo Logging application select the Graphite logger.
    2. Change the log level to DEBUG. Save and then apply settings.
    3. Reproduce the issue running the preloaded DB using the MobileDbGeneration cron task.
    4. Collect the Maximo server logs. For Maximo, gather the systemout.log, for MAS, use the mustGather.
    5. Revert the log level back to the default, INFO.
     
  • Mobile Debug logging:
    1. In the Maximo mobile select the Navigator (9 dot menu) > Help and Support > Log data.
    2. Toggle on the Enable debug logging option.
    3. Reproduce the issue in the mobile app.
    4. Return to the Log data page and select the icon in the upper right to share logs
     
  • Query the mobiledb table in the Maximo Database
    Run the following sql query in the maximo database to gather more details about the preloaded database.
    select MOBILEDBID, STATUS, BUILDTIMESTAMP, GENERATIONTRACE, GENERATIONTIME, PERSONGROUP from MOBILEDB;

    The mobiledbid returned from the sql query can be used in the following URL to download the preloaded database from the server.
    https://manageURL/maximo/oslc/graphite/mobile/db?mobileDbId=mobiledbid.
  • For out of memory errors on the server, gather the java core dump (.phd file).
    How to collect heapdumps and javacores in Maximo Application Suite Manage application
Title Description

After upgrading to Manage 9.0.11 the preloaded database creation fails due to a new relationship .CALTOOLTRANS.
Java heap space error appears when running the cron task, MobileDbGeneration.
If the user have access to a large set of prelaod DB to choose from(100+) this causes a memory crash.
FldAutolocatedGeometry calculationcauses causes a heap dump.
Refreshing lookup data with images fails when the _imagelibref attribute is used during synchronization.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSRHPA","label":"IBM Maximo Application Suite"},"ARM Category":[{"code":"a8m0z000000boKKAAY","label":"Mobility-\u003EConfiguration"},{"code":"a8m50000000CbEKAA0","label":"Mobility-\u003EGeneral Documentation"}],"ARM Case Number":"TS000000000","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"and future releases;8.10.0;8.11.0;9.0.0;9.1.0"}]

Document Information

Modified date:
26 June 2025

UID

ibm17233155

Page Feedback