Known issues and limitations for Db2 Data Management Console

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

Known issues

The Db2 Data Management Console fails to load data into Db2 for multiple users

Applies to: 5.0.3

After completing the workaround steps of changing the directory permissions, user still runs into issue with load data.

As a workaround, complete the following steps:

If you are using a private registry run the skopeo copy to copy the image to local private registry.

skopeo copy --all --authfile "<folder path>/auth.json" \

--dest-tls-verify=false --src-tls-verify=false \

docker://cp.icr.io/cp/cpd/ibm-dmc-admin@sha256:ca74db8145523ae445cb631aec179fc2c1a9c191a56f8a2bb0ba1980f982f943 \ <local private registry>/cp/cpd/ibm-dmc-admin@sha256:ca74db8145523ae445cb631aec179fc2c1a9c191a56f8a2bb0ba1980f982f943

Once you do skopeo copy, you can run the patch command to update the dmc CR:

oc patch dmc data-management-console --type merge -n '<namespace>' -p '{
  "spec": {
    "image_digests": {
      "admin": "sha256:ca74db8145523ae445cb631aec179fc2c1a9c191a56f8a2bb0ba1980f982f943"
    }
  }
}'

The new admin pod should appear shortly. Verify that the admin pod is using the above image.

The service instance is not automatically upgraded when you upgrade Db2 Data Management Console from 4.7.x to 5.0.0

Applies to: 5.0.0

Fixed in: 5.0.1

When you upgrade Db2 Data Management Console from 4.7.x to 5.0.0, the service instance is not automatically upgraded after the dmcaddon upgrade is completed.

As a workaround, after you upgrade Db2 Data Management Console, you must manually upgrade the service instance that is associated with Db2 Data Management Console. Complete the following steps:

Get the Db2 Data Management Console instance name.
```
oc get dmc -n ${PROJECT_CPD_INST_OPERANDS}
```

Edit the Db2 Data Management Console instance.

oc edit dmc {instance-name} -n ${PROJECT_CPD_INST_OPERANDS}

Change the version to 5.0.0.

cat << EOF | oc apply -f -
apiVersion: dmc.databases.ibm.com/v1
kind: Dmc
spec:
  arch: x86_64
  version: 5.0.0
  description: "Data Management Console"
  scaleConfig: small
  storageClass: "YOUR_STORAGECLASS"
  storageSize: 10Gi   
  license:
    accept: true 
    license: Standard   
EOF

Save your changes and exit.

The Db2 Data Management Console fails to load data into Db2

Applies to: 5.0.0 and later

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:

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

The apply-olm command for Db2 Data Management Console fails

Applies to: 5.0.0

Fixed in: 5.0.1

Db2 Data Management Console air-gapped installation fails when you run the apply-olm command.

As a workaround, edit the deployment for ibm-dmc-controller-manager to pull the image for Db2 Data Management Console.

icr.io/cpopen/ibm-dmc-operator@sha256:0c20d03b207ab15402da6ca7df2bb552aafa59c71f868668899142120130d7e8

Limitations

The Database availability widget displays incorrect values for availability percentage

Applies to: 5.0.0 and later

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.0.0 and later

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.