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

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 upgrade 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 Deploy the SAS Embedded Process Parcel or Stack to the Cluster.

Last updated: February 9, 2017