IBM Support

In IBM MDM Publisher, if an endpoint connection fails, the teardown script might not fully remove the pod

Troubleshooting


Problem

If an IBM MDM Publisher endpoint connection fails and causes the pod to go into an error state, you might want to remove the pod using the tear_down_publisher.sh script and then reinstall it. However, in MDM Publisher instances that were deployed using the Ansible Operator, you might get errors during the removal and subsequent installation after correcting the endpoint.

Resolving The Problem

To resolve this issue, manually delete the namespace of the MDM Publisher, then run a new MDM Publisher installation.
  1. Remove the publisher pod:
    ./tear_down_publisher.sh
  2. Delete the namespace:
    oc delete ns <PUBLISHER NAMESPACE>
  3. Reinstall the MDM Publisher operator and instance. For details, see IBM Documentation.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSWSR9","label":"IBM InfoSphere Master Data Management"},"ARM Category":[{"code":"a8m3p000000LPMoAAO","label":"Product-Related->Publisher"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0.0"}]

Document Information

Modified date:
27 April 2022

UID

ibm16479539