Setting up a repository fails

When you setup a repository in Db2® Data Management Console, it fails.

Symptom
The status of Dbprofile configmap is always connecting.
oc get cm {Db2u_instance_id} -o jsonpath='{.data.status}'

Workaround

Delete the pod list by running the following command: 
oc get pod | grep registry-manager
Symptom
The location of SSL certificate is incorrect. When you run the command oc logs ibm-dmc-addon-api-xxxxxx , you might see an error message similar to the following message:
Java.io.FileNotFoundException: Error opening socket to server c-db2wh-xxxxxxxx-db2u-engn-svc/172.30.160.4 on port 50,001 with message: /opt/ibm-datasrvrmgr/Config/internal-tls/ca.crt (No such file or directory).

Workaround

Refer to Configuring JDBC properties.

Symptom

The database is assigned to the monitor pod, even though the CP4D zen-core-api is idle for more than 15 minutes. Also, the Db2 Data Management Console addon fails to get the instance status. It deletes the metadata that is related to the Db2 Data Management Console instance, but doesn't clean the databases that are assigned to the monitor pods.

Workaround
  1. Check the log of DMC addon-api pod. 
    oc logs $(oc get pod -l component=dmc-addon-api -o
        jsonpath="{.items[0].metadata.name}")
    If you find an error message similar to Db {DbName} has already been assigned to monitor pod, then edit the assignment configmap by using the following command: 
    oc edit cm ibm-dmc-$(oc get dmc -o
        jsonpath="{.items[0].spec.zenServiceInstanceId}")-ucconfigmap -o yaml
  2. In the configmap, find the profile_mon_map.yaml key. For example, 
    profile_mon_map.yaml: |
    ibm-dmc-1658481570282442-monitor-0:
      host: ibm-dmc-1658481570282442-monitor-0.ibm-dmc-1658481570282442-monitor-stateful.cpd-instance.svc.cluster.local
      profiles:
        db2oltp-1658818957193106: ""
    ibm-dmc-1658481570282442-monitor-1:
      host: ibm-dmc-1658481570282442-monitor-1.ibm-dmc-1658481570282442-monitor-stateful.cpd-instance.svc.cluster.local
      profiles:
        db2oltp-1658818943672593: ""

  3. In the error message, find the {DbName} that has the same instanceid as the profile name and delete it from the configmap. For example, if the DbName is db2oltp-1658818943672593, then delete it from the configmap as shown the following code:

    profile_mon_map.yaml: |
    ibm-dmc-1658481570282442-monitor-0:
      host: ibm-dmc-1658481570282442-monitor-0.ibm-dmc-1658481570282442-monitor-stateful.cpd-instance.svc.cluster.local
      profiles:
        db2oltp-1658818957193106: ""
    ibm-dmc-1658481570282442-monitor-1:
      host: ibm-dmc-1658481570282442-monitor-1.ibm-dmc-1658481570282442-monitor-stateful.cpd-instance.svc.cluster.local
      profiles:
  4. After you delete the profile, restart the registry-manager pod.