Installation instructions for hot fix P20024 on Linux for x64

Installation Instructions for Hot Fix P20024

Linux for x64

Hot fix P20024 addresses the issue(s) in SAS Revenue Optimization 5.2_M4 as documented in the Issue(s) Addressed section of the hot fix download page:

http://ftp.sas.com/techsup/download/hotfix/HF2/P20.html#P20024

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

P23027 updates SAS Merchandise Intelligence Client 5.21_M4
P28027 updates SAS Merchandise Intelligence Grid Server 5.21_M4
P24027 updates SAS Merchandise Intelligence Mid-Tier 5.21_M4
P25027 updates SAS Merchandise Intelligence Plug-in for SAS Management Console 5.21_M4
P68016 updates SAS Merchandise Intelligence Server 5.21_M4
P26027 updates SAS Merchandise Intelligence Workbench Server 5.21_M4
P27027 updates SAS Merchandise Solutions Configuration Workbench 5.21_M4
P52002 updates SAS Regular Price Optimization 5.2_M4
P22018 updates SAS Revenue Optimization Server 5.2_M4

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

Do NOT extract the contents of P20024pt.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 P20024 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.

After downloading P20024pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.3: User’s Guide.

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

For each product installed, click the link to be redirected to post-installation instructions.

P23027 updates SAS Merchandise Intelligence Client 5.21_M4
P28027 updates SAS Merchandise Intelligence Grid Server 5.21_M4
P24027 updates SAS Merchandise Intelligence Mid-Tier 5.21_M4
P25027 updates SAS Merchandise Intelligence Plug-in for SAS Management Console 5.21_M4
P68016 updates SAS Merchandise Intelligence Server 5.21_M4
P26027 updates SAS Merchandise Intelligence Workbench Server 5.21_M4
P27027 updates SAS Merchandise Solutions Configuration Workbench 5.21_M4
P52002 updates SAS Regular Price Optimization 5.2_M4
P22018 updates SAS Revenue Optimization Server 5.2_M4

P23027 updates SAS Merchandise Intelligence Client 5.21_M4
P27027 updates SAS Merchandise Solutions Configuration Workbench 5.21_M4

Security Update for SAS Merchandise Intelligence Client 5.21_M4 and SAS Merchandise Solutions Configuration Workbench 5.21_M4

If the updates for the Java Deserialization Vulnerability documented at http://support.sas.com/security/Java-deserialization.html were applied to your system, you must rerun the SAS Security Update after applying this hot fix. The current SAS Security Update can be downloaded from http://ftp.sas.com/techsup/download/hotfix/HF2/Java-deserialization_update.html. To apply the update, perform Step 1 — Apply SAS Security Update and Step 3 — Rebuild and Redeploy Web Applications in the instructions in the PDF document provided at the same link.

P28027 updates SAS Merchandise Intelligence Grid Server 5.21_M4

NONE

P24027 updates SAS Merchandise Intelligence Mid-Tier 5.21_M4

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:

Step 1. Remove com.sas.app.launcher.cacheFile

Delete

<SASHOME>/SASVersionedJarRepository/eclipse/com.sas.app.launcher.cacheFile

Step 2: Re-build Web Applications

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

Re-build the Merchandise Intelligence Mid-Tier 5.2 Web application as instructed here:

SAS(R) 9.3 Intelligence Platform: Middle-Tier Administration Guide

Note: Select Merchandise Intell Mid-Tier 5.2 Web Applications to Rebuild

This process will update the SAS Merchandise Intelligence Mid-Tier 5.2 ear in

<CONFIGDIR>/Lev1/Web/Staging

A backup of the original ear file will be placed in the Backup directory.

Step 3: Re-deploy Web Applications

Re-deploy the Merchandise Intell Mid-Tier 5.2 Web application (only). Re-deploy the SAS Web Applications as instructed here:

SAS(R) 9.3 Intelligence Platform: Middle-Tier Administration Guide

Note: Select sas.miserver5.2.ear when re-deploying the Web application.

Step 4: Stop and restart the Web application server.

P25027 updates SAS Merchandise Intelligence Plug-in for SAS Management Console 5.21_M4

NONE

P68016 updates SAS Merchandise Intelligence Server 5.21_M4

Please query the Oracle table DI_TRANS.RDBMS_DM_CHANGE_MANAGEMENT to see if CHANGE_ID = ‘S1136150’ has already been applied. If it has not been applied a query for that CHANGE_ID will return zero rows. If CHANGE_ID 1336150 has not been applied and if the Oracle table RPP_VENDOR_DEAL already has an index named RPP_VENDOR_DEAL_IX5 in your environment please remove it. This will allow the update_datamart.sh script to run successfully. To remove the index, you can do so with the following code run in a SAS session where the SAS Merchandise Intelligence libraries are allocated:

proc sql noprint;
drop index RPP_VENDOR_DEAL_IX5 on DI_TRANS.RPP_VENDOR_DEAL;
quit;

Run the Update Data Mart Script

Run the Update Data Mart Script to update the existing data mart:

Log on as MI ETL User (sasmietl).
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)
Adds a new UNIQUE index: ‘PKO_PROD_HIER_IX10’ on PKO_PRODUCT_HIER_ASSOC_DM (PROD_HIER_ASSOC_CD, PARENT_PROD_HIER_SK, PROD_LVL, PROD_HIER_SK)
Adds a new spec ‘im_instore_maxlimit’ in PRF_CONFIG.
MAX_ALERT_BATCH_SIZE , should be also checked in DI_DM2.Global_setting_group_member and DI_DM2. Global_setting_details

The following two indexes are getting created on the table - MPLN_GEO_PROD_AGG:

CREATE INDEX MPLN_GPA_IX2 ON MPLN_GEO_PROD_AGG (MDO_PLAN_SK, PROD_HIER_SK, GEO_HIER_SK) PARALLEL ;
CREATE INDEX MPLN_GPA_IX3 ON MPLN_GEO_PROD_AGG (PROD_HIER_SK, MDO_PLAN_SK, GEO_HIER_SK) PARALLEL ;

ALTER INDEX MPLN_GPA_IX2 NOPARALLEL;
ALTER INDEX MPLN_GPA_IX3 NOPARALLEL;

Before executing the update_datamart.sh, please follow the below steps as update_datamart.sh might fail if there are indexes already present in the schema.
Case 1 : If the same indexes are already present in the schema with same name (MPLN_GPA_IX2 or MPLN_GPA_IX3) or different name
- delete them before running the update_datamart.sh
Case 2 : If different indexes (created by the customer) are present in the schema with same name (MPLN_GPA_IX2 or MPLN_GPA_IX3)
- rename them before running the update_datamart.sh

SAS changes:

Adds the INDEPENDENT_BATCH_PREP global setting
Adds the MUST_MEET_SKU_MIN and DEDUPE_MULTIPLE_BULK_PACKS global settings
Adds the parameter ETLP_POS_ENABLE in JOB_PARAM
Adds a UNIQUE index: PROD_HIER_IX8 on PRODUCT_HIER_ASSOC_DM (PROD_HIER_ASSOC_CD,PARENT_PROD_LVL, PROD_HIER_SK)
Adds a UNIQUE index: PROD_HIER_IX10 on PRODUCT_HIER_ASSOC_DM (PROD_HIER_ASSOC_CD, PARENT_PROD_HIER_SK, PROD_LVL, PROD_HIER_SK)
Adds the PROMO_MIX_BLEND_CALC_TYPE global setting
A new record for SPEC_NM = MAX_ALERT_BATCH_SIZE is added to the table DI_DM.GLOBAL_SETTING for ‘ALL’ applications is created

Note: This hot fix adds the INDEPENDENT_BATCH_PREP global setting. For details, see the Administrator’s Guide Errata document.

After applying this hotfix '|' is the separator for entries in the following three tables.
• pricing_relation.attr_value_list1
• pricing_relation.attr_value_list2
• pricing_reln_match_attr.match_attr_value_list

After installation of HF the following macro needs to be executed as follows - for existing customers having data already loaded in the three tables.
New Customers having no data didn’t need to run the script.

%di_util_update_pricing_reln_attr(src_delim=%str(,),tgt_delim=%str(|));

The macro will replace the ',' in attribute values with '|'. The replace operation will be done in the RDBMS tables mentioned above.

P26027 updates SAS Merchandise Intelligence Workbench Server 5.21_M4

NONE

P52002 updates SAS Regular Price Optimization 5.2_M4

NONE

P22018 updates SAS Revenue Optimization Server 5.2_M4

NONE

After completing all of the post-install sections above, run your weekly ETL and back-end jobs.