Version 1.0.9.0 release notes (June 2018)

Web console

• Real-time arrangement of the layout on the home page. You no longer need to use the Personalize sidebar. Instead, you can rearrange the widgets on the home view directly.
• On the Hardware widget, you can now drill down to the Hardware page and individual rack position.
• Visual improvements are introduced to the personalized home page and its widgets, such as tooltips, padding, and layout.
• The web console now runs in a stand-alone container instead of being a part of the Db2® Warehouse container. The IIAS console no longer needs to be out of service during Db2 Warehouse maintenance. For example, when Db2 Warehouse is upgraded, the system administrator can still monitor system hardware and software in the console. The console URL and its functions don’t change. The web console port is changed from 8443 to 11089, but port redirection is used with the old URL.
  Note: Network settings must be changed to open port 11089. You might also need to open the new port on your firewall.

Backup and restore

• IBM has certified Dell EMC NetWorker Module for Databases and Applications for integration with Integrated Analytics System for backup and restore operations. Contact support for more information on installation and configuration.
  • A new option -emc is added to the db_backup command to run all types of backups (online, offline, incremental) to EMC, if it’s installed and configured.
    Usage:

    db_backup [-emc] [-type]

  • A new option -emc is added to the db_restore command to allow users to run all types of restores (online, offline, incremental) from the backups done to EMC.
    Usage:

    db_restore [-type] [-timestamp] [-emc]

  • A new script setup_nmda_cfg is now available so that you can set the configurations for both the NMDA Db2 configuration file (nmda_db2.cfg), and to the NMDA Db2 transaction logs configuration file (nmda_db2_tlogs.cfg).

    For more information, see Configuring EMC NetWorker, or watch the video tutorial at https://www.youtube.com/watch?v=RSyvmCwIWTU.

• Added a check to validate that enough space is available in the specified directory before you run a backup.
• Added a check to validate time stamp of the backup images in the specified path before you run a restore operation.
• Added a check to verify whether TRACKMOD is set to YES in Db2 configuration settings before you run the online or incremental backup.

Platform management

• A new command is now available to manually close FSP events.

  FSP events are now reported as issues (stateful alerts) by Platform Manager. These issues stay open until the particular FSP events are manually closed by the operator.

  To close an FSP event with ID ZZZ generated on node Y in HA domain X, the following command can be used: ap elog close hadomainX.nodeY ZZZ, for instance:

  ap elog close hadomain1.node2 0x504BDCB8

  It’s also possible to close all the FSP events for a specified node by using all in place of ID, for example:

  ap elog close hadomain1.node3 all

• The .tar file with logs that are collected for an alert now includes information about SMTP configuration and alerts rules.

Performance and compatibility

Improved Insert and Update performance on logged temporary tables.

Components

When you migrate from other databases, you can now use Database Conversion Workbench Version 4.0.15. See: https://www.ibm.com/developerworks/community/wikis/home?lang=en-us#!/wiki/W252c18693c7e_432e_ad40_03c3417db6b1/page/Release%20Notes.

Resolved issues

• Fixed an issue where Platform Manager requested an unnecessary node power cycle due to internal problems related to REST communication with an agent that is running on that node.
• Fixed an issue with a node not responding to shut down request sent by apstop command. The command failed with Problem occurred: Timeout exceeded when waiting for deactivation message.
• Fixed an issue where the Db2 Warehouse container on nodes was restarted by Platform Manager when GPFS NSDs related to cool file systems of tired storage weren’t available.
• Fixed an issue with alert 410 generated during software update of Call Home service, about not being able to stop Call Home.

  Fixed an issue where a multi-HA domain system got stuck in RECOVERING state if all Db2 Warehouse containers in the first HA domain were restarted as part of a GPFS file system recovery.

Known issues

Applying House IP address configuration fails in some situations.

When an installation or switch/ node replacement happens in a multiple HA Domain system, the House IP address configuration might fail.

The following situations are the trigger:

• An installation with two HA Domains and House IP addresses only on the Fabric Network
• An installation with 4 (or more) HA Domains and House IP addresses only on Management or only on Fabric Networks

This issue affects all releases that support multiple High Availability Domains. Single and fractional HA Domain systems aren’t impacted. Systems with House Addresses on both Fabric and Management networks aren’t impacted. Tiered Storage isn’t relevant to this issue.

Workaround:

To work around the issue, an adjustment in the House IP address configuration can be done. After configuring the addresses, choose Save Configuration and Exit (without applying) from the main menu. The configuration meta information is saved to the storage so it can be applied later. Then, run

/opt/ibm/appliance/platform/comms/tools/apnetApplySetup.py -t node

and

/opt/ibm/appliance/platform/comms/tools/apnetApplySetup.py -t <switch_type>

The <switch-type> is based on which network has the House IP addresses:

• If the patch panel interface that is used for the House is eth0, eth1, eth2, eth3, or any mbond, the <switch-type> is mgtsw.
• For interfaces eth4-eth11, and all fbond possibilities, the <switch-type> is fabsw.

When both command executions complete, the House IP addresses are configured.

Three consecutive unsuccessful login attempts result in locking out the platform user

The platform users get permanently locked out after 3 consecutive unsuccessful login attempts within 15 minutes, on the systems provisioned with RHEL 7.4 (v1.0.6, v1.0.7, v1.0.8) and then upgraded to the latest version.

Workaround:

1. Log in as root user.
2. Run the following command:

   authconfig --disablefailloc --update

Note: If you upgrade from versions 1.0.6, 1.0.7, 1.0.8 to 1.0.9 or above, to run the authconfig command you must be logged in as root. If you do not have the root access, please contact IBM Support.