Upgrading from or Reinstalling a Previous Version :: SAS(R) 9.4 In-Database Products: Administrator's Guide, Seventh Edition

Upgrading from or Reinstalling from SAS 9.3

To upgrade or reinstall from SAS 9.3, follow these steps:

Stop the SAS Embedded Process.
```
EPInstallDir/SAS/SASTKInDatabaseServerForHadoop/9.35/bin/sasep-stop.all.sh
```
EPInstallDir is the master node where you installed the SAS Embedded Process.
Delete the SAS Embedded Process from all nodes.
```
EPInstallDir/SAS/SASTKInDatabaseServerForHadoop/9.35/bin/sasep-delete.all.sh
```
Verify that the sas.hadoop.ep.distribution-name.jar files have been deleted.

The JAR files are located at HadoopHome/lib.
For Cloudera, the JAR files are typically located here:
```
/opt/cloudera/parcels/CDH/lib/hadoop/lib
```
For Hortonworks, the JAR files are typically located here:
```
/usr/lib/hadoop/lib
```
Continue the installation process.

For more information, see Using the SAS Deployment Manager to Create the SAS Embedded Process Parcel or Stack.

Upgrading from or Reinstalling from SAS 9.4 before the July 2015 Release of SAS 9.4

Note: SAS Data Loader users: If you want to remove either the Quality Knowledge Base (QKB) or the SAS Data Management Accelerator for Spark, you must remove them 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 or SASDMP_ADMIN.SH Syntax.

To upgrade or reinstall from SAS 9.4 before the July 2015 release of SAS 9.4, follow these steps:

Stop the SAS Embedded Process.
```
EPInstallDir/SAS/SASTKInDatabaseServerForHadoop/9.*/bin/sasep-servers.sh
   -stop -hostfile host-list-filename | -host <">host-list<">
```
EPInstallDir is the master node where you installed the SAS Embedded Process.
For more information, see the SASEP-SERVERS.SH syntax section of the SAS In-Database Products: Administrator’s Guide that came with your release.
Remove the SAS Embedded Process from all nodes.
```
EPInstallDir/SAS/SASTKInDatabaseForServerHadoop/9.*/bin/sasep-servers.sh
   -remove -hostfile host-list-filename | -host <">host-list<">
   -mrhome dir
```
Note: This step ensures that all old SAS Hadoop MapReduce JAR files are removed.

For more information, see the SASEP-SERVERS.SH syntax section of the SAS In-Database Products: Administrator’s Guide that came with your release.
Verify that the sas.hadoop.ep.apache*.jar files have been deleted.

The JAR files are located at HadoopHome/lib.
For Cloudera, the JAR files are typically located here:
```
/opt/cloudera/parcels/CDH/lib/hadoop/lib
```
For Hortonworks, the JAR files are typically located here:
```
/usr/lib/hadoop/lib
```
Note: If all the files have not been deleted, then you must manually delete them. Open-source utilities are available that can delete these files across multiple nodes.
Verify that all the SAS Embedded Process directories and files have been deleted on all nodes except the node from which you ran the sasep-servers.sh -remove script. The sasep-servers.sh -remove script removes the file everywhere except on the node from which you ran the script.

Note: If all the files have not been deleted, then you must manually delete them. Open-source utilities are available that can delete these files across multiple nodes.
Manually remove the SAS Embedded Process directories and files on the node from which you ran the script. Open-source utilities are available that can delete these files across multiple nodes.
The sasep-servers.sh -remove script removes the file everywhere except on the node from which you ran the script. The sasep-servers.sh -remove script displays instructions that are similar to the following example.
```
localhost WARN: Apparently, you are trying to uninstall SAS Embedded Process 
for Hadoop from the local node.
The binary files located at 
   local_node/SAS/SASTKInDatabaseServerForHadoop/local_node/
SAS/SASACCESStoHadoopMapReduceJARFiles will not be removed.
localhost WARN: The init script will be removed from /etc/init.d and the 
   SAS Map Reduce JAR files will be removed from /usr/lib/hadoop-mapreduce/lib.
localhost WARN: The binary files located at local_node/SAS 
   should be removed manually.
```
Tip
You can use this command to find the location of any instance of the SAS Embedded Process:
```
ps -ef | grep depserver
```
Continue the installation process.

For more information, see Using the SAS Deployment Manager to Create the SAS Embedded Process Parcel or Stack.

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

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 Create the SAS Embedded Process Parcel or Stack.

If you want to remove the existing parcel or stack, see either Removing the SAS Embedded Process Parcel Using Cloudera Manager or Removing the SAS Embedded Process Stack Using Ambari.

Removing the SAS Embedded Process Parcel Using Cloudera Manager

Note: SAS Data Loader users: If you want to remove either the Quality Knowledge Base (QKB) or the SAS Data Management Accelerator for Spark, you must remove them 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 or SASDMP_ADMIN.SH Syntax.

To remove the SAS Embedded Process Parcel using Cloudera Manager, follow these steps:

Start Cloudera Manager.
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.
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 HomeStatus tab.
Deactivate the SASEP parcel:
1. Navigate to the HostsParcels tab.
2. Select ActionsDeactivate.
  
  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.
Remove the SASEP parcel:
1. Select ActivateRemove from Hosts.
2. Click OK to confirm.
Delete the SASEP parcel.
Select DistributeDelete.
Click OK to confirm.

This step deletes the parcel files from the /opt/cloudera/parcel directory.
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/
Continue the installation process.

For more information, see Using the SAS Deployment Manager to Create the SAS Embedded Process Parcel or Stack.

Removing the SAS Embedded Process Stack Using Ambari

Note: SAS Data Loader users: If you want to remove either the Quality Knowledge Base (QKB) or the SAS Data Management Accelerator for Spark, you must remove them 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 or SASDMP_ADMIN.SH Syntax.

Note: You need root or passwordless sudo access to remove the stack.

To remove the SAS Embedded Process stack using Ambari, follow these steps:

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.
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
```
Use this command to run the delete script.
```
./delete_stack.sh <Ambari-Admin-User-Name>
```

Enter the Ambari administrator password at the prompt.

The following message appears.

Select one of the options from the below
enter 1 to remove SASEP config file only
enter 2 to remove specific version of SASEP
enter 3 to remove all versions of SASEP

Choose one of the three options:
- 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.
To complete the removal of the SASEP SERVICE, you are prompted to restart the Ambari server.
Enter y to restart the Ambari server. The SASEP SERVICE should not appear.
Continue the installation process.

For more information, see Using the SAS Deployment Manager to Create the SAS Embedded Process Parcel or Stack.