Troubleshooting
Problem
In IBM® Maximo® Application Suite, changes that are made from the Application summary page to the IBM Maximo® Health database configuration are not applied because the health-runtime pod does not automatically restart.
Resolving The Problem
After you complete the database configuration changes, complete the following steps:
- As an administrator, log in to Red Hat® OpenShift® Container Platform.
- Click Projects and open the Maximo Health project.
- In the Inventory section, click Config Maps and then delete the maxinst-version config map.
- Click Pods and then locate and delete the health-runtime-<> pod. <> is a randomly generated set of numbers and letters.
The pod is automatically recreated and restarted.
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.2.0"}]
Was this topic helpful?
Document Information
Modified date:
13 November 2020
UID
ibm16357577