This section includes the new features and functions included in IBM® Db2® Data Management Console v3.1.8.
- The single query recommendation report now displays the access plan summary and catalog information sections.
- Enhanced user experience to view the tuning recommendations.
- Single query tuning can now be used to run the query and collect actual access path cost information.
- Workload tuning now provides recommendations to convert tables from row stored to column stored organization.
- The single query index what-if analysis now displays the revised access plan graph with the virtual indexes.
For more information, see Tuning.
- Run SQL page now includes a new page My script.
- Users can now view data objects.
- Auto completion feature now provides hints for schema and table names.
- The In-flight executions page, now provides information on the time spent for each execution. The Other wait option provides more details on metrics.
- Users can now view the memory usage at the instance and database level from the new
- To view the memory consumed at the instance level, go to .
- To view all the memory sets and memory pools within each set for a selected database, go to .
The Database time spent page, now provides data at the database level. The All workloads and All user workloads menus now include the Workloads chart that provides the workload breakdown for the current active metrics of the Time spent chart.
Db2 Data Management Console can now monitor a HADR cluster with non-ROS standby. When a failover occurs, the non-ROS standby switches over to the primary and Db2 Data management Console continues to monitor both the primary and standby HADR databases based on their new roles. The console also collects and saves the historical monitoring data of both the primary and standby HADR databases.
- To view and edit the database manager configuration parameters, go to .
- To view and edit the database configuration parameters, go to .
For more information, see Updating configuration parameters.
Enhancement to jobs
- A new Stop button is now available on the Jobs page to enable users to stop the shell jobs that are in the Running state. When the job is stopped completely, the status of the job changes from Running to Stopped.
- Users can now perform the following actions on jobs:
- Send emails to multiple recipients based on the execution status of jobs.
- Delete a job when the execution is still in running status.
- Convert an on-demand job to a scheduled job without recreating the job from start.
Support for JRE upgrade
Db2 Data Management Console now supports upgrading the Java™ Runtime Environment to IBM Semeru Runtime Certified Edition 184.108.40.206.
Support for resetting repository user password
When the Db2 Data Management Console uses repository based authentication and if the password of the repository user is expired, the password can be updated by using a script.
For more information, see Resetting repository user password.
Improvement to alerts
- For stored procedures of custom alerts, an OUT parameter with a data type
INTEGERmust be defined in the script to return the severity of an alert. For example:
DROP PROCEDURE username.db_underutilization_uda_out@ CREATE PROCEDURE username.db_underutilization_uda_out(OUT severity INTEGER) . . END @ CALL username.db_underutilization_uda_out(?) @
- Added a column to the custom alert script to return the script output value on successful execution. In view mode, the custom alert log history displays alert details which now include alert severity and script output.
(;)is now used as the standard delimiter to separate multiple commands in a shell script. For more information, see Creating custom alerts.
- Db2 Data Management Console now enables only the users with the privilege to monitor databases to view and manage alerts. To verify privileges, go to .
Enhancement to dmctop
- Support for Db2 pureScale® statistics at member level.
- Fixes for APARs.