Problem Note 56885: SAS® Customer Intelligence campaigns fail and return a syntax error when you connect to the common data model
SAS Customer Intelligence campaigns fail when the following conditions are true:
- You use the QUERY_BAND= option in the LIBNAME statement that is used to connect to the common data model.
- The database is Teradata.
If you encounter this problem, the following error appears in the SASCustIntelCore6.x.log file:
MPRINT(MACDICHE): proc sql noerrorstop;
NOTE: Line generated by the macro variable "DBCONNECT".
167 connect to TERADATA( DEFER=YES CONNECTION=SHARED QUERY_BAND="org=CDM;report=XXX;"
TPT=NO SERVER="xxx.sas.com" USER=sasdemo
_
79
167 ! PASSWORD=******** );
MPRINT(MACDICHE): connect to TERADATA( DEFER=YES CONNECTION=SHARED QUERY_BAND="org=CDM;
NOTE: Line generated by the macro variable "DBCONNECT".
167 connect to TERADATA( DEFER=YES CONNECTION=SHARED QUERY_BAND="org=CDM;report=XXX;"
TPT=NO SERVER="xxx.sas.com" USER=sasdemo
_
79
167 ! PASSWORD=******** );
ERROR 79-322: Expecting a ).
NOTE: Line generated by the macro variable "DBCONNECT".
167 connect to TERADATA( DEFER=YES CONNECTION=SHARED QUERY_BAND="org=CDM;report=XXX;"
TPT=NO SERVER="xxx.sas.com" USER=sasdemo
______
180
167 ! PASSWORD=******** );
ERROR 180-322: Statement is not valid or it is used out of proper order.
NOTE: You do not encounter this problem if you use the QUERY_BAND= option in the LIBNAME statement to connect to the data mart.
The only circumvention for this problem is to avoid using the QUERY_BAND= option for the common data model.
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.1_M1 | 6.5 | | 9.4 TS1M3 |
64-bit Enabled AIX | 6.1_M1 | 6.5 | | 9.4 TS1M3 |
64-bit Enabled Solaris | 6.1_M1 | 6.5 | | 9.4 TS1M3 |
HP-UX IPF | 6.1_M1 | 6.5 | | 9.4 TS1M3 |
Linux for x64 | 6.1_M1 | 6.5 | | 9.4 TS1M3 |
Solaris for x64 | 6.1_M1 | 6.5 | | 9.4 TS1M3 |
*
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-04-25 10:02:07 |
Date Created: | 2015-10-22 09:12:02 |