INSTALLATION INSTRUCTIONS FOR HOT FIX 22RO02 ON AIX BEFORE DOWNLOADING: The hot fix 22RO02 addresses the issue(s) in 2.2 of SAS Revenue Optimization software on AIX as documented in the "Issue(s) Addressed" section of the hot fix download page: http://ftp.sas.com/techsup/download/hotfix/ro22.html#22ro02 IMPORTANT NOTE(S): 1. You must have SAS Revenue Optimization 2.2 installed on your system before applying this hot fix. 2. You must install the Hot Fix using the same user ID that you used to install the 2.2 product. The vpd.properties file from the initial installation must be in the user's home directory. 3. Before applying this hot fix, you must terminate all currently active SAS Merchandise Intelligence sessions, Object Spawners and Metadata Servers. 4. Recommended - Log on as root and issue the slibclean command to ensure a clean environment. AFTER DOWNLOADING: The hot fix package downloaded is a tar file named 22ro02r6.tar. This tar file contains the script and supporting files to update Mid-Tier Server, Data Tier, and Clients. To install this hot fix follow these steps: 1. Extract 22ro02r6.tar into a temporary directory. > cd /tmp > tar -xf $HOME/22ro02r6.tar where $HOME is the location of the downloaded tar file. This extracts three components of this hot fix and supporting documentation into /tmp/22ro02. The three components extracted are: 22disvr02r6.tar contains updates to the SAS MI Mid-Tier Server for AIX 22diclnt02wn.exe contains updates to the SAS Revenue Optimization client for WIN 22ro02r6.tar.Z contains updates to the SAS Revenue Optimization Data Tier on AIX Use the instructions below to apply the individual components that apply to your system. MID Tier: ---------- Installing 22disvr02r6.tar The Server component of the hot fix package is a tar file named 22disrv02r6.tar. 22disrv02r6.tar Java installation file containing replacement files below: com.sas.solutions.di.server.jar com.sas.solutions.di.server.api.jar Execute these steps on the MI Mid-Tier Server machine. STEP 1: Extract the contents of the hot fix package Extract the contents of the tar file into the temporary directory, i.e. /tmp/22ro02. $> cd /tmp/22ro02 $> tar -xf ./22disvr02r6.tar This will result in the following 3 files written to r64 subdirectory: Setup_AIX_Power media.inf setup.jar STEP 2: Execute the installation wizard $> export DISPLAY=:0 <==== set your display $> cd /tmp/22ro02/r64 $> chmod +x Setup_AIX_Power $> ./Setup_AIX_Power This will initiate the InstallShield Wizard. Follow the prompts to complete the installation. To verify the installation of the hot fix confirm that the file(s) in the location(s) below have been updated to the level indicated by the date provided: /SASMerchandiseIntelligence/Server/2.2/com.sas.solutions.di.server.jar Date: 04/20/07 (EST) /SASMerchandiseIntelligence/Server/2.2/com.sas.solutions.di.server.api.jar Date: 04/20/07 (EST) MID Tier Post-Installation Instructions On the middle tier machine, perform the following steps: STEP 1: Enable the data migration process for the CLR_GROUP table upon MI Mid-Tier Server startup. Edit the server.xml in the SASMerchandiseIntelligence/cfg directory and insert startup="yes" for the CPOService component as follows: com.sas.solutions.di.server.cpo.CPOServiceMBean com.sas.solutions.di.server.cpo.CPOService localhost 1444 STEP 2: For DB2 only, add JVM Options to the wrapper.conf file. The wrapper.conf file is located in the conf directory of your MI Mid-Tier Server installation directory. Add the following lines under the “IBM Server JVM Options” section of the wrapper.conf file: wrapper.java.additional.7=-verbose:gc wrapper.java.additional.8=-Xms1280m wrapper.java.additional.9=-Xmx1920m wrapper.java.additional.10=-Xk8000 wrapper.java.additional.11=-Xloratio0.3 wrapper.java.additional.12=-Xgcpolicy:optavgpause wrapper.java.additional.13=-Xpartialcompactgc wrapper.java.additional.14=-Dsun.rmi.dgc.client.gcInterval=3600000 wrapper.java.additional.15=-Dsun.rmi.dgc.server.gcInterval=3600000 wrapper.java.additional.16=-Djava.awt.headless=true wrapper.java.additional.17=-Dibm.dg.trc.print=st_verify CLIENT Tier: ------------ Installing 22diclnt02wn.exe The client component of the hot fix package is a self extracting executable named 22diclnt02wn.exe. 22diclnt02wn.exe should be copied to and installed on all client machines. Launching the executable will initiate a Java install wizard, which will guide you through the extraction of the updated component(s). 22diclnt02wn.exe Java installation file containing replacement files below: com.sas.solutions.di.server.jar com.sas.solutions.di.server.api.jar com.sas.solutions.di.studio.jar com.sas.solutions.di.studio.rcp.jar com.sas.solutions.di.studio.rpt.jar com.sas.solutions.di.studio.rpp.jar To verify the installation of the hot fix confirm that the file(s) in the location(s) below have been updated to the level indicated by the date provided: \SASManagementConsole\9.1\plugins\com.sas.solutions.di.server.api.jar Date: 04/20/07 (EST) \SASRevenueOptimization\Client\2.2\plugins\com.sas.solutions.di.studio.jars_1.0.0\lib\jars\com.sas.solutions.di.server.api.jar Date: 04/20/07 (EST) \SASRevenueOptimization\Client\2.2\plugins\com.sas.solutions.di.studio_1.0.0\com.sas.solutions.di.studio.jar Date: 04/20/07 (EST) \SASRevenueOptimization\Client\2.2\plugins\com.sas.solutions.di.studio.rcp_1.0.0\com.sas.solutions.di.studio.rcp.jar Date: 04/20/07 (EST) \SASRevenueOptimization\Client\2.2\plugins\com.sas.solutions.di.studio.rpt_1.0.0\com.sas.solutions.di.studio.rpt.jar Date: 10/03/06 (EST) \SASRevenueOptimization\Client\2.2\plugins\com.sas.solutions.di.studio.rpp_1.0.0\com.sas.solutions.di.studio.rpp.jar Date: 10/03/06 (EST) CLIENT Tier Post-Installation Instructions The file com.sas.solutions.di.server.api.jar was installed as part of the SAS Revenue Optimization hot fix when 22diclnt02r6.exe was executed. To complete the hot fix, copy com.sas.solutions.di.server.api.jar from the SAS Revenue Optimization client install location to the plug-ins folder under the SAS Management Console install location. SAS Database Tier: ------------------ Installing 22ro02r6.tar.Z The name of the tar file is 22ro02r6.tar.Z, and it contains the following updated files: * sasmacr.sas7bcat the replacement catalog containing the hot fix in !SASROOT/cmacros/di * sasmacr.sas7bcat the replacement catalog containing the hot fix in !SASROOT/cmacros/dipcl * sasclprs the replacement module containing the hot fix in !SASROOT/sasexe * mireports.spk the replacement file containing the hot fix in !SASROOT/misc/di/Config/cfg * dipcl_rpt_clr_idc_inv_stp.sas the replacement file containing the hot fix in !SASROOT/sasstp/dipcl * dipcl_rpt_md_projection_stp.sas the replacement file containing the hot fix in !SASROOT/sasstp/dipcl * dipcl_rpt_clr_aging_stp.sas the replacement file containing the hot fix in !SASROOT/sasstp/dipcl * Load_STG2DM_Promo_price_fact.xml the replacement file containing the hot fix in !SASROOT/misc/di/etlxml * Load_DM_Data_lvl.xml the replacement file containing the hot fix in !SASROOT/misc/di/etlxml * Load_STG2DM_Date_dm.xml the replacement file containing the hot fix in !SASROOT/misc/di/etlxml * Load_STG2DM_Geo_prod.xml the replacement file containing the hot fix in !SASROOT/misc/di/etlxml * Load_STG2DM_Geography_relation.xml the replacement file containing the hot fix in !SASROOT/misc/di/etlxml * Load_STG2DM_Product_dm.xml the replacement file containing the hot fix in !SASROOT/misc/di/etlxml * Load_STG2DM_Product_relation.xml the replacement file containing the hot fix in !SASROOT/misc/di/etlxml * di_tool_build_subset.sas the replacement file containing the hot fix in !SASROOT/misc/di/tool * di_tool_forecast_plot.sas the replacement file containing the hot fix in !SASROOT/misc/di/tool * di_tool_ts_decomp_plot.sas the replacement file containing the hot fix in !SASROOT/misc/di/tool * di_tool_update_price_fact.sas the replacement file containing the hot fix in !SASROOT/misc/di/tool * di_tool_agg_forecast_eval.sas the replacement file containing the hot fix in !SASROOT/misc/di/tool Execute these steps on the Data Tier, which is configured on AIX. In this example, !SASROOT, the directory where SAS 9.1.3 (9.1 TS1M3) is installed: /usr/local/SAS/SAS_9.1 STEP 1: Back up the existing version of sasclprs before extracting the contents of this hot fix. $> cd /usr/local/SAS/SAS_9.1 $> cp sasexe/sasclprs sasexe/sasclprs.bak STEP 2: Extract the contents of the hot fix package $> pwd /usr/local/SAS/SAS_9.1 $> uncompress -c /tmp/22ro02/22ro02r6.tar.Z | tar -xf - STEP 3: Update the installation history file. Execute the script that will update the hot fix install history file. This script MUST be executed from the !SASROOT directory. $> pwd /usr/local/SAS/SAS_9.1 $> install/admin/hotfix/hist_upd SAS Database Tier Post-Installation Instructions On the database machine, perform the following steps: STEP 1: Add 5 new columns to the DB2 table CLR_GROUP by issuing the following statement at a DB2 command prompt: ALTER TABLE CLR_GROUP ADD COLUMN NUM_MEMBERS INTEGER ADD COLUMN NUM_PRODS INTEGER ADD COLUMN NUM_GEOS INTEGER ADD COLUMN PARENT_PROD_HIER_SK INTEGER ADD COLUMN PARENT_GEO_HIER_SK INTEGER; To keep your metadata synchronized, use SAS Management Console to re-import the CLR_GROUP table metadata for each of the database libraries. STEP 2: Change the cache setting for the CLR_PLAN_PRICE_CHANGE_SK column in the CLR_PLAN_PRICE_CHANGE table, (the default cache setting is 20,000) by issuing the following statement at a DB2 command prompt: RENAME TABLE CLR_PLAN_PRICE_CHANGE TO CLR_PLAN_PRICE_CHANGE_OLD; DROP INDEX CLR_PLAN_PCHG_FK1; CREATE TABLE CLR_PLAN_PRICE_CHANGE ( CLR_PLAN_PRICE_CHANGE_SK INTEGER NOT NULL GENERATED ALWAYS AS IDENTITY( START WITH 100000, INCREMENT BY 1, CACHE 20000 CYCLE ), CLR_PLAN_SK INTEGER NOT NULL, START_DT DATE NOT NULL, END_DT DATE, SUGGESTED_PRICE NUMERIC(12,2), SUGGESTED_DISC_PCT NUMERIC(12,4), APPROVAL_STATUS_CD INTEGER, APPROVAL_STATUS_DT DATE, APPROVAL_STATUS_APP_USER_SK INTEGER, PRIMARY KEY (CLR_PLAN_PRICE_CHANGE_SK)); CREATE INDEX CLR_PLAN_PCHG_FK1 ON CLR_PLAN_PRICE_CHANGE ( CLR_PLAN_SK ASC) ALLOW REVERSE SCANS; INSERT INTO CLR_PLAN_PRICE_CHANGE ( CLR_PLAN_SK, START_DT, END_DT, SUGGESTED_PRICE, SUGGESTED_DISC_PCT, APPROVAL_STATUS_CD, APPROVAL_STATUS_DT, APPROVAL_STATUS_APP_USER_SK) SELECT CLR_PLAN_SK, START_DT, END_DT, SUGGESTED_PRICE, SUGGESTED_DISC_PCT, APPROVAL_STATUS_CD, APPROVAL_STATUS_DT, APPROVAL_STATUS_APP_USER_SK FROM CLR_PLAN_PRICE_CHANGE_OLD; DROP TABLE CLR_PLAN_PRICE_CHANGE_OLD; After completing this step, you must grant all permissions on this table to the midbuser and mietldb user IDs. To keep your metadata synchronized, use SAS Management Console to re-import the CLR_PLAN_PRICE_CHANGE_SK table metadata for each of the database libraries. Determine the appropriate cache setting value for your installation by determining the number of pregenerated values that will handle the average number of inserts to the CLR_PLAN_PRICE_CHANGE table in a 24-hour period. The CLR_PLAN_PRICE_CHANGE table contains one row for each product-location plan and an additional row for each price change in that plan that occurs after the first week. For example, a product-location plan with one price change in week 1 will have one row. A product-location plan with a price change only in week 2 or later will have 2 rows. Set the value of the identity column cache settings to contain enough pregenerated values to handle the average number of inserts to the table in a 24-hour period. For more information about additional DB2 configuration parameters for performance, see the DB2 Recommendations document on the SAS Revenue Optimization Web site: http://support.sas.com/software/revoptimization/deployreqs.html STEP 3: Change existing indexes to allow reverse scans by issuing the following statement at a DB2 command prompt: DROP INDEX APP_GEO_PROD_IX1; DROP INDEX APP_GEO_PROD_IX2; DROP INDEX AUDIT_TRAIL_FK1; DROP INDEX AUDIT_TRAIL_IX1; DROP INDEX CAL_VEH_ASN_IX1; DROP INDEX CLASS_AUTH_FK1; DROP INDEX CLASS_AUTH_FK2; DROP INDEX CLR_PLAN_PCHG_FK1; DROP INDEX CLR_PLAN_PCHGM_IX1; DROP INDEX CPLAN_IX1; DROP INDEX CPLAN_IX2; DROP INDEX CPLAN_IX3; DROP INDEX CPLAN_MTR_AGG_FK1; DROP INDEX CPLAN_MTR_FK1; DROP INDEX CSPC_IX1; DROP INDEX DATA_AUTH_FK1; DROP INDEX EVENT_FK1; DROP INDEX EVENT_VEH_FK1; DROP INDEX EVENT_VEH_FK2; DROP INDEX GEO_HIER_IX2; DROP INDEX GEO_HIER_IX3; DROP INDEX GEO_PROD_AGG_IX1; DROP INDEX GEO_PROD_SET_IX1; DROP INDEX PGRID_RNG_FK1; DROP INDEX PGRID_RNG_VAL_FK1; DROP INDEX PLAN_FK1; DROP INDEX PLAN_FK2; DROP INDEX PLAN_FK3; DROP INDEX PLAN_OBJ_IX1; DROP INDEX PLAN_OPT_SET_IX1; DROP INDEX PLAN_VEH_ASG_IX1; DROP INDEX PLAN_VEH_ASG_IX2; DROP INDEX PLAN_VEH_ASG_IX3; DROP INDEX PLAN_VEH_ASG_IX4; DROP INDEX PROC_MSG_DET_FK1; DROP INDEX PROC_MSG_DET_FK2; DROP INDEX PROC_STATUS_IX1; DROP INDEX PROD_DM_IX1; DROP INDEX PROD_DM_IX2; DROP INDEX PROD_DM_IX3; DROP INDEX PROD_HIER_IX2; DROP INDEX PROD_HIER_IX3; DROP INDEX PROD_NO_MIX_FK1; DROP INDEX PVAL_TYPE_OVRD_FK1; DROP INDEX PVAL_TYPE_OVRD_FK2; DROP INDEX SAVED_ENTITY_IX1; DROP INDEX SAVED_REP_PARM_FK1; DROP INDEX SAVED_REPORT_FK1; DROP INDEX SCOPE_DETAIL_FK1; DROP INDEX SCOPE_DETAIL_FK2; DROP INDEX SCOPE_DETAIL_FK3; DROP INDEX STATUS_TRANS_FK1; DROP INDEX STATUS_TRANS_FK2; DROP INDEX USER_VEH_FK1; DROP INDEX USER_VEH_FK2; DROP INDEX USER_VEH_FK3; DROP INDEX USER_VEH_FK4; DROP INDEX VEH_CAT_ATTR_FK1; DROP INDEX VEHICLE_ATTR_FK1; DROP INDEX VEHICLE_FK1; DROP INDEX VEHICLE_FK2; DROP INDEX VEHICLE_FK3; DROP INDEX GEO_DM_IX1; DROP INDEX GEO_HIER_IX1; DROP INDEX PROD_HIER_IX1; CREATE INDEX APP_GEO_PROD_IX1 ON APP_GEO_PROD ( CLR_STATUS_CD ASC) ALLOW REVERSE SCANS; CREATE INDEX APP_GEO_PROD_IX2 ON APP_GEO_PROD ( CLR_GROUP_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX AUDIT_TRAIL_FK1 ON AUDIT_TRAIL ( APP_USER_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX AUDIT_TRAIL_IX1 ON AUDIT_TRAIL ( OBJECT_TYPE ASC) ALLOW REVERSE SCANS; CREATE INDEX CAL_VEH_ASN_IX1 ON CALENDAR_VEHICLE_ASSIGNMENT ( GEO_HIER_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX CLASS_AUTH_FK1 ON CLASS_AUTHORIZATION ( APP_SECURE_CLASS_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX CLASS_AUTH_FK2 ON CLASS_AUTHORIZATION ( APP_GROUP_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX CPLAN_IX1 ON CLR_PLAN ( CLR_GROUP_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX CPLAN_IX2 ON CLR_PLAN ( GROUP_CLR_PLAN_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX CPLAN_IX3 ON CLR_PLAN ( PROD_HIER_SK, GEO_HIER_SK) CLUSTER ALLOW REVERSE SCANS; CREATE INDEX CLR_PLAN_PCHG_FK1 ON CLR_PLAN_PRICE_CHANGE ( CLR_PLAN_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX DATA_AUTH_FK1 ON DATA_AUTHORIZATION ( APP_GROUP_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX EVENT_FK1 ON EVENT ( CAL_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX EVENT_VEH_FK1 ON EVENT_VEHICLE ( VEHICLE_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX EVENT_VEH_FK2 ON EVENT_VEHICLE ( EVENT_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX GEO_PROD_SET_IX1 ON GEO_PROD_SETTING ( PROD_HIER_SK ASC, GEO_HIER_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX PLAN_FK1 ON PLAN ( EVENT_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX PLAN_FK2 ON PLAN ( SCOPE_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX PLAN_FK3 ON PLAN ( APP_USER_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX PLAN_OBJ_IX1 ON PLAN_OBJECTIVE ( PLAN_SK ASC, KPI_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX PLAN_OPT_SET_IX1 ON PLAN_OPT_SETTING ( PLAN_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX PLAN_VEH_ASG_IX1 ON PLAN_VEHICLE_ASSIGNMENT ( VEHICLE_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX PLAN_VEH_ASG_IX2 ON PLAN_VEHICLE_ASSIGNMENT ( PROD_HIER_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX PLAN_VEH_ASG_IX3 ON PLAN_VEHICLE_ASSIGNMENT ( GEO_HIER_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX PLAN_VEH_ASG_IX4 ON PLAN_VEHICLE_ASSIGNMENT ( PLAN_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX PGRID_RNG_FK1 ON PRICE_GRID_RANGE ( PRICE_GRID_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX PGRID_RNG_VAL_FK1 ON PRICE_GRID_RANGE_VAL ( PRICE_GRID_RANGE_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX PVAL_TYPE_OVRD_FK1 ON PRICE_VALUE_TYPE_OVERRIDE ( PLAN_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX PVAL_TYPE_OVRD_FK2 ON PRICE_VALUE_TYPE_OVERRIDE ( PROD_HIER_SK ASC, GEO_HIER_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX PROC_MSG_DET_FK1 ON PROCESS_MESSAGE_DETAIL ( MESSAGE_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX PROC_MSG_DET_FK2 ON PROCESS_MESSAGE_DETAIL ( PROCESS_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX PROC_STATUS_IX1 ON PROCESS_STATUS ( PROCESS_NM ASC) ALLOW REVERSE SCANS; CREATE INDEX PROD_NO_MIX_FK1 ON PROD_NO_MIX ( PROD_HIER_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX SAVED_ENTITY_IX1 ON SAVED_ENTITY ( GLOBAL_UNIQUE_ID ASC) ALLOW REVERSE SCANS; CREATE INDEX SAVED_REPORT_FK1 ON SAVED_REPORT ( APP_USER_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX SAVED_REP_PARM_FK1 ON SAVED_REPORT_PARM ( SAVED_REPORT_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX SCOPE_DETAIL_FK1 ON SCOPE_DETAIL ( SCOPE_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX SCOPE_DETAIL_FK2 ON SCOPE_DETAIL ( PROD_HIER_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX SCOPE_DETAIL_FK3 ON SCOPE_DETAIL ( GEO_HIER_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX STATUS_TRANS_FK1 ON STATUS_TRANSITION ( FROM_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX STATUS_TRANS_FK2 ON STATUS_TRANSITION ( TO_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX USER_VEH_FK1 ON USER_VEHICLE ( APP_USER_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX USER_VEH_FK2 ON USER_VEHICLE ( VEHICLE_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX USER_VEH_FK3 ON USER_VEHICLE ( PLAN_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX USER_VEH_FK4 ON USER_VEHICLE ( STATUS_CD ASC) ALLOW REVERSE SCANS; CREATE INDEX VEHICLE_FK1 ON VEHICLE ( VEHICLE_CATEGORY_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX VEHICLE_FK2 ON VEHICLE ( CAL_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX VEHICLE_FK3 ON VEHICLE ( SCOPE_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX VEHICLE_ATTR_FK1 ON VEHICLE_ATTR ( VEHICLE_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX VEH_CAT_ATTR_FK1 ON VEHICLE_CATEGORY_ATTR ( VEHICLE_CATEGORY_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX CPLAN_MTR_FK1 ON CLR_PLAN_METRICS ( CLR_PLAN_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX CPLAN_MTR_AGG_FK1 ON CLR_PLAN_METRICS_AGG ( CLR_PLAN_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX CLR_PLAN_PCHGM_IX1 ON CLR_PLAN_PRICE_CHANGE_METRICS ( CLR_PLAN_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX CSPC_IX1 ON CLR_SUBPROD_PRICE_CHANGE ( CLR_PLAN_PRICE_CHANGE_SK ASC) ALLOW REVERSE SCANS; CREATE INDEX GEO_PROD_AGG_IX1 ON GEO_PROD_AGG ( WHOLE_PROD_HIER_SK ASC) ALLOW REVERSE SCANS; CREATE UNIQUE INDEX GEO_DM_IX1 ON GEOGRAPHY_DM ( GEO_ID) ALLOW REVERSE SCANS; CREATE UNIQUE INDEX GEO_HIER_IX1 ON GEOGRAPHY_HIER_ASSOC_DM ( GEO_HIER_SK , PARENT_GEO_LVL) ALLOW REVERSE SCANS; CREATE INDEX GEO_HIER_IX2 ON GEOGRAPHY_HIER_ASSOC_DM ( GEO_HIER_SK) ALLOW REVERSE SCANS; CREATE INDEX GEO_HIER_IX3 ON GEOGRAPHY_HIER_ASSOC_DM ( PARENT_GEO_HIER_SK) ALLOW REVERSE SCANS; CREATE INDEX PROD_DM_IX1 ON PRODUCT_DM ( BRAND_NM) ALLOW REVERSE SCANS; CREATE INDEX PROD_DM_IX2 ON PRODUCT_DM ( PROD_ID) ALLOW REVERSE SCANS; CREATE INDEX PROD_DM_IX3 ON PRODUCT_DM ( VENDOR_SK) ALLOW REVERSE SCANS; CREATE UNIQUE INDEX PROD_HIER_IX1 ON PRODUCT_HIER_ASSOC_DM ( PROD_HIER_SK , PARENT_PROD_LVL) ALLOW REVERSE SCANS; CREATE INDEX PROD_HIER_IX2 ON PRODUCT_HIER_ASSOC_DM ( PROD_HIER_SK) ALLOW REVERSE SCANS; CREATE INDEX PROD_HIER_IX3 ON PRODUCT_HIER_ASSOC_DM ( PARENT_PROD_HIER_SK) ALLOW REVERSE SCANS; On the SAS Server machine, perform the following steps: STEP 1: Before you import metadata, ensure that the SAS foundation hot fix E9BA54 is installed on the SAS Metadata Server: http://ftp.sas.com/techsup/download/hotfix/e9_sbcs_prod_list.html#E9BA54 STEP 2: Import 6 updated ETL Studio jobs as follows: a) In Data Integration Studio, select Tools ->Job Import and Merge Wizard. Click Add. b) Browse to the location where the ETL package has been extracted: !SASROOT/misc/di/etlxml Or copy the files from the server location to a local filesystem c) Select the updated XML files. Click Next. d) Click Finish, and the wizard imports the jobs into the repository. STEP 3: Import reports as follows: a) Log In to SAS Management Console as miuser, in the navigation window, expand the BI Manager to navigate to BI Manager -> BIP Tree -> Report Studio -> Shared -> Reports -> Stored Processes b) In the display window, right-click the Price Change Budget Impact stored process and select Delete. c) In the navigation window, right-click on the BI MANAGER folder and select Import. Click Browse to specify the location of the mireports.spk : !SASROOT/misc/di/config/cfg Or copy the file from the server location to a local filesystem d) Select All Objects, then click Next e) Deselect all objects except Price Change Budget Impact. Click next. f) For the target server select MIPool. g) For target path, select !sasroot/sasstp/dipcl/ h) Then Import to import the package. i) In the Login on to MIPooled enter the following information: 1. User ID: miuser 2. Enter the password for miuser. 3. Select OK j) Click Finish to exit the wizard. You can ignore the warning about missing resource source code. STEP 4: Run the standard weekly job flow for incremental updates, which includes the following steps to update metrics and plans: a) Macro dicpo_rpt_clr_item_metrics_exe b) Macro dipcl_etl_geo_prod_agg c) Auto-optimize and auto-evaluate markdown plans See the SAS Revenue Optimization 2.2 Data Administrator’s Guide. This completes the installation of hot fix 22RO02 on AIX.