Problem Note 58797: Batch simulation for a decision campaign fails with a fatal error status in SAS® Customer Intelligence Studio
In SAS Customer Intelligence Studio, a batch-simulation run for a decision campaign might finish with a fatal error status, accompanied by the following error in the SAS Decision Services design-server log:
2016-07-29 10:50:32,314 ERROR com.sas.rtdm.implementation.batch.EngineBatchDriver - Fatal error com.sas.analytics.ph.RTDMException: SQLException received while writing to results table: Server error occurred while processing invokeExecute2. Error message: [com.sas.tkts.sql.FSException: T_EXECUTE2: Table Service: Function failed.] SQLSTATE:[22001] MESSAGE:[String data, right-truncated] NATIVEERROR:[-2130708420]
Verify first column is of type string and named 'batch_job_id,' second column is of type string and named 'correlation_id,' and third column is of type string and named 'status_cd.'
Remaining columns must match event reply variable names and types.
Terminating batch job # for event: 'xxxxx'
This issue occurs when character in_out fields are used in a DS2 package that is associated with the decision campaign.
To work around the issue, set the com.sas.analytics.crm.inbound.batch_string_length option equal to 32767 for every SASServer6 node where SAS® Real-Time Decision Manager is deployed. To change the length of character fields to 32767, add the following option to the configuration file:
-Dcom.sas.analytics.crm.inbound.batch_string_length=32767
In Microsoft Windows operating environments, the configuration file (wrapper.conf) resides in the SAS-configuration-file\Levn\Web\WebAppServer\SASServer6_cluster_number\conf\ directory.
In UNIX operating environments, the configuration file (setenv.sh) resides in the SAS-configuration-file/Levn/Web/WebAppServer/SASServer6_cluster_number/bin/ directory.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Real-Time Decision Manager | Microsoft Windows 8 Pro 32-bit | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows 8 Pro x64 | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows 8 Enterprise x64 | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows 8 Enterprise 32-bit | 6.4 | | 9.4 TS1M2 | |
Microsoft® Windows® for x64 | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows 8.1 Enterprise 32-bit | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows 8.1 Enterprise x64 | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows 8.1 Pro 32-bit | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows 8.1 Pro x64 | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows 10 | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows Server 2008 | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows Server 2008 R2 | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows Server 2008 for x64 | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows Server 2012 Datacenter | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows Server 2012 R2 Datacenter | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows Server 2012 R2 Std | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows Server 2012 Std | 6.4 | | 9.4 TS1M2 | |
Windows 7 Enterprise 32 bit | 6.4 | | 9.4 TS1M2 | |
Windows 7 Enterprise x64 | 6.4 | | 9.4 TS1M2 | |
Windows 7 Home Premium 32 bit | 6.4 | | 9.4 TS1M2 | |
Windows 7 Home Premium x64 | 6.4 | | 9.4 TS1M2 | |
Windows 7 Professional 32 bit | 6.4 | | 9.4 TS1M2 | |
Windows 7 Professional x64 | 6.4 | | 9.4 TS1M2 | |
Windows 7 Ultimate 32 bit | 6.4 | | 9.4 TS1M2 | |
Windows 7 Ultimate x64 | 6.4 | | 9.4 TS1M2 | |
64-bit Enabled AIX | 6.4 | | 9.4 TS1M2 | |
64-bit Enabled Solaris | 6.4 | | 9.4 TS1M2 | |
HP-UX IPF | 6.4 | | 9.4 TS1M2 | |
Linux for x64 | 6.4 | | 9.4 TS1M2 | |
Solaris for x64 | 6.4 | | 9.4 TS1M2 | |
*
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.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2016-12-14 13:08:11 |
Date Created: | 2016-08-16 12:59:12 |