Known issues and limitations for Db2 Data Management Console

The following known issues and limitations apply to Db2 Data Management Console.

Known issues

DMC fails to provision when using a tethered namespace in ArgoCD.

Applies to: 5.3.1

DMC application becomes unhealthy because the ibm-dmc-controller-manager-xxx operator enters a CrashLoopBackOff state. This issue occurs when the --tethered_instance_ns parameter is passed in the cpd-ci manage create-argo-apps command. DMC is not supported in tethered projects or namespaces. Refer to Multitenancy for services

As a workaround, follow the steps below to ensure that DMC application is deployed correctly if you are using a tethered namespace in the cpd-ci manage create-argo-apps command. After running the cpd-ci manage create-argo-apps command, edit the DMC application YAML files located in the folder path shown in the below example:

CPD_CLI_MANAGE_WORKSPACE=/root/cpd-cli-workspace/olm-utils-workspace/work

Edit the following YAML files:
  1. Edit cluster-scoped DMC app YAML:
    vi ${CPD_CLI_MANAGE_WORKSPACE}/charts/5.3.1/cluster-scoped/dmc-cluster-scoped-app.yaml
    Before:
    tetheredNamespaces:
    - z1
    Change to:
    tetheredNamespaces: []

    Save and exit the file.

  2. Edit namespace-scoped DMC app YAML:
    vi ${CPD_CLI_MANAGE_WORKSPACE}/charts/5.3.1/namespace-scoped/dmc-app.yaml
    Before:
    tetheredNamespaces:
    - z1
    Change to:
    tetheredNamespaces: []

    Save and exit the file. You must remove all tethered namespaces such as z1.

  3. Apply cluster-scoped YAML:
    oc apply -f ${CPD_CLI_MANAGE_WORKSPACE}/charts/5.3.1/cluster-scoped/dmc-cluster-scoped-app.yaml

    After applying, check the DMC applications in the ArgoCD UI to confirm they are synced and healthy.

  4. Apply namespace-scoped YAML:
    oc apply -f ${CPD_CLI_MANAGE_WORKSPACE}/charts/5.3.1/namespace-scoped/dmc-app.yaml
Custom alerts generated do not show in the notification center for Alerts

Applies to: 5.3, 5.2 and 5.1

Custom alerts generated do not show in the notification center for Alerts.

The Db2 Data Management Console fails to load data into Db2

Applies to: 5.3, 5.2 and 5.1

When a user attempts to load data into Db2, it fails with an access denied and File I/O error messages.

As a workaround, complete the following steps:
  1. Connect to the db2u pod. For example, run the following command:
    oc rsh c-db2oltp-1703681564383095-db2u-0
  2. Clear the user folder. For example, to clear the cpdadmin folder, run the following command:
    rm -rf /mnt/blumeta0/db2/load/cpadmin/
  3. Change the group ownership of files and directories. For example, run the following command:
    sudo chown -R db2uadm:db2iadm1 /mnt/blumeta0/db2/load/

Limitations

DMC runsql pods fail to start due to ephemeral-storage constraints

Applies to: 5.3

Db2 Data Management Console runsql pods fail to start. As a result, the ibm-dmc-1770179333068605-register pod also does not come up.

As a workaround, the ephemeral-storage is increased to 2GI to the runsql pod.
oc patch dmc data-management-console -n ${PROJECT_CPD_INST_OPERANDS} --type=merge --patch
        '{"spec":{"custom_resources_v2":{"runsql":{"resources":{"limits":{"cpu":"400m","memory":"1000Mi","ephemeral-storage":"2Gi"},"requests":{"cpu":"400m","memory":"1000Mi","ephemeral-storage":"500Mi"}}}}}}'
The Database availability widget displays incorrect values for availability percentage

Applies to: 5.3

The Database availability widget in the Summary page might not display the correct value for availability percentage. The availability percentage is calculated based on historical data. When the repository database is not available for a certain period, the historical data for that period is lost causing the availability percentage value to deviate.

As a workaround, view the database availability alert to understand whether the database is available or not.

Db2 Data Management Console fails to import large CSV files

Applies to: 5.3

The Db2 Data Management Console fails to import large CSV files (300 MB or larger) from your local system.

As a workaround, use Cloud Object Storage or Amazon S3 for importing large CSV files.