Version 102 of the IBM: DB2 PowerPack includes updates to the sample SOAP/XML credentials that are included in the PowerPack, as well as updates to the PowerPack's Dynamic Applications.
- Minimum Required SL1 Version: 10.1.0
Before You Install or Upgrade
Ensure that you are running version 10.1.0 or later of SL1 before installing IBM: DB2 version 102.
For details on upgrading SL1, see the appropriate Release Notes.
Installation or Upgrade Process
To install version 102 of the IBM: DB2 PowerPack, perform the following steps:
By default, installing a new version of a PowerPack will overwrite all content in that PowerPack that has already been installed on the target system. You can use the Enable Selective PowerPack Field Protection setting in the Behavior Settings page (System > Settings > Behavior) to prevent the new version of the PowerPack from overwriting local changes for some commonly customized fields.
If you are currently using the Dynamic Applications in this PowerPack to monitor devices, collection errors might occur for one or two polling cycles during the installation of a new version. To prevent collection errors during an upgrade, you can optionally disable collection for monitored devices before performing the following steps and re-enable collection after the upgrade.
To install this PowerPack:
- Familiarize yourself with the Known Issues for this release.
- See the Before You Install or Upgrade section. If you have not done so already, upgrade your system to the 10.1.0 or later release.
- Download the "IBM: DB2" version 102PowerPack from the Support Site to a local computer.
- Go to the PowerPack Manager page (System > Manage > PowerPacks). Click the menu and choose Import PowerPack. When prompted, import "IBM: DB2" version 102.
- Click the button. For details on installing PowerPacks, see the chapter on Installing a PowerPack in the PowerPacks manual.
See the manual Monitoring IBM DB2 for instructions on using the new PowerPack.
Features
Version 102 of the IBM: DB2 PowerPack includes the following features:
- Dynamic Applications to discover, model, and monitor performance metrics and collect configuration data for IBM Db2 devices
- Event Policies that are triggered when Db2 devices meet certain status criteria
- Example Credentials that you can use to connect to IBM Db2 databases and instances
- A Run Book Action and Run Book Automation policy for aligning Dynamic Applications
- A device dashboard to display information about Db2 instances
Enhancements and Issues Addressed
The following enhancements and addressed issues are included in version 102 of the IBM: DB2 PowerPack:
- The example SOAP/XML credentials that are included in the PowerPack were updated to add logic that deletes extra white space before and after the colon (:) in the credential headers. If you want to include paths with white spaces in the credential, surround the path with double quotes after the colon. For example: <base_db2_path:"/opt/folder name/program files">
- The "DB2 Soap with SSH Example" credential was updated to support the inclusion of a database username and password. This enables the Dynamic Applications in the PowerPack to successfully collect data even when the corresponding SSH/Key credential used includes only a PEM key and no password, as SL1 can now obtain the username and password from the SOAP/XML credential. If the SOAP/XML credential does not contain a username and password, then the Dynamic Applications use the credentials provided in the SSH/Key credential.
- A new "IBM: DB2 EE" Execution Environment was added to the PowerPack, and all Dynamic Applications in the PowerPack were updated to use that Execution Environment.
If you are upgrading from an earlier version of the PowerPack, you must be using the minimum required platform version or later to ensure that the Dynamic Applications in the PowerPack update to use the new Execution Environment.
- An issue was addressed that was causing exceptions to occur due to input failures in the execution environment when running Dynamic Applications if a new version of the "sl_connex" library was present on the system.
- An issue was addressed that was causing errors when running the "IBM DB2: Dynamic Application Alignment" Run Book Automation policy. With this update, the Run Book Automation works as expected and Dynamic Applications are aligned successfully.
- An issue was addressed that was causing credential information to be exposed in plain text in the collector log file for users who were running earlier versions of the PowerPack. With this update, this information is no longer exposed in the log. (Case: 00166665)
Known Issues
The following known issues affect version 102 of the IBM: DB2 PowerPack:
- This PowerPack does not currently support Military Unique Deployment (MUD) systems.
- When using the IBM DB2 Power Pack, some errors are logged to the collector syslog due to missing permissions. These errors will not cause any collection issues, but can be bothersome if you are monitoring the syslog. To clean up the errors, run the following commands on the collector you will be using to monitor your DB2 servers:
sudo chmod o+w /usr/lib64/python2.7/site-packages/clidriver/
sudo chmod o+w /usr/lib64/python2.7/site-packages/clidriver/cfgcache/conlic.bin
- For Linux and Unix users, the user profiles that you create on the database will likely need to use a shell. If that is the case, Linux users should use Bash and Unix users should use KornShell. You should not use Shell (sh) as the user shell, as doing so could result in shell-related errors appearing in the Device Log.