Version 1.0.14.0 release notes (December 2018)

What's new

Backup, restore, disaster recovery

• You can now perform more granular backups and restores by using the db_backup and db_restore commands:
  • You can perform schema-level backups and restores by passing the schema name to the db_backup and db_restore tool by using the [-schema <schema_name>] parameter. If you omit the schema argument, the tools back up and restore the entire database.
  • You can perform table-level restore by passing both schema and table name to the db_restore utility, by using the [-schema <schema_name> [-table <table_name>]] parameters. If the schema argument is omitted, db_restore performs database-level restore.
  For more information, see Backing up and restoring a database, schema, or table or watch IAS Granular Backup and Restore.
• IAS is now integrated with IBM Data Replication for Db2 Continuous Availability, which enables high-speed data replication for business continuity across IBM Integrated Analytics System configurations. It offers near real-time asynchronous data replication from a primary database server to one or more target database servers. You can access the new replication feature in the web console, by selecting CONTINUOUS AVAILABILITY > Data Replication. You can use a 90-day free trial license to test the capability. For more information, see: IBM Data Replication for Db2 Continuous Availability.
• The command line arguments of the apdr disaster recovery tool changed to make it more consistent and user friendly. Run apdr -h to see the updated options and command syntax, or read apdr command for more information.

Data migration

You can now migrate tables between two IAS appliances by using the db_migrate_iias tool available in dbtoolkit. For more information, see Migrating data between two appliances.

Software administration

The appkg_install command now provides the --list option, which lists all packages that are installed with the tool on your system.

Usage:

appkg_install --list
+---------------------+-------------------------------------+
| Vendor              | Installed Package                   |
+---------------------+-------------------------------------+
| EMC                 | EMC NetWorker Solution              |
+---------------------+-------------------------------------+

For more information on the tool, see Installing third-party software with appkg_install command.

Reliability and serviceability

The apdiag tool now allows simpler form of time specification with --atime and --btime options. Before IAS Version 1.0.14, the only supported timestamp format was YYYY-mm-dd HH:MM:SS. The new available format is [HDW] where you specify a number of hours, days, or weeks respectively. For example, --atime 8H specifies that content from the past 8 hours is gathered. For more information, see Running diagnostics by using the apdiag command.

Security

You can now enable encryption of the appliance storage on IBM FlashSystem® 900 devices, and manage the encryption keys using IBM Security Key Life Cycle Manager (ISKLM). You use a platform utility apesklm to manage encryption and keys. For more information, see Storage hardware encryption on systems with integrated rack.

Platform Manager

• Maintenance mode was added to platform management. When in maintenance mode, the platform is monitored but all management actions are suspended: no alerts or PMRs are open, and no invasive actions are performed by platform manager. Maintenance mode is managed by using the ap maintenance command. For more information, see ap commands.
• SNMP traps can now be generated for new alerts. They can be generated along with existing alert actions - emails, PMRs, or by themselves. Configuration parameters are set by using ap config command. For more information, see ap config command.
• You can now disable Db2 Warehouse application with the ap apps disable command, similarly to other monitored applications. As a result, the database is stopped and it cannot be started by running apstart. When you run ap apps disable dashDB, the only way to start the database is by running ap apps enable dashDB. When running apstart, you get the following warning:

  [root@node0101 ~]# apstart
  Successfully activated platform. Warning: DashDB disabled, will not be started

  When running apstart -a, you get the following warning:

  
  DashDB disabled, cannot start application

• The Call Home container is now stopped during full apstop procedure or apstop -p -m.
• Alerts for top-level components now aggregate issues from subcomponents for some component types. Error data for these subcomponents is present in alert details.
• Sample script with usage of REST API to run a custom action or a script on new alerts is now available in /opt/ibm/appliance/platform/management/samples/pm_alerts_processor_sample.py. More information can be found inside the script file).

Web console

• The menu now includes CONTINUOUS AVAILABILITY where you can manage data replication and data backup and restore.
• A new widget is now available on the personalized home page for data replication.

Components

You can use IAS with DSX Local Version 1.2. DSX is not pre-installed and IBM Support must be involved in the installation process. For more details, see What's new

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

Resolved issues

• Fixed the problem with permissions for deleting backups and backup directories:
  • Added group write permissions to db2iadm1 user group on the backup directories.
  • Added group read and write permissions to db2iadm1 user group on backup files.
• FSN firmware is upgraded to 1.5.2.1 to fix the incorrect multibit ECC error during code load.

  The FSN900 DRAM technology consists of two dies in a single package, where each die is a different memory rank. Micron is calling this technology TwinDie. The issue is that the Xilinx memory controller is loading the wrong values into the top rank. The wrong values affect the DRAM write path and thus causes the incorrect multibit ECC during code load. The code is loaded correctly but due to this issue the ECC is incorrect.

Known issues

• Missing terminal server network connection can potentially cause a crash when running sys_hw_diags power.

  Workaround:

  Check terminal server network connections and re-run the diagnostics.

• Sort heap Db2 error might occur during schema backup. The problem is caused by the configured Db2 SORTHEAP value. db_backup performs various operations which allocate memory that is based on the configured SORTHEAP/SHEAPTHRES values. There are several factors that can impact how much memory is needed, for example, accessing column-organized tables. If you notice these errors, contact IBM Support to have the value increased. For more information, see https://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.1.0/com.ibm.db2.luw.admin.config.doc/doc/r0006014.html.
• Unable to take automated snapshots after running apdr setup.

  Workaround:

  1. Confirm that apdr setup completed successfully by running apdr setup -s.
  2. Run the following commands on both the primary and secondary systems to make AFMDR ready for replication:

     apdr disable
     apdr enable

     For more information, see Setting up file system replication based DR solution on IAS.
• When running schema backup, the following error causes the backup to fail:

  ERROR: The backup path is missing from EXTBL_LOCATION. Add your backup path to the database configuration.

  Contact IBM Support to have the external storage mount point added to EXTBL_LOCATION.
• Schema backups are only available via command line. The web console might list schema backups in restore options, but if you choose one and try to restore, an error is displayed. Use only the command line to restore schemas.
• IPv6: If you are planning to use IPv6, call IBM Support for assistance in configuring the system.
• Tiered storage systems only: Disk Storage Node (DSN) firmware update fails if upgrading to 1.0.14.0 from a release older than 1.0.12.0.
  Example failure output:

  -------------------------DSN CHECKING FIRMWARE STATUS--------------------------
  Canister firmware check DSN(s) (4 running)                               [DONE]
  Drive firmware check DSN(s) (4 running) (3 running)                      [DONE]
  ------------------------------DSN FIRMWARE UPDATE------------------------------
  The following dsns need to have their canister firmware updated :
  All Disk Storage Nodes in the system
  ---------------------------CANISTER FIRMWARE UPDATE----------------------------
  Updating the firmware on the DSN(s) (4 running)                          [DONE]
  Rack 2 Disk Storage Node 4 Failed to copy files to canister              [FAIL]
  Rack 2 Disk Storage Node 1 Failed to copy files to canister              [FAIL]
  Rack 2 Disk Storage Node 3 Failed to copy files to canister              [FAIL]
  Rack 2 Disk Storage Node 2 Failed to copy files to canister              [FAIL]

  Workaround:

  1. Allow the upgrade to fail.
  2. Run the upgrade again with the --skip-firmware flag to update firmware on all components except the DSN.
• When running apupgrade to start the upgrade on the appliance, Platform Manager might time out resulting in node0101 (or current head node) rebooting, or, in some cases, powering itself off.

  Workaround: Restart the database with apstop -p --service and apstart -p before upgrading to avoid this condition.