Share This:

With the May 2 2020 TKU, there are some "Special Instructions" to perform after applying the update.  The instructions are documented here:




Q1)  If a customer skips the May TKU entirely, is it still necessary to perform the special instructions?


A1)  Yes. If, for example, a customer updates from April 2020 TKU to July 2020 TKU, the customer needs to perform the special instructions after applying the July 2020 TKU.


Q2)  Does the customer need to continue using the Special Instructions from now on after each TKU Update?

A2)  No. These instructions are one-time-only.


Q3) The instructions are confusing.  Is there something easier?

A3) Yes.  After updating to the May 2020 TKU, simply reboot the appliance / cluster from the UI:  Administration->Control->'Reboot Appliance' or 'Reboot Cluster'


Q4) Why do we have the special instructions?

A4) This TKU 2020-TKU-May-2 re-release includes an important upgrade for AWS Schedule Scans and Microsoft SQL Server containment relationships

       To correct the existing data, the special instructions are necessary.


Q5) Why is the May 2020 TKU dated May 2 instead of May 1?

A5) Sometimes a TKU is re-released after the initial release.  The initial TKU, May 1 2020, had some problems. 

       The problems were corrected, and the May TKU was re-released as May 2 2020 TKU.

       On the EPD site, the older problematic TKU is removed when the TKU is re-released.



Best Practice:

Customers who download a TKU in advance of Uploading the TKU should check back on the EPD site to see if that TKU has been re-released.



SPECIAL INSTRUCTIONS AFTER APPLYING MAY 2 2020 TKU (or after skipping over May and applying a later TKU):


Once the TKU has been applied the upgrade must be applied. There are two ways to do this.

1. Via the appliance command line:

1.1. Log into the appliance command line as the “tideway” user. For clusters, these steps must be done on each cluster member.

1.2. Restart the “cluster” service:

  • For 11.2 and CentOS/RedHat 6 based 11.3 systems: sudo service cluster restart.
  • For CentOS/RedHat 7 based 11.3 systems: sudo systemctl restart cluster.

1.3. Perform a conditional service start: tw_service_control --start --conditional.  You should see a message “Performing model upgrades”.
        Note: this step only needs to be done on the cluster coordinator machine.


2. Reboot the appliance (for a cluster:  reboot all members of the cluster). Note that simply restarting system services will NOT apply the update.



NOTE:  This blog posting refers only to the on-premise Discovery product.

             Customers on Helix Discovery do not update their TKU's because that is done automatically each month.