Installation Instructions for Hot Fix P64003

64-bit Enabled Solaris

Hot fix P64003 addresses the issue(s) in SAS Customer Experience Targeting Server 6.3 on 64-bit Enabled Solaris as documented in the Issue(s) Addressed section of the hot fix download page:

http://ftp.sas.com/techsup/download/hotfix/HF2/P64.html#P64003

The hot fix downloaded, P64003s6.zip, contains the updated files required to address the documented issues.
Do NOT extract the contents of P64003s6.zip. The hot fix installation process will extract the contents as needed.

IMPORTANT NOTES

1. You must have SAS Customer Experience Targeting Server 6.3 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.

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

3. You must have Administrator Privileges on your CLIENT or SERVER machine.

4. All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix.

5. This hot fix should be installed using the same userid who performed the initial software installation.

6. During the hot fix installation process, be sure to deselect the 'Configure SAS hot fix' check box when prompted.

INSTALLATION

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

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

POST-INSTALLATION INSTRUCTIONS

IMPORTANT: SAS PATCH CODE GIVEN BELOW NEEDS TO BE APPLIED IMMEDIATELY AFTER THE HOTFIX IS APPLIED AND BEFORE CXT ETL RUN.

What you will need to do:

• Ensure SAS Metadata server, SAS Object Spawner, SAS Connect Spawner are all up and running.
• Launch Base SAS from ~/Lev/SASApp as an user who has administrative privileges for CXT.
• Assign CXTWH and CXTCNFG in the SAS session before running the SAS code patch for geo_ip_md5 given below.
• The library statement for CXTWH and CXTCNFG can be obtained by login into SAS DI Studio. To get the CXTWH and CXTCNFG library names.
• Launch SAS DI studio using CXT admin user credentials.
• On the Folders tab, navigate to CXT ETL -> Data Sources -> CXTWH.
• Right-click CXTWH and select ‘view LIBNAME’.
• Copy the library details and paste it in the program editor window and run it.
• Make sure the library is assigned without error.
• Similarly get the library statement for CXTCNFG under the folder CXT ETL -> Data Source -> CXTCNFG and assign that library in the SAS session without any errors in the log.

/*SAS CODE PATCH STARTS*/

/*Take backup of existing CXTCNFG.Geo_ip_md5, just for reference and keep track of what changed with this sas patch code*/
  Data CXTCNFG.Geo_ip_md5_bkp_bef_hotfix;
       Set CXTCNFG.Geo_ip_md5;
  Run;

/*Read the existing dim tables*/
  data work.geo_ip_dim_temp;
     set CXTWH.geo_ip_dim;
  run;

/*Generate old md5 and new md5 based on old and new primary sk values*/
  data work.geo_ip_dim_temp2;
     set work.geo_ip_dim_temp;
        length old_md5 $16 new_md5 $16;
        format old_md5 $hex32. new_md5 $hex32.;

     geo_ip_key_old= compbl(lowcase(trim(longitude)||trim(latitude)||
                  ktrim(country_cd)||trim(state_region_cd)||ktrim(city_nm)));

     old_md5=md5(compbl(geo_ip_key_old));

geo_ip_key_new=compbl(lowcase(trim(longitude)||trim(latitude)||
ktrim(country_cd)||trim(state_region_cd)||ktrim(city_nm)||ktrim(country_nm)||ktrim(organization_nm)||ktrim(region_nm)||trim(metro_cd)));

     new_md5=md5(compbl(geo_ip_key_new));

  run;

  data work.geo_ip_dim_temp2(rename=(new_md5=geo_ip_md5));
     set work.geo_ip_dim_temp2(keep=geo_ip_sk new_md5);
  run;

  proc sort data=work.geo_ip_dim_temp2;
     by geo_ip_sk;
  run;


  proc sort data=CXTCNFG.geo_ip_md5;
     by geo_ip_sk;
  run;

  data CXTCNFG.geo_ip_md5;
      merge CXTCNFG.geo_ip_md5(in=a) work.geo_ip_dim_temp2(in=b);
      by geo_ip_sk;
      if a;
  run;

  proc sql;
       alter table CXTCNFG.geo_ip_md5
          add constraint geo_ip_md5 primary key (geo_ip_md5)
       ;
quit;
/* SAS CODE PATCH ENDS*/

You need to do the following step to fix an issue documented in SN-56298.

1. When Configuring CXT, depending on whether the data warehouse user have create permissions or not, do the following:
   • If the data warehouse user have permissions to create database objects in the target database, then use priming job to initialize CXT.
   • If the data warehouse user does not have the permissions to create the database objects in the target database, use ‘cxt_oracle_ddls.sql’ or ‘cxt_postgres_ddls.sql’ file to create the objects in the target database, then execute the priming job to complete cxt initialization.

2. Do the following changes, if the data warehouse user do not have the permissions to create the database objects in the target database:
   1. Browse to ETL Jobs > 6.3 Jobs > Optional Jobs > Data Archiving job. Right click on the Job transformation and select properties. In the Options tab, select General options in left pane.
      1. Set “Disable indexes prior to delete and rebuild them after delete?” to No.

   2. Browse to ETL Jobs > 6.3 Jobs > Optional Jobs > ETL Reset Job. Right click on the Job transformation ‘cxt_etl_reset’ and select properties. In the Options tab, select General options in left pane.
      1. Set “Rebuild Table Indexes” to None.
      2. Set “Create temporary index on load_dttm” to No.

   3. Browse to ETL Jobs > 6.3 Jobs > ETL Jobs > cxt_1000_pre_extract Job. Right click on the Job transformation and select properties. In the Options tab, select Timeshifting* option in left pane.
      1. Set “Create load_dttm index if it does not exist” to No.
      2. Redeploy the job.

   4. Browse to ETL Jobs > 6.3 Jobs > ETL Jobs. For all the load jobs do the following. Right click on the Job transformation and select properties.
      1. In the Options tab, select General options in left pane. Set “Drop Index?” to No.
      2. In the Options tab, select Additional options in left pane. Set “Generate indexes on target tables” to No.

   5. Browse to ETL Jobs > 6.3 Jobs > ETL Jobs > cxt_1000_pre_extract Job. Right click on the Job transformation and select properties. In the Options tab, select Additional Options* in left pane.
      1. Set “Generate indexes on target tables” to No.