The SAS®  Embedded Process for Teradata (EP) package contains a special file, <rpm_name>.pkf, which is used with the Teradata Parallel Upgrade Tool (TDput) package management utility. The .pkf file is incorrectly named in the sas-sepcoretera-16.0.1 and the sas-sepcoretera-17.0.0 versions of the EP.

Because the .pkf file name does not match the EP package name, TDput does not include the --nopostun flag under the following conditions:

• the EP update is done from the prior version, sas-sepcoretera-16.0.0
• the update is to either sas-sepcoretera-16.0.1 or sas-sepcoretera-17.0
• the update is performed using the Teradata Parallel Upgrade Tool (TDput)

Without that flag, the RPM calls the postuninstall script for the prior EP version, which results in all of the newly installed files being removed. The RPM package manager thinks that the sas-sepcoretera was installed, but the /opt/SAS directory does not contain any files.

The workaround is for the Teradata support person who is performing the EP install to do one of the following:

• Manually remove the existing EP before installing the new EP:
  1. Remove the EP on all nodes using the following command:

2. Install the new EP using TDput.

• Not use TDput to update the EP:
  1. Manually copy the EP RPM to all Teradata TPA nodes.
  2. Manually update the EP package using the following command:

These workarounds are similar to the procedure that must be used when updating the Teradata EP from an older version with a different RPM name (tkindbsrv or sepcoretera) to a new RPM name (sas-sepcoretera).