IBM Support

Cleaning Up a Failed Activation of Safety Within Maximo Application Suite

Troubleshooting


Problem

Safety activation states it is activated before it is completed.  To verify, and debug, that Safety activation is completed, it is necessary to review the API log file.

Symptom

When you activate Safety, it almost immediately states it is completed successfully.  However, it does not yet know whether activation is completed, or if it was successful.

Resolving The Problem

Workaround:

To verify, and debug that Safety activation is completed, it is necessary to review the API log file.  In Red Hat OpenShift, navigate to the mas--safety project.  There is one pod with 'safety-api' in the name.  Look in the log file for a statement like:

Second part of tenant (3) provisioning is successful.  The number 3 in this example is random.

If instead of that message you see: Second part of tenant (3) provisioning failed. Then, there is a problem. The full log file needs to be reviewed to understand why it failed.

1. We advise that you Deactivate Safety when the log file contains provisioning failed.

2. Then, fix the issue as indicated in the log file and do the Activate again.

If any assistance is required, contact support with the full API log file.

Document Location

Worldwide

[{"Type":"SW","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":"a8m3p000000GoDCAA0","label":"Maximo Safety"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.4.0"}]

Document Information

Modified date:
21 May 2021

UID

ibm16454913

Page Feedback