Limitations and known issues

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

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 database available or not.
If a database contains many tables, query ADMIN_GET_TAB_INFO runs too slow and exceeds the timeout setting (10s). As a workaround, disable the Table invalid option from alert monitoring.
Db2 Data Management Console, the data server type for Db2 on Cloud connection is displayed as IBM Db2. Therefore, for monitoring Db2 on Cloud databases, the console uses the default monitor that is assigned for IBM Db2.
For some Db2 databases, when you view the Top consumers page, the column values are empty. The following error message is displayed.
```
SQL0101N The statement is too long or too complex.
```
This is an issue with the statement heap size for IBM Db2. To learn more on the statement heap size and the symptom of the problem, see stmtheap - Statement heap size configuration parameter.
As a workaround, update the heap size as follows:
1. Determine the current value of the STMHEAP size by using the following command:
```
db2 => get db cfg
SQL statement heap (4KB)                     (STMTHEAP) = 9216
```
2. Increase the size of STMHEAP to a higher value by using the following command:
```
db2 update db cfg for coral using stmtheap
      <size>
```
  For example, to increase the STMHEAP to 27648, run the following command:
```
db2 => update db cfg for coral using stmtheap 27648
DB20000I  The UPDATE DATABASE CONFIGURATION command completed successfully.
db2 => get db cfg
...
SQL statement heap (4KB)                     (STMTHEAP) = 27648
...
```
When Db2 Data Management Console is installed on a Windows system and if windows service is enabled for Db2 Data Management Console, on some systems, the status of Db2 Data Management Console's Windows service might not be synchronized with the actual running status of Db2 Data Management Console.
As a workaround, restart the Windows system, or use the <setup_directory>/ibm-datamgmtconsole/bin/start.bat and <setup_directory>/ibm-datamgmtconsole/bin/stop.bat scripts to control the running status of Db2 Data Management Console.
You cannot run a block of scripts, instead you can use the command line to call and execute a block of scripts.
On a Windows system, for any version of the Db2 database, if the Db2 Data Management Console login password contains special characters such as "N1cetest!", the console fails to connect to the Db2 monitor database by using either grant_mondb_min.bat or verify_mondb_min.bat scripts.
As a workaround, submit the SQL statement in double quotation marks and specify the password in single quotation marks if the password contains special characters.
EasyPrivacy 3rd party filters for uBlock Origin contain generic filters that can cause interface issues or block all API requests /v4/metrics by the monitor. One of the following messages is displayed:
```
Network disconnected
```
```
Error: Please check network connectivity then try again.
```
As a workaround, disable the EasyPrivacy filter and try again.
Db2 Data Management Console does not support AIX® POWER7® compatible systems.
Date formatting issues occur when you export data to a CSV file. As a workaround, change the date format in exported data.
The Monitor page might display an error message similar to the following message:
```
There is an internal error. Please refresh this page if it dose not behave properly.
```
This issue occurs due to the limitation of the Smiley web server to process only five API requests at a time. This error can safely be ignored.
The Data > Application objects > User-defined types page displays data only for Structured and Row user-defined types (UDTs) and does not display data for the following data types.
- Distinct
- Ordinary array
- Associative array
- Cursor
Db2 Data Management Console might fail to start on Red Hat® Enterprise Linux® 9 for IBM z/OS®. As a workaround, do the following steps:
1. Go to ibm-datamgmtconsole/addons/job-scheduler/bin and run the following command:
```
# ./status.sh
```
2. If the result is FAILURE, restart the job server:
```
# ./start.sh
# ./status.sh
```
3. If the status is still FAILURE, check the log file ibm-datamgmtconsole/addons/job-scheduler/logs/nohup.ou for the following error message:
```
...error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory
```
4. If the error message exists, install libcrypt.so.1 s390x package, and restart the job server:
```
# ./start.sh
# ./status.sh
```
  The job scheduler works as expected, if the status is SUCCESS.
Installing Db2 Data Management Console v3.1.10 on AIX 7.2 might fail. For a workaround, refer to this topic.
Db2 Data Management Console v3.1.10 supports only GUI installation on Mac OS. Script installation is not supported.
When you monitor a Db2 partitioned database environment, the Database availability widget in the Summary page might not display the correct value for availability percentage and alerts are not generated when the Network File System (NFS) server is down. As a workaround, you can implement and maintain a highly available solution for the shared file system and use monitor tools to reflect the availability of the file system.
Db2 Data Management Console v3.1.11 does not support GUI installation on Intel Mac systems. As a workaround, Intel Mac system users can install Db2 Data Management Console v3.1.11 by using the docker image.