SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 52971: Results are incorrect when you use the operator EXACTLY MATCHES in the custom details of SAS® Marketing Automation

DetailsHotfixAboutRate It

In SAS Marketing Automation, using the operator EXACTLY MATCHES to correlate two fields produces an incorrect result. This problem occurs when custom details are populated by a dynamic list from an Oracle database.

For example, you have two fields, Communication Code and Communication Key, where a single communication code is related to many communication keys. You create two custom details that load dynamic lists from the Oracle database. Then, you create a Communication Key dependent on Communication Code dependencies relationship, using the operator EXACTLY MATCHES. When you select a specific communication code, you should see multiple communication keys in the resulting drop-down list. However, the drop-down list is empty and fails to display any exact matches.

To work around this issue, use the operator CONTAINS instead of EXACTLY MATCHES.

Click the Hot Fix tab in this note to access the hot fix for this issue.

After you apply the hot fix, enable the following Java option:

-Dcom.sas.prompts.trimvalues=true

To enable the Java argument in Microsoft Windows operating environments (where servers are started as Windows services):

  1. Navigate to the server location where the sas.wip.services.war file is located. That location is, typically, SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer1_1\sas_webapps.
  2. Navigate to the SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer1_1\conf directory and open the wrapper.conf file.
  3. Add the new argument to the wrapper.conf file, as shown below:
    wrapper.java.additional.XX=-Dcom.sas.prompts.trimvalues=true
    In this argument, XX represents the next number in the sequence that already exists in the file. For the new argument, modify XX to be the next number in that sequence.

To enable the option in Linux or other UNIX operating environments:

  1. Navigate to the server location where the sas.wip.services.war file is located. That location is, typically. SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer1_1\sas_webapps.
  2. Navigate to the directory that contains the setenv.sh file. This file is typically located in the SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/bin directory.
  3. Add the -Dcom.sas.prompts.trimvalues=true option to the setenv.sh file, as shown in the last argument in the following example:
    JVM_OPTS="-Xdebug -Xrunjdwp:transport=dt_socket,address=8003,server=y,suspend=n
    -Xmx4096m -Xss256k -Xms1024m
    -XX:PermSize=768m -XX:MaxPermSize=1280m -d64 -XX:NewRatio=8
    -XX:+UseConcMarkSweepGC -XX:+UseTLAB -XX:+DisableExplicitGC
    -XX:+CMSIncrementalMode -XX:+CMSClassUnloadingEnabled -XX:+UseCompressedOops
    -XX:ReservedCodeCacheSize=96m
    -Djava.awt.headless=true -Dcom.sas.services.logging.disableRemoteLogging=true
    -Dcom.sas.log.config.ignoreContextClassLoader=true
    -Dsas.svcs.http.max.connections=512 -Dcom.sas.prompts.trimvalues=true"
  4. After you add the option, restart your system so that the setting takes effect.


Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Marketing AutomationWindows 7 Enterprise 32 bit6.1_M1 9.3 TS1M29.4 TS1M4
Microsoft Windows XP Professional6.1_M19.3 TS1M2
Microsoft Windows Server 2012 Std6.1_M1 9.3 TS1M29.4 TS1M4
Microsoft Windows Server 2012 R2 Std6.1_M1 9.3 TS1M29.4 TS1M4
Microsoft Windows Server 2012 R2 Datacenter6.1_M1 9.3 TS1M29.4 TS1M4
Microsoft Windows Server 2012 Datacenter6.1_M1 9.3 TS1M29.4 TS1M4
Microsoft Windows Server 2008 for x646.1_M1 9.3 TS1M29.4 TS1M4
Microsoft Windows Server 2008 R26.1_M1 9.3 TS1M29.4 TS1M4
Microsoft Windows Server 20086.1_M1 9.3 TS1M29.4 TS1M4
Microsoft Windows Server 2003 for x646.1_M19.3 TS1M2
Microsoft Windows Server 2003 Standard Edition6.1_M19.3 TS1M2
Microsoft Windows Server 2003 Enterprise Edition6.1_M19.3 TS1M2
Microsoft Windows Server 2003 Datacenter Edition6.1_M19.3 TS1M2
Microsoft Windows 8.1 Pro x646.1_M1 9.3 TS1M29.4 TS1M4
Microsoft Windows 8.1 Pro 32-bit6.1_M1 9.3 TS1M29.4 TS1M4
Microsoft Windows 8.1 Enterprise x646.1_M1 9.3 TS1M29.4 TS1M4
Microsoft Windows 8.1 Enterprise 32-bit6.1_M1 9.3 TS1M29.4 TS1M4
Microsoft Windows 8 Pro x646.1_M1 9.3 TS1M29.4 TS1M4
Microsoft Windows 8 Pro 32-bit6.1_M1 9.3 TS1M29.4 TS1M4
Microsoft Windows 8 Enterprise x646.1_M1 9.3 TS1M29.4 TS1M4
Microsoft Windows 8 Enterprise 32-bit6.1_M1 9.3 TS1M29.4 TS1M4
Microsoft® Windows® for x646.1_M1 9.3 TS1M29.4 TS1M4
Microsoft Windows XP 64-bit Edition6.1_M19.3 TS1M2
Microsoft Windows Server 2003 Enterprise 64-bit Edition6.1_M19.3 TS1M2
Microsoft Windows Server 2003 Datacenter 64-bit Edition6.1_M19.3 TS1M2
Microsoft® Windows® for 64-Bit Itanium-based Systems6.1_M19.3 TS1M2
Windows 7 Enterprise x646.1_M1 9.3 TS1M29.4 TS1M4
Windows 7 Home Premium 32 bit6.1_M1 9.3 TS1M29.4 TS1M4
Windows 7 Home Premium x646.1_M1 9.3 TS1M29.4 TS1M4
Windows 7 Professional 32 bit6.1_M1 9.3 TS1M29.4 TS1M4
Windows 7 Professional x646.1_M1 9.3 TS1M29.4 TS1M4
Windows 7 Ultimate 32 bit6.1_M1 9.3 TS1M29.4 TS1M4
Windows 7 Ultimate x646.1_M1 9.3 TS1M29.4 TS1M4
Windows Vista6.1_M19.3 TS1M2
Windows Vista for x646.1_M19.3 TS1M2
64-bit Enabled AIX6.1_M1 9.3 TS1M29.4 TS1M4
64-bit Enabled HP-UX6.1_M1 9.3 TS1M29.4 TS1M4
64-bit Enabled Solaris6.1_M1 9.3 TS1M29.4 TS1M4
HP-UX IPF6.1_M1 9.3 TS1M29.4 TS1M4
Linux6.1_M1 9.3 TS1M29.4 TS1M4
Linux for x646.1_M1 9.3 TS1M29.4 TS1M4
Solaris for x646.1_M1 9.3 TS1M29.4 TS1M4
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.