SAS Real-Time Decision Manager introduces a choice of how to write to the SAS^® Customer Intelligence Common Data Model. Three different subdiagrams (flows) are provided for this functionality. You can choose to activate any of the following subdiagrams:

• the subdiagram that uses DS2 to write to the common data model,
• the subdiagram that uses the traditional mid-tier plus workspace server method
• the subdiagram that does not write to the common data model at all

If you choose to activate the flow that uses DS2, then you might receive a message similar to the following saying that the subdiagram (flow) failed to activate:

ERROR [00016948] App.Statement.Statement.PrepareWithNumResultCols 
125:fedadmin@SASBAP - 74; fedadmin; 1.1.4; T_PREP_NUM_RES_COLS: 
PREP: Table Service: Function failed.  Diagnostics: SQLState=42000, 
NativeRC=81BFC10B, Text: Syntax error at or near "\". 

This failure is caused by incorrect SQL code in the DS2 that is associated with the DS2 subdiagram. The SQL code incorrectly contains backslashes in the catalog and schema names.

Here is an example of the incorrect SQL:

INSERT INTO CIDB."CDM"."CI_CONTACT_HISTORY" ("CELL_PACKAGE_SK", "CONTACT_DTTM",
"CONTACT_DT", "CONTACT_HISTORY_STATUS_CD",  \    "PACKAGE_HASH_VAL",
"OPTIMIZATION_BACKFILL_FLG", \    "EXTERNAL_CONTACT_INFO_ID1",
"EXTERNAL_CONTACT_INFO_ID2", "RESPONSE_TRACKING_CD","INDIVID") VALUES
(?,?,?,?,?,'N',?,?,?,?) 

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

After you apply the hot fix, you need to use SAS^® Management Console to delete two SAS Contact History DS2 activity resources in order to complete the fix.

In SAS Management Console, the paths to the two resources are as follows:

• Folders ► System ► Applications ► SAS Decision Services ► SASDSDesignRepository _SAS_CHUPDATE_DS2_ACTIVITY
  

  

• Folders ► System ► Applications ► SAS Decision Services ► SASDSEngineRepository _SAS_CHUPDATE_DS2_ACTIVITY
  

  

After you delete these resources, you need to restart the deployment.

Operating System and Release Information

A fix for this issue for SAS Marketing Automation 6.4 is available at:

A fix for this issue for SAS Marketing Automation 6.3 is available at: