Hot fix M46006 addresses the issue(s) in SAS Fraud Management 3.3 as documented in the Issue(s) Addressed section of the hot fix download page:
M46006 is a "container" hot fix that contains the following "member" hot fixes which will update the software components as needed.
M48003 updates SAS Fraud Management Alert Generation Server 3.3
M53001 updates SAS Fraud Management Common Macros 3.3
M47003 updates SAS Fraud Management Mid-Tier 3.3
U90001 updates SAS Fraud Management Multi Entity History DB Maintenance Macros 3.3
P82002 updates SAS Fraud Management Reporting History DB Maintenance Macros 3.3***
T31001 updates SAS Fraud Management Reporting History ETL Server Macros 3.3
M49002 updates SAS Fraud Management Scoring Engine 3.3
M50002 updates SAS Fraud Management System of Record DB Maintenance Macros 3.3***
P60001 updates SAS Fraud Management Transaction Extensions 3.3
*** member hot fixes that have been updated since the previously released hot fix (M46005)
|Software Component||Server||M46001 HF1||M46002 HF2||M46003 HF3||M46004 HF4||M46005 HF5||M46006 HF6|
|SAS FM Alert Generation Server 3.3||AGS||M48001||M48002||-||-||M48003||-|
|SAS FM Common Macros 3.3||Rules Server/AGS/JOSE||M53001||-||-||-||-||-|
|SAS FM Mid-Tier 3.3||Midtier||M47001||M47002||-||-||M47003||-|
|SAS FM Multi Entity History DB Maintenance Macros 3.3||JOSE||-||-||-||U90001||-||-|
|SAS FM Reporting History DB Maintenance Macros 3.3||Rules Server/AGS/JOSE||-||P82001||-||-||-||P82002|
|SAS FM Reporting History ETL Server Macros 3.3||Rules Server/AGS||-||-||T31001||-||-||-|
|SAS FM Scoring Engine 3.3||JOSE||M49001||M49002||-||-||-||-|
|SAS FM System of Record DB Maintenance Macros 3.3||AGS||M50001||-||-||-||-||M50002|
|SAS FM Transaction Extensions 3.3||Rules Server/AGS/JOSE||-||P60001||-||-||-||-|
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, M46006pt.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 M46006pt.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of M46006pt.zip. The hot fix installation process will extract the contents as needed.
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 M46006pt.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.logfor 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.
Database updates are generally performed by the DBA. The instructions for each file should be reviewed before running each update.
Create a "M46006pt" directory on your machine and unzip the contents of M46006pt.zip into that directory.
Go to the M46006pt/Miscellaneous directory. Based on the table below, determine which files need to be run and copy those files to the appropriate database server.
|DB2||SOR||HF2||sor_db2_upgrade_22.214.171.124.tar||Installation Instructions for DB2_SOR updates|
|DB2||MEH||HF4||meh_db2_upgrade_126.96.36.199.tar||Installation Instructions for DB2_MEH updates|
|DB2||SOR||HF6||sor_db2_upgrade_188.8.131.52.tar||Installation Instructions for DB2_SOR updates|
In order for this step to execute correctly, the Metadata Server must be running.
$ export DISPLAY=<displayname>:0
From the SASDeploymentManager directory execute sasdm.sh, for example
$ cd <SASHOME>/SASDeploymentManager/9.3
Re-deploy the web applications based on the instructions appropriate for your web application server. See SAS 9.3 Intelligence Platform Middle-Tier Administration Guide, Chapter 7, for more details.