Troubleshooting Updates and Service Packs

Expiring Old Updates to Save Disk Space on your Computer

When an update is installed, the old version of the binary is replaced with a new one. When there are many updates or Service Packs installed on the computer, these old binary versions may take up a large amount of space on the computer. Hence, to save space on your client computers, you can configure nExpireUpdates registry key. If there has been no install activity during the specified number of days, once you restart the services, this key will remove all updates in the updates folder. Thereafter, the existing updates on the computer cannot be uninstalled.

Use the following steps to configure this capability on each client computer:

1. From the CommCell Console, navigate to Client Computers.
2. Right-click the <Client> you want to configure, and then click Properties.
3. Click the Registry Key Settings tab.
4. Click Add.
5. In the Name field, type nExpireUpdates.
6. In the Location field, type UpdateFlags.
7. For Windows, in the Type list, select REG_DWORD.

   For Unix, in the Type list, select Value.

8. In the Value field, type the number of days after which the update information must be removed from the computer.

   It is recommended that you set the value to 20 days.

9. Click OK to save the key.
10. Click OK.

Applying Updates for the Content Indexing Engine

Consider the following for applying updates in computers with the Content Indexing Engine software:

Updates for the Content Indexing Engine can be installed interactively - Automatic Update are not supported. Use the following sequence to install the updates on these computers:

1. Verify that no Content Indexing jobs are in progress or scheduled to occur while installing the updates. If Content Indexing jobs are running or scheduled to run, either install the update at another time or kill the job in the Job Controller and disable all Content Indexing jobs from the CommServe Properties (Activity Control) dialog box in the CommCell Console.
2. First, stop the Content Indexing Services in all the Index/Storage Nodes and then stop the services in the Admin Node.

   Follow the below procedure to stop the services:

   1. Log on to the computer containing the Content Indexing Engine software.
   2. Click Start menu, and then click Run.
   3. Type services.msc in the text field and press enter.
   4. From the services.msc console, Right-click the FAST ESP service, and then click Stop.
3. Install the necessary Updates.
4. First, start the Content Indexing Services in the Admin Node, and then start the services in all the Index/Storage Nodes.

   Follow the below procedure to start the services:

   1. Log on to the computer containing the Content Indexing Engine software.
   2. Click Start menu, and then click Run.
   3. Type services.msc in the text field and press enter.
   4. From the services.msc console, Right-click the FAST ESP service, and click Start.
5. Enable Activity Control if it was disabled and re-run the job if necessary.

Applying Database Updates

• To allow individual database updates to be installed without stopping software services, create and enable the nForceApplyDBUpdates registry key. This is especially useful in a clustered environment. Note that this registry key (even when enabled) does not affect non-database updates.
• When installing updates on a DB2 client, if the database configuration parameter LOGARCHMETH1 is set to VENDOR, you need to stop the DB2 services before installing updates.

How To Recover from Update Install Failures?

Use the following steps to recover from an Update Install failure.

1. Uninstall Updates from a specific Client.

   See Uninstall Updates for more information.

2. Re-Install the Updates.

   See Interactive Install for more information on installing update interactively.

   See Automatic Updates for more information to setup components to automatically receive updates.