Version 1.0.18.1 release notes (August 2019)

Resolved issues

• A number of issues that were related to the upgrade procedure were fixed:
  • Fixed the issue with NodeOS upgrade fail due an rpm package installed by DSX.
  • To avoid breaking GPFS during upgrade, run a pre-check mmccr check command on all nodes to verify that GPFS is in a consistent state before running an upgrade. The command should return the following output:

    [root@node0101 ~]# mmccr check
    mmccr check results:CCR Client initialization succeed
    Check CCR authorized key file succeed
    Check CCR cached directory and file succeed
    Check both CCR paxos files succeedT

    To resolve the issue, run the following command on the node where the command mmccr check failed:

    mmchcluster --ccr-disable
    mmsdrrestore
    mmchcluster --ccr-enable

    Then, run mmccr check again to confirm that the CCR error is resolved.
  • Fixed the issue with ROW systems: When upgrading row organized system, apinit was changing dashDB.env file parameters from row to column parameters, and the environments variable was changed.
  • Fixed the issue with NodeOS upgrade resulting in the following error:

    NodeosUpgrader.install : nodeos:NodeosUpgrader.install:Fatal Problem: The Node OS rpm is not correctly installed/configured.
    This error requires manual intervention to resolve. Please contact IBM Support.

Known issues