Known issues and limitations for Db2 Data Management Console

Known issues

After an upgrade, the load log directory is cleared and cannot be retrieved

Applies to: 4.7.0 and later

After an upgrade, the Db2 Data Management Console load log directory is cleared and cannot be retrieved.

To know more about the workaround, see Load logs are cleared after upgrade

Redis pods fail to start if quota is applied to namespace but limitrange is not set

Applies to: 4.7.0

Fixed in: 4.7.2

Redis pods cannot start if quota is applied to namespace but limitrange is not set. An error occurs, because Redis init containers do not have limits.cpu, limits.memory, requests.cpu, or requests.memory.

As a workaround, apply limit range with defaults for limits and requests. Modify the namespace in the following yaml to the namespace where Cloud Pak for Data is installed:

apiVersion: v1
kind: LimitRange
metadata:
  name: cpu-resource-limits
  namespace:  ${PROJECT_CPD_INST_OPERANDS}  #Change it to the namespace where Cloud Pak for Data is installed
spec:
  limits:
  - default:
      cpu: 300m
      memory: 200Mi
    defaultRequest:
      cpu: 200m
      memory: 200Mi
    type: Container

Redis pods fail to start after you run a backup and restore

Applies to: 4.7.2

Fixed in: 4.7.3

Redis pods might fail to start after you run a backup and restore on Db2 Data Management Console.

To know more about the workaround, see Redis pods fail to start.

Explain pods fail to start after you restart the pods

Applies to: 4.7.2

Fixed in: 4.7.3

Db2 Data Management Console explain pods fail to start after you restart the pods.

To know more about the workaround, see Explain pods fail to start.

Limitations

Database availability widget displays incorrect values for availability percentage

Applies to: 4.7.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.