SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 62102: The error "The table MATables does not exist" occurs when you execute static Link nodes in SAS® Customer Intelligence Studio

DetailsHotfixAboutRate It

In SAS Customer Intelligence Studio, you might receive an error message when you use static Link nodes in campaigns. This problem happens when you perform steps similar to the following:

  1. Create a campaign called Layer1 that contains a Select node and a Cell node.
  2. Make the Cell node available for linking and clear the property Use the most current data when referenced by a link. Choose whether to execute the campaign and then save and close the campaign.
  3. Create a campaign called Layer2 that contains a Link node that points to the Cell node in Layer1 and that contains a Cell node.
  4. Make the Cell node available for linking and clear the property Use the most current data when referenced by a link. Choose whether to execute the campaign. Then save and close the campaign.
  5. Create a campaign called Layer3 with a Link node that is linked to the Cell node in Layer2. Then add one of the following types of nodes:  LIMIT, PRIO, ANDOR, or PROCESS.
  6. Execute campaign Layer3. When you execute the campaign, the counts are updated properly.
  7. Change the selection criteria in campaign Layer1. Then execute and save the campaign.
  8. Execute the Layer3 campaign again.

When you execute Layer3 again, the execution fails and the following error is generated:

2018-03-01 16:10:58,533 ERROR [CITaskCleanup-9] [bf515236f5c2e9e0:23b11c9e:161e10ee533:-a8] [sasdemo]
com.sas.analytics.crm.flow.MALimitNode   - A table (MATables.TECAFGZ015JCCSMFIsasdemo) referenced by the node Link to Link Cell Layer2 is no longer available.  Clear all counts before attempting to update counts again., MA Return Code: 1123, MA Return Message: The table MATables.TECAFGZ015JCCSMFIsasdemo does not exist., SAS Return Code: 5

As a workaround, close all three Layer campaigns and make sure that the Cell nodes do have counts before you save the campaigns.

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

 

Note: After you apply the hot fix, the following new Java argument is introduced:

-Dcom.sas.ci.staticlinknode.owntable=true

When this property is enabled, link nodes *always* hold a copy of the MATable to which they point.

  • For Microsoft Windows operating environments (in which the servers are started as Windows services):

Navigate to the SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer6_1\conf directory and add the new argument to the wrapper.conf file, as shown below:

wrapper.java.additional.XX=-Dcom.sas.ci.staticlinknode.owntable=true

In this argument, XX represents the next number in the sequence that already exists in the file. Modify XX to be the next number in that sequence.

  • For Linux or other UNIX operating environments:

Add the option to the setenv.sh file, as shown below:

JAVA_OPTS="$JAVA_OPTS -Dcom.sas.ci.staticlinknode.owntable=true"

The setenv.sh file is typically located in the SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer6_1/bin directory.

After you add the argument, restart the middle tier so that the setting can take effect.

Note: It is assumed that the following properties are also set:

set JAVA_OPTS=%JAVA_OPTS% -Dcom.sas.ci.alwaysrunlinknode=true
set JAVA_OPTS=%JAVA_OPTS% -Dcom.sas.ci.alwaysrunlinknode.cis.latest=true
 

These options are described in the following SAS Notes:

  • SAS Note 60225, "Enabling the option "Use the most current data when referenced by a link" only returns current data when a campaign is executed"
  • SAS Note 61240, Counts are not updated when you execute a campaign multiple times in the same SAS® Customer Intelligence Studio session

 



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Customer Intelligence StudioMicrosoft® Windows® for x646.46.69.4 TS1M29.4 TS1M6
Microsoft Windows 8 Enterprise 32-bit6.46.69.4 TS1M29.4 TS1M6
Microsoft Windows 8 Enterprise x646.46.69.4 TS1M29.4 TS1M6
Microsoft Windows 8 Pro 32-bit6.46.69.4 TS1M29.4 TS1M6
Microsoft Windows 8 Pro x646.46.69.4 TS1M29.4 TS1M6
Microsoft Windows 8.1 Enterprise 32-bit6.46.69.4 TS1M29.4 TS1M6
Microsoft Windows 8.1 Enterprise x646.46.69.4 TS1M29.4 TS1M6
Microsoft Windows 8.1 Pro 32-bit6.46.69.4 TS1M29.4 TS1M6
Microsoft Windows 8.1 Pro x646.46.69.4 TS1M29.4 TS1M6
Microsoft Windows 106.46.69.4 TS1M29.4 TS1M6
Microsoft Windows Server 20086.46.69.4 TS1M29.4 TS1M6
Microsoft Windows Server 2008 R26.46.69.4 TS1M29.4 TS1M6
Microsoft Windows Server 2008 for x646.46.69.4 TS1M29.4 TS1M6
Microsoft Windows Server 2012 Datacenter6.46.69.4 TS1M29.4 TS1M6
Microsoft Windows Server 2012 R2 Datacenter6.46.69.4 TS1M29.4 TS1M6
Microsoft Windows Server 2012 R2 Std6.46.69.4 TS1M29.4 TS1M6
Microsoft Windows Server 2012 Std6.46.69.4 TS1M29.4 TS1M6
Windows 7 Enterprise 32 bit6.46.69.4 TS1M29.4 TS1M6
Windows 7 Enterprise x646.46.69.4 TS1M29.4 TS1M6
Windows 7 Home Premium 32 bit6.46.69.4 TS1M29.4 TS1M6
Windows 7 Home Premium x646.46.69.4 TS1M29.4 TS1M6
Windows 7 Professional 32 bit6.46.69.4 TS1M29.4 TS1M6
Windows 7 Professional x646.46.69.4 TS1M29.4 TS1M6
Windows 7 Ultimate 32 bit6.46.69.4 TS1M29.4 TS1M6
Windows 7 Ultimate x646.46.69.4 TS1M29.4 TS1M6
64-bit Enabled AIX6.46.69.4 TS1M29.4 TS1M6
64-bit Enabled Solaris6.46.69.4 TS1M29.4 TS1M6
HP-UX IPF6.46.69.4 TS1M29.4 TS1M6
Linux for x646.46.69.4 TS1M29.4 TS1M6
Solaris for x646.46.69.4 TS1M29.4 TS1M6
* 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.