Version 1.0.18.0 release notes for M4002-001 model (November 2019)

What's new

Upgrade

You can now use a single file location to store and update your custom Db2 settings: /opt/ibm/appliance/storage/head/db2_config/. The location is persistent over apupgrade and apstop/apstart. For more information, see Preserving custom Db2 configuration settings between upgrades.

Migration tools

• A new script db_build_dictionary is now available in dbtoolkit, which allows you to build a dictionary before migrating data with db_migrate or db_migrate_iias. This improves compression and saves space on the target system. For more information on usage, see db_build_dictionary command.
• Fast Data Movement version 1.0.3 is now available. For more information, see What's New.

Monitoring

Hardware inventory (ap hw -d) may now be retrieved via SNMP interface. This allows you to configure Platform Manager to send hardware metrics and other details to any data center management system via the SNMP interface. The SNMP interface is disabled by default. You can use apsnmpagent command to manage its state. For more information, see Enabling the SNMP interface to retrieve hardware information.

Backup and restore

• During a schema restore, -drop-existing option has to be specified if the schema exists in the database already, to drop and recreate it from the backup.
• In a schema backup, the data files for tables with Spatial and LOBs types can also be compressed using -compress gzip option. db_restore can be used to restore these tables from the compressed data files.
• Backup and restore to tapes using IBM Spectrum Protect is now supported. Installing and uninstalling IBM Tape Device Drivers for Linux can be done using appkg_install command and the tape configurations are persistent upon reboots and upgrades: Installing IBM Tape Device Drivers for Linux.
• IBM Spectrum Protect configuration enhancements:
  • Added a new parameter to manage_tsm to set SSL
  • Enhanced the manage_tsm --dsmsta-setstorageserver script
  • Updated IBM Spectrum Protect configuration checks in db_backup/db_restore, to differentiate between the nodes that are configured for LAN-Free operations vs the nodes that are configured for LAN-Based operations.
  • In db_backup, updated -sessions option to allow up to 6 sessions to perform a backup to IBM Spectrum Protect using -tsm option.

Components

When you migrate from other databases, you can now use IBM® Database Conversion Workbench 4.0.28 - see Release Notes for details.

Resolved issues

• Backup and restore:
  • For a given backup path, updated db_backup to only change permissions on the directories created by the script, leaving the permissions of the existing directories unaltered.
  • During a schema backup, modules and their aliases will be backed up. And during a restore, these objects will be left unaltered if they do not exist in the backup.
  • Updated db_backup and db_restore to limit the number of processes spawned during a schema backup or a restore.
  • For multi-table restore, updated -tablefile option to handle empty lines in the file that has the table names to restore.
  • db_backup now uses schema size instead of the database size to check if the given path has enough space for the schema backup.
  • Updated checks for schema backups: when multiple paths are specified with a comma (,) and no space separator is used, then these paths are now parsed correctly as multiple paths instead of a single path.
  • For a schema backup, the trigger and schema objects' ownership as well as the ownership type is now backed up. And during a restore, the ownership of these objects will be restored to its original owner.
  • All the backup directories will be owned by db2inst1 user and database admin group to allow non-bluadmin users to access the backup. A warning will be displayed instead of an error if db_backup fails to change the ownership on the backup directories to:

    db2inst1 : {admin_group}

  • Fixed a bug in db_restore, to allow restores when a table has the same name as the schema.
• The list of Red Hat CVEs patched in 1.0.18.0 release:

  CVE-2019-3839 CVE-2019-2602 CVE-2019-2684 CVE-2019-2698 CVE-2018-9568 CVE-2018-17972 CVE-2018-18445 CVE-2019-6974 CVE-2019-7221 CVE-2018-12126 CVE-2018-12127 CVE-2018-12130 CVE-2019-11091 CVE-2018-5743 CVE-2019-10132 CVE-2014-3565 CVE-2019-9636 CVE-2016-10745 CVE-2019-5953

Limitations

Known issues

Security

Using IBM® Security Key Lifecycle Manager (ISKLM) is not supported.

Backup and restore

• EMC NetWorker is not supported.
• Backing up with IBM Spectrum Protect (TSM) is not supported from the web console. You can use command line (db_backup) instead.
• Backup to TSM fails with SQL2033N An error occurred while accessing TSM during the processing of a database utility. TSM reason code: "12".
• Issue with object permissions: the backup and restore of schema results in ownership changes to objects within the restored schema. After a restore, objects ownership includes both, db2inst1, and the original owner.
• db_backup size check might cause incremental backups to fail even if there is enough space for the incremental backup.

Memory issues on degraded systems

On degraded systems (systems with one node down) memory issues can arise after failover making the database unavailable.

Web console

When you select Connect > Download Tools > Database Support Tools, the link to download spark-submit.sh script is not working.

apdiag command issues:

• When running apdiag, network/ethtool fails due to error Settings for br0: No data available.
• The apdiag collect --sets hw_logs command output is missing FFDC logs.

  Workaround

  Run the following command to gather FFDC logs:

  apdiag collect --sets hw_logs --components hw/node/log_ffdc

• The apdiag collect command fails when specifying nodes, for example:

  apdiag collect --components hw/node/log_ffdc --nodes node0101 node0103

  Workaround

  Specify nodes as in the following example:

  apdiag collect --components hw/node/log_ffdc --nodes node0101-fab node0103-fab