Installation instructions for hot fix C9Z001 on Linux for x64

Installation Instructions for Hot Fix C9Z001

Linux for x64

Hot fix C9Z001 addresses the issue(s) in Episode Analytics 4.2 as documented in the Issue(s) Addressed section of the hot fix download page:

https://tshf.sas.com/techsup/download/hotfix/HF2/C9Z.html#C9Z001

C9Z001 is a "container" hot fix that contains the following "member" hot fixes which will update the software components as needed.

C9U001 updates SAS Episode Analytics Mid-Tier 4.2
C9T001 updates SAS Episode Analytics Server 4.2

See What is a container hot fix? in the Hot Fix FAQ for more information about container hot fixes.

Before applying this hot fix, follow the instructions in SAS Note 35968 to generate a SAS Deployment Registry report, then verify that the appropriate product releases are installed on your system. The release number information in the Registry report should match the 'member' release number information provided above for the software components installed on each machine in your deployment.

The hot fix downloaded, C9Z001pt.zip, includes the updates required for all components listed above on all applicable operating systems. To apply this hot fix on multiple machines, you can either save C9Z001pt.zip on each machine or save it in a network location that is accessible to all machines.

Do NOT extract the contents of C9Z001pt.zip. The hot fix installation process will extract the contents as needed.

IMPORTANT NOTES

Files delivered in this hot fix will be backed up during the installation process. However, it is good general practice to back up your system before applying updates to software.
You must have Administrator Privileges on your CLIENT or SERVER machine.
All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix.
This hot fix should be installed using the same userid who performed the initial software installation.
CONFIGURATION: No automatic configuration scripting is included for this hot fix. If you have previously configured software installed, the SAS Deployment Manager may present a screen where you will see "Apply SAS Hot Fixes" and "Configure SAS Hot Fixes" options. On this screen, you must ensure that the "Configure SAS Hot Fix" option is *not* selected. If this option is automatically selected, please de-select it prior to proceeding with the SAS Deployment Manager Screens. Failure to do so could have unintended consequences when applying this hot fix.

INSTALLATION

Hot Fix C9Z001 must be installed on each machine where the updated components of the product, listed above, are installed. During the installation process you may see references to all operating systems for which updates are provided in the hot fix. The installation process will determine the operating system and which component(s) of Episode Analytics 4.2 require updating on the machine. See SAS Note 44810 for more details.

The hot fix will be applied using the SAS Deployment Manager. By default, the SAS Deployment Manager will search in the <SASHOME>/InstallMisc/HotFixes/New directory for hot fixes to be applied, but will also prompt for a location if you have downloaded hot fixes to a different directory.

After downloading C9Z001pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.4: User's Guide.

Please review the CONFIGURATION Important Note above concerning proper selection of the "Configure SAS Hot Fix" option in the SAS Deployment Manager.

The hot fix installation process generates the log file

<!SASHOME>/InstallMisc/InstallLogs/IT_date-and-time-stamp.log

for example, IT_2011-10-31-13.18.21.log. Each attempt to apply a hot fix results in the creation of a new log file giving detailed information regarding the installation process.

Postexec log files are created after the installation is completed and identifies the files that were added, backed up, changed and removed. These log files include the 'member' hot fix id in the name of the file and are also written to the <!SASHOME>/InstallMisc/InstallLogs directory. There is one postexec log for each 'member' hot fix applied (member hot fixes are listed at the top of these instructions).

The content of this hot fix is listed in the hot fix manifest.

POST-INSTALLATION INSTRUCTIONS

Follow the instructions below to complete the updates for products listed. They can be performed one time per installation.

C9U001 updates SAS Episode Analytics Mid-Tier 4.2

Step 1: Re-build Web Applications

In order for this step to execute correctly, the Metadata Server must be running.

1.1 Set the DISPLAY environment variable, for example

$ export DISPLAY=<displayname>:0

1.2 Invoke the SAS Deployment Manager 9.4

From the SASDeploymentManager directory execute sasdm.sh, for example

$ cd <SASHOME>/SASDeploymentManager/9.4
$ ./sasdm.sh

1.3 Select a language in the Choose Language box

1.4 Select Rebuild Web Applications

1.5 Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated

1.6 Specify Connection Information, including the sasadm User ID and Password

1.7 Select each Web Application to Rebuild based on the list of products installed above.

1.8 Verify the information on the Summary screen and select Start

1.9 Select Finish when the deployment is complete

This process will update the ear files in <CONFIGDIR>/Lev1/Web/Staging and place the updated exploded ears in <CONFIGDIR>/Lev1/Web/Staging/exploded. A backup of the original ear file will be placed in the Backup directory.

Step 2: Re-deploy Web Applications

2.1 Re-deploy the updated ears listed above to the web application server you are using based on the instructions appropriate for your web application server. See SAS 9.4 Intelligence Platform Middle-Tier Administration Guide, Chapter 8, for more details.
C9T001 updates SAS Episode Analytics Server 4.2

Step 3: Run SAS Program to Update Oracle Tables

3.1 On the SAS Compute server, launch the SAS Workspace Server, for example

$ cd <CONFIGDIR>/Lev1/SASApp $ ./sas.sh

3.2 Select File > Open� and select the <SASHOME>/SASFoundation/9.4/misc/avaecrsvr/sea_run_file_set_alter_ddl.sas program.

3.3Submit the code by selecting Run > Submit. The end of the log should display a message showing the data precision is 12.
For example,

SYMBOLGEN: Macro variable DATA_PRECISION resolves to 12