IBM Support

Maximo Asset Management interim fix 002 released

Technical Blog Post


As with all interim fixes, Maximo Asset Management interim fix 002 is cumulative. It contains all fixes from earlier interim fixes, with the addition of new fixes listed in this post.


 Tivoli's process automation engine interim fix 002 is available at Fix Central.


Application Name



System UI Security Scans

Security defect. CVE-2017-1208; CVSS Base Score: 5.4; CVSS Temporal Score: Go to for the current score.



In the Assets application, if you have a meter registered on an asset, you can only register new meter readings to the meter if it is active.
However, if you integrate Maximo Asset Management with an external system that is sending meter readings to Maximo Asset Management, values are accepted even though the meter is not set as active.



In the Assets application, when you change the status of an asset that has active PMs associated with it, selecting the option to change the status of all the associated PMS to inactive, the asset is still in the operating state. The status of the asset did not change even though you received a message that states that the record has been saved.



In the Inventory application, when you are importing records, an error occurs.


Map Manager

In the Map Manager application, you cannot find signature options that you created with Visible set to false and then added to a layer.


Migration Manager

In the Migration Manager, when you are migrating a DATADICTIONARY group, after the deploy is completed, the internal index has been deleted.


Service Requests

In the Service Requests application, when you apply a Service Request template, you receive the following message:
BMXAA4183E - Constructor not found. Use database configuration to check the field class registered and ensure that it is valid
and included in the deployment.


Service Requests

In the Service Requests application, when you duplicate a service request, the attributes are not copied over to the new service request.


Communication Template

When a host name is referenced in a communication template, the host name variable does not resolve correctly.


All Applications

When creating a new change record, you attempt to select a value from a field. Instead of retrieving the record, you receive the following message: BMXAA6713E - The MBO fetch operation failed in the mboset with the SQL error code 1795.  The record could not be retrieved from the database.


Report Viewer

When you run the Asset Cost Rollup report, some asset costs are rolled up higher than expected.



When you start the Maximo server, an error occurs in the systemout.log file.

To install, see Installing an interim fix in Maximo 7.6.

[{"Business Unit":{"code":"BU005","label":"IoT"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":""}]