Upgrade Instruction for Data Server Manager v2.1.5 Interim Fix

Content List

Problem Description

TS000954460

When installing IBM Data Server Manager (DSM) version 2.1.5 on a windows operating system, an error such as "<install_path> not recognized" is generated if the specified installation directory path contains spaces. This error is reported when executing some of the *.bat files that are located within the <install_path>/bin folder.

TS000153515

An issue has been seen where, after migrating a DSM instance from version 2.1.3 to version 2.1.5, if the connection name contains "." or " ", the user cannot view the results for the corresponding jobs.

TS000124569

An issue has been seen where, after migrating a DSM instance to version 2.1.5 or to version 2.1.5 interim fix, historical package cache data is not collected.

TS000126550

An issue has been seen where, after migrating a DSM instance to version 2.1.5 or to version 2.1.5 interim fix, an error such as "ProcessRunner.java:95" is reported repeatedly in the DS_System.0 log.

TS000138756

The java file "jackson-databind" that is packaged with DSM version 2.1.5 requires an update, to address specific security vulnerabilities such as "Insecure Deserialization Vulnerability (CVE-2017-7525, CVE-2017-17485, CVE-2018-5968)".

TS000108261

The function that evicts idle connections from the connection pool is not enabled for the Apache connection pool. This results in timeout issues when attempting to borrow an idle connection after a long period of time.

37361,442,000

When attempting to EXPLAIN a query based on RUNSTATS recommendation, an error is generated if the recommended column does not exist in the table that is being queried.

TS000101189

An issue has been seen where, after migrating a DSM instance to version 2.1.5 or to version 2.1.5 interim fix, higher CPU usage is detected on the DSM server.

TS000126550

An issue has been seen where, after migrating a DSM instance to version 2.1.5 or to version 2.1.5 interim fix, in a Db2 pureScale environment configured for HADR, an increased number of connections are created to the repository database.

TS001023867

An issue has been seen where, when the timeout setting in a user-defined alert schedule fails, alerts are generated erroneously and continuously.

RFE#112966

Implement DSM privilege assignment by using Db2 role with UDF.

RFE: https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=112966 

Contents fixed for IDAA

1. Mask the Save trace function (FTP) for IDAA traces for GDPR compliance. 
2. Monitor functionality availability for v5 IDAA.
3. Replication enablement for v7 IDAA.
4. Issues related to repository for IDAA components in DSM.

Content List

Problem Description

TS000100476

1. An issue has been seen where, when two instances of IBM Data Server Manager (DSM) are installed on a UNIX system, using two separate user accounts, the last-created user cannot log into DSM.
2. An issue has been seen where, when two instances of DSM are installed on the same system, running a status.sh shell script on one instance to determine the status of a stopped instance returns a SERVER STATUS: ACTIVE value.  This should return an INACTIVE value.
3. An issue has been seen where some JVM options used by DSM do not include the equals (=) operator between keys and values.
   For example, the option Dhttps.protocols=SSL_TLSv2 is appearing as Dhttps.protocolsSSL_TLSv2.
   As a result, any functions using these JVM options become invalid.

TS000096799

An issue has been seen where, after migrating a previous version of DSM to version 2.1.5, email notifications are not sent when alerts are generated.

TS000108251

An issue has been seen where, when using an SMTP server for DSM user authentication, after migrating a DSM instance to version 2.1.5, operations fail to generate email notifications when thresholds have been hit.

17764,999,000

An issue has been seen where, when performing an LDAP search from DSM V2.1.5, to determine the final list of DSM users and their privileges, hitting an LDAP Size Limit constraint will cause the search to fail. 

TS000126550

An issue has been seen where, after migrating from DSM V2.1.4 to V2.1.5, the DS_System.0 log is spammed with the error message ERROR   ProcessRunner:run failed.

Miscellaneous fixes

1. The credential checking time/interval setting does not take effect when manually changed. When the ID/PW used to connect to a database become invalid, DSM will continuously try to use the wrong ID/PW to connect to the database.
2. If a user attempts to log into DSM before all plugins are started, DSM will reject the login attempt.
3. If a user attempts to run a SQL statement that is larger than 1 MB from within the SQL Editor, the process will hang.

TS000100476

1. An issue has been seen where, when two instances of IBM Data Server Manager (DSM) are installed on a UNIX system, using two separate user accounts, the last-created user cannot log into DSM.
2. An issue has been seen where, when two instances of DSM are installed on the same system, running a status.sh shell script on one instance to determine the status of a stopped instance returns a SERVER STATUS: ACTIVE value.  This should return an INACTIVE value.
3. An issue has been seen where some JVM options used by DSM do not include the equals (=) operator between keys and values.
   For example, the option Dhttps.protocols=SSL_TLSv2 is appearing as Dhttps.protocolsSSL_TLSv2.
   As a result, any functions using these JVM options become invalid.

TS000096799

An issue has been seen where, after migrating a previous version of DSM to version 2.1.5, email notifications are not sent when alerts are generated.