Problem Note 64941: An error occurs and publishing to the Contact History fails in SAS® Customer Intelligence when you use SAS/ACCESS® Interface to Microsoft SQL Server
Publishing to the Contact History table might fail when you use the SAS/ACCESS SQLSVR engine for the Microsoft SQL Server interface. When this problem occurs, the following error is displayed in the SASApp_STPServer_xxxx.log file:
MPRINT(MACDICHE): proc sql noerrorstop;
MPRINT(MACDICHE): connect to SQLSVR( READBUFF=32767 DATASRC=CDM USER=sasdemo PASSWORD=******** connection=global );
MPRINT(MACDICHE): ;
MPRINT(MACDICHE): execute(insert into CDM.CI_CONTACT_HISTORY_KL ( PART_PK,CELL_PACKAGE_SK, RESPONSE_TRACKING_CD, CONTACT_HISTORY_STATUS_CD,
PACKAGE_HASH_VAL, OPTIMIZATION_BACKFILL_FLG,CONTACT_DTTM, CONTACT_DT ) select PART_PK, CELL_PACKAGE_SK,RESPONSE_TRACKING_CD, CHSTATUS_CD,
PACKAGE_HASH_VAL, OPTIMIZATION_BACKFILL_FLG,
'2019-10-01 17:24:14.717', '2019-10-01' from CH6D8C748A1A8B553B36A0C_001 )by SQLSVR;
ERROR: CLI execute error: [SAS][ODBC SQL Server Wire Protocol driver][MicrosoftSQL Server]Invalid object name 'CH6D8C748A1A8B553B36A0C_001'.
MPRINT(MACDICHE): disconnect from SQLSVR;
MPRINT(MACDICHE): quit;
This issue occurs only when you enable the option Use temporary table capability of database that is available when you select Settings ► Options in the Business Context Properties dialog box, as shown below:
To work around this problem, disable the option in the Business Context Properties dialog box.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Customer Intelligence Core Mid-Tier | Microsoft® Windows® for x64 | 6.5 | 6.6 | | 9.4 TS1M6 |
64-bit Enabled AIX | 6.5 | 6.6 | | 9.4 TS1M6 |
64-bit Enabled Solaris | 6.5 | 6.6 | | 9.4 TS1M6 |
HP-UX IPF | 6.5 | 6.6 | | 9.4 TS1M6 |
Linux for x64 | 6.5 | 6.6 | | 9.4 TS1M6 |
Solaris for x64 | 6.5 | 6.6 | | 9.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.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2019-12-17 16:39:28 |
Date Created: | 2019-10-15 11:56:13 |