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, P20018pt.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
P20018pt.zip on each machine or save it in a network location that is accessible to all machines.

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

IMPORTANT NOTES

You must have SAS Merchandise Intelligence 5.2_M4 installed on your system before applying this hot fix.
Refer to SN-35968 for instructions on how to determine which
product releases you have installed.

At a minimum, back up your system:a. For SAS, refer to the SAS 9.3 Guide to Software Updates for documentation about back up tasks:
http://support.sas.com/documentation/cdl/en/whatsdiff/63859/HTML/default/viewer.htm#titlepage.htm

b. For SAS Merchandise Intelligence, backup the MI data mart and database.
Technical Support strongly suggests that you back up all of your files. You should always
try to include the current date in the name of the backup file created to distinguish between
versions of backup files. By doing this, you will maintain a history of the file, which will be
helpful when multiple iterations of a maintenance release have been applied to the same file.
For example:
cp com.sas.solutions.di.server.jar com.sas.solutions.di.server.jar.08202012
where 08202012 is the date when the maintenance release is applied.
The extension must be appended after the .jar extension, as it appears above.

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.

You must deploy the hot fix in the following timeframe

after your weekly activity has completed

before the weekly ETL and back-end job

INSTALLATION

Hot Fix P20018 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 SAS Revenue Optimization 5.2_M4 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.

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).

Web application Update

Updates to the SAS Merchandise Intelligence Mid-Tier 5.21 provided in this hot fix require that Web Applications
be rebuilt and redeployed. If this component is installed on Unix, follow the steps below to rebuild and redeploy
the web application:

From the sasmietl home directory, run the update_datamart script./Lev1/Applications/SASMerchIntellServer5.2/sas/update_datamart.sh

Check the log file (update_datamart.log) for output and errors.

Note: When you run the update_datamart script, the system adds a date and time stamp to the name of the
log file. This enables the system to maintain multiple versions of the log files. It also makes it easier to identify
which log files correspond to specific runs of the scripts.

Here is an example of a log file that results from a script run on May 8, 2012, at 9:44 a.m.:
update_datamart_20120508_0944.log

This hot fix makes the following schema changes.

RDBMS changes:

Adds a new index: ‘RPP_VENDOR_DEAL_IX5’ on RPP_VENDOR_DEAL (abs(PLAN_SK))

Adds a new index: ‘PKO_PROD_HIER_IX8’ on PKO_PRODUCT_HIER_ASSOC_DM (PROD_HIER_ASSOC_CD, PARENT_PROD_LVL, PROD_HIER_SK)