Problem Note 50873: The contact history records are not updated as failed contacts when the underlying broadcasts return as hard bounces
SAS® Customer Intelligence campaign contact history records are not being updated as failed contacts when the associated SAS® Digital Marketing broadcast e-mails return as hard bounces.
When the underlying database is Teradata, this might occur because the database schema is not known. The only way to deduce this is to review the SAS Customer Intelligence reporting log for the implicit pass-through SQL, which updates the contact history:
execute ( MERGE INTO CI_CELL_PACKAGE tt USING
PROD_MA_WRK_TB.CH_CP_FAILED_CNT121304 st ON ( tt.CELL_PACKAGE_SK =
st.CELL_PACKAGE_SK ) WHEN MATCHED THEN UPDATE SET
TOTAL_ATTEMPTED_CONTACT_CNT = TOTAL_ATTEMPTED_CONTACT_CNT - st.FAILED_CNT,
TOTAL_MARKETING_CONTACT_CNT = TOTAL_MARKETING_CONTACT_CNT - st.FAILED_CNT,
PROCESSED_DTTM = CURRENT_TIMESTAMP ) by TERADATA;
Notice that the
MERGE INTO CI_CELL_PACKAGE clause does not have a schema preceding the table name.
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 Reporting Mid-Tier | Microsoft® Windows® for x64 | 5.4 | 6.1 | 9.2 TS2M3 | 9.3 TS1M0 |
64-bit Enabled AIX | 5.4 | 6.1 | 9.2 TS2M3 | 9.3 TS1M0 |
64-bit Enabled Solaris | 5.4 | 6.1 | 9.2 TS2M3 | 9.3 TS1M0 |
HP-UX IPF | 5.4 | 6.1 | 9.2 TS2M3 | 9.3 TS1M0 |
Linux for x64 | 5.4 | 6.1 | 9.2 TS2M3 | 9.3 TS1M0 |
Solaris for x64 | 5.4 | 6.1 | 9.2 TS2M3 | 9.3 TS1M0 |
*
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.
This problem occurs when you are using the Teradata database.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2013-08-29 15:23:23 |
Date Created: | 2013-08-27 16:32:36 |