IBM Support

Additional step to redeploy Maximo Health if Maximo Predict is deployed

Troubleshooting


Problem

If IBM® Maximo® Predict and IBM Maximo® Health are both deployed and Maximo Health must be redeployed and reactivated, you must complete an additional step to reconnect the two applications.

If this step is not completed, users who have entitlement and an access level for only Maximo Predict are not able to log in to Maximo Predict or Maximo Health.

Resolving The Problem

In the MAS_domain name_PREDICT schema, in the PMITENANT table, change the value for the MAS_INTG_STATUS column to PENDING.  

For example, MAS_INTG_STATUS=‘PENDING’;

Document Location

Worldwide

[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSRHPA","label":"IBM Maximo Application Suite"},"ARM Category":[{"code":"a8m0z000000cwZDAAY","label":"Maximo Application Suite"},{"code":"a8m0z000000cxN3AAI","label":"Maximo Health"},{"code":"a8m0z000000cxN8AAI","label":"Maximo Predict"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1.0;8.2.0"}]

Document Information

Modified date:
30 October 2020

UID

ibm16357585