Updates to JDBC configuration are not applied in the Maximo Monitor application

Symptom

Suite-level updates to JDBC configuration are not applied immediately in the Maximo Monitor application.

Cause

The Service Binding Operator , which is responsible for applying Suite-level configuration changes to Suite applications, does not apply the changes in the Maximo Monitor application.

Resolution

1. Log in to the Red Hat® OpenShift® web console as an administrator.
2. In the mas-<instanceName>-monitor project, click Workloads > Pods.
3. Locate the pod that is named ibm-mas-monitor-operator-* and delete it.
4. In the web console or a command shell, delete all of the cron jobs in the project.

• In the web console, click Workloads > Cron Jobs and delete all of the cron jobs in the project.
• Alternatively, in a command shell, perform a bulk delete of all of the project's cron jobs by running the following command:

  for j in $(kubectl get cj --namespace mas-<instanceName>-monitor -o custom-columns=:.metadata.name); do kubectl delete cj $j; done

1. Open a connection to the Maximo Monitor database and delete the row in the IOTANALYTICS.KPI_IMAGE_MANAGEMENT table where the value in the TENANT_ID column matches your tenant identifier.
2. Click Workloads > Pods and locate the Maximo Monitor workspace pod, which is entitymgr-ws.
3. Delete the pod and allow it to fully restart.