Upgrading from or Reinstalling from the July 2015 Release of SAS 9.4 and Later

Overview
Removing the SAS Embedded Process Parcel Using Cloudera Manager
Removing the SAS Embedded Process Stack Using Ambari

Overview

The version number of the parcel or stack is calculated by the SAS Deployment Manager with the actual version of the installed product that you selected to deploy. You cannot deploy a parcel or stack that has the same version number as a parcel or stack that was previously deployed. The SAS Deployment Manager assigns a new version number or you can specify your own.
You can either deactivate the existing parcel or stack or remove it before upgrading or reinstalling. If you want to deactivate the existing parcel or stack, use your cluster manager to deactive the parcel or stack, and continue with the installation instructions in Using the SAS Deployment Manager to Deploy the SAS Embedded Process Parcel or Stack to the Cluster.

Removing the SAS Embedded Process Parcel Using Cloudera Manager

CAUTION:
If you are using SAS Data Loader for Hadoop, you should remove the Quality Knowledge Base (QKB) and the SAS Data Management Accelerator for Spark from the Hadoop nodes before removing the SAS Embedded Process.
Removing the SAS Embedded Process removes the scripts that are used to remove these products. For more information, see “Removing the QKB” and “Removing the SAS Data Management Accelerator for Spark” in the SAS Data Loader for Hadoop: Installation and Configuration Guide.
To remove the SAS Embedded Process Parcel using Cloudera Manager, follow these steps:
  1. Start Cloudera Manager.
  2. Stop the SAS_EP service:
    1. On the Home page, click the down arrow next to SASEP service.
    2. Under SAS EPActions, select Stop, and click Stop.
    3. Click Close.
  3. Delete the SASEP service from Cloudera Manager:
    1. On the Home page, click the down arrow next to SASEP service.
    2. Click Delete.
    3. Click Close.
      The SASEP service should not appear on the Homethen selectStatus tab.
  4. Deactivate the SASEP parcel:
    1. Navigate to the Hoststhen selectParcels tab.
    2. Select Actionsthen selectDeactivate.
      You are asked to restart the cluster.
    3. Click Cancel.
      Note: Restarting the cluster is not required. If you want to restart and a rolling restart is available on your cluster, you can choose to perform a rolling restart instead of a full restart. For instructions about performing a rolling restart, see the Cloudera Manager documentation.
    4. Click OK to continue the deactivation.
  5. Remove the SASEP parcel:
    1. Select Activatethen selectRemove from Hosts.
    2. Click OK to confirm.
  6. Delete the SASEP parcel.
  7. Select Distributethen selectDelete.
  8. Click OK to confirm.
    This step deletes the parcel files from the /opt/cloudera/parcel directory.
  9. Manually remove the ep-config.xml file:
    CAUTION:
    If you fail to remove the ep-config.xml file, the SAS Embedded Process still appears to be available for use.
    Any software that uses the SAS Embedded Process fails.
    1. Log on to HDFS.
      sudo su - root
su - hdfs | hdfs-userid
      Note: If your cluster is secured with Kerberos, the HDFS user must have a valid Kerberos ticket to access HDFS. This can be done with kinit.
    2. Navigate to the /sas/ep/config/ directory on HDFS.
    3. Locate the ep-config.xml file.
      hadoop fs -ls /sas/ep/config/ep-config.xml
    4. Delete the directory.
      hadoop fs -rmr /sas/ep/

Removing the SAS Embedded Process Stack Using Ambari

CAUTION:
If you are using SAS Data Loader for Hadoop, you should remove the Quality Knowledge Base (QKB) and the SAS Data Management Accelerator for Spark from the Hadoop nodes before removing the SAS Embedded Process.
Removing the SAS Embedded Process removes the scripts that are used to remove these products. For more information, see “Removing the QKB” and “Removing the SAS Data Management Accelerator for Spark” in the SAS Data Loader for Hadoop: Installation and Configuration Guide.
Note: You need root or passwordless sudo access to remove the stack.
To remove the SAS Embedded Process stack using Ambari, follow these steps:
  1. Navigate to the SASHOME/SASHadoopConfigurationLibraries/2.4/Config/Deployment/stacks/sasep directory on the client where the SAS software is downloaded and installed.
    cd SASHOME/SASHadoopConfigurationLibraries/2.4/Config/Deployment/stacks/sasep
    The delete_stack.sh file should be in this directory.
  2. Copy the delete_stack.sh file to a temporary directory where the cluster manager server is located. Here is an example using secure copy.
    scp delete_stack.sh user@cluster-manager-host:/mydir
  3. Use this command to run the delete script.
    ./delete_stack.sh <Ambari-Admin-User-Name>
  4. Enter the Ambari administrator password at the prompt.
    A message appears that offers options for removal. Enter one of the options as appropriate:
    • Enter 1 to remove only the ep-config.xml file.
    • Enter 2 to remove a specific version of the SAS Embedded Process. If you enter 2, a list of all the versions that are available for removal appears. You can then enter any of the versions to be deleted.
    • Enter 3 to remove all versions of the SAS Embedded Process.
  5. You are prompted to restart the Ambari server in order to complete the removal of the SASEP service. To remove the SAS Embedded Process, you must restart the Ambari server.
  6. Enter y to restart the Ambari server. The SASEP service is no longer listed on the Ambari dashboard user interface.
Copyright © SAS Institute Inc. All Rights Reserved.
Last updated: February 9, 2017