The IBM DB2 profile path is missing in the meh_sasfraud_env.sh file after installing SAS® Fraud Management 6.1


After installing SAS Fraud Management 6.1, the meh_sasfraud_env.sh script that is found in the SAS-configuration-directory/Levn/Applications/SASFraudManagement/6.1/impl-name/batch/common/etc directory is incorrect. The db2profile path is not set. 

The incorrect code is as follows:

if [ -f /db2profile ]; then
     . /db2profile
fi
 

To fix the issue, update the meh_sasfraud_env.sh file to add the path to the db2profile file as shown in the example below. Substitute the path of your db2profile file for the path that is shown in the example.

if [ -f /home/db211cli/sqllib/db2profile ]; then
     . /home/db211cli/sqllib/db2profile
fi

One impact of this issue is that the Multi-Entity History (MEH) database purge job 7099 fails. The job errors that are found in the YY_MM_DD_hh_mm_job_7099_lookup_pid.log file are as follows:

2022-01-12T14:34:12,421 ERROR [00000006] :m4q1bch - ERROR: Could not load /sasvol01/sashome94/SASFoundation/9.4/sasexe/sasdbu (65 images loaded)
2022-01-12T14:34:12,421 ERROR [00000006] :m4q1bch - ERROR: libdb2.so.1: cannot open shared object file: No such file or directory
2022-01-12T14:34:12,421 ERROR [00000006] :m4q1bch - ERROR: The SAS/ACCESS Interface to DB2 cannot be loaded. The SASDBU   code appendage could not be loaded.

This log is located in the SAS-configuration-directory/Levn/Applications/SASFraudManagement/6.1/impl-name/common/logs directory.