Version 1.0.8.0 release notes (May 2018)

New features in Version 1.0.8.0 include a personalized home page with configurable widgets that allow you to better monitor and understand the status of the appliance, as well as a new ap apps command.

What's new

Web console
  • You can now personalize your home page to see the status of your database or data warehouse at a glance. Pre-defined monitoring widgets and templates allow you to customize your home page and display only the information that is of interest to you, regardless of your role. Sample templates are available for system monitoring, database monitoring and for troubleshooting. For more information, see Personalizing the console home page.
    Figure 1. IAS personalized dashboard
    The IAS home page with Personalization sidebar
  • The nine new widgets allow you to understand the overall health of the system at a glance and decide which subsystem might require further investigation. Each widget tells a story about one key aspect of the overall system or database. Multiple metrics are available, as well as the ability to fly over or drill down for more details and problem resolution. For more information, see Monitoring the appliance with the web console.
    Figure 2. IAS widget for database responsiveness
    A screenshot of the Database Responsiveness widget
Monitoring
The ap apps command allows you to monitor the state of the applications running on the appliance, such as the web console, or Db2 Warehouse. You can also use this command to enable or disable the selected application. When the application is disabled, platform management monitors its status but no longer starts or stops it automatically. For more information on the command, see ap commands.
Reliability and serviceability
  • Fibre Channel network-related issues that are detected by platform manager are now appended to a single service request (PMR) instead of creating a separate request for every issue.
  • During system startup, the status for Db2 application nodes is now reported as STARTING in ap sw command output. Earlier it was reported as RECOVERING.
Security
You can now use the status option of the ap_external_ldap.pl utility to list the current status of the external LDAP Server and the LDAP server attributes used in platform user authentication. For more information, see Viewing status of the external LDAP server.

Resolved issues

  • Platform Manager no longer reports that the database state is OK when some database services are stopped and as a result, the user cannot connect to the database. Database connections are now monitored and recovery is enabled.
  • Added a check to see whether a backup or restore process is already running when a user tries to run a new backup or restore.
  • A TRACKMOD check is now included for incremental backup. The Track modified pages setting must be set to YES for incremental backup.
  • Platform level backups:
    • Added prechecks for GPFS Cluster Status and GPFS Mounts before Platform Level Backups
    • Renamed apcomms option as apnetworking, and rlockdown option as apsecurity.
  • The db_backup -history and db_restore -history command output no longer shows an error when no records are found in the history. Instead, a relevant message is displayed.
  • Fixed an issue with the external LDAP server configuration. The external LDAP user can now log in to any node having an external IP, and can switch to any of the platform nodes with the valid password.
  • Added a meaningful error message if host, search-base-dn, searcher-dn and ca-cert arguments that are passed to ap_external_ldap.pl are empty.
  • The port number that is passed to ap_external_ldap.pl is now validated, and a meaningful error message is provided if it is not valid.
  • Fixed an issue where an alert about high storage usage (reason code 901) was raised incorrectly (without legitimate reason) on problems with mounting GPFS files system on one of the nodes.

Included components

IBM® Integrated Analytics System includes the following components:
  • Db2 Warehouse Version 2.7.0.
  • DSX Local Version 1.1.2.
  • Apache Spark version 2.1.1.

Known issues

  • Customers that use fabric network connections must not perform automated upgrade themselves. Contact IBM Support for help.
  • After upgrading the NodeOS component, restarting the system might fail. If this issue is encountered:
    1. Run the following command on all nodes:
      /usr/lpp/mmfs/bin/mmbuildgpl
    2. Run apupgrade again.
  • A multi-HA domain system may get stuck in RECOVERING state if all Db2wh containers in the first HA domain were restarted as part of a GPFS file system recovery. The workaround is to run apstop and then apstart.