Problem Note 57068: Invalid dates are inserted into the contact history after the initial contact history insert fails
 |  |  |  |  |
When you initially insert data into the SAS® Real-Time Decision Manager contact-history table, sometimes that insertion fails. This failure is normal in some cases. However, when the automatic recovery process is initiated after such a failure, the process inserts invalid dates into the contact-history table.
When the failure occurs, the following log messages appear in the SASCustIntelCore6.x.log file:
- insert into RTDMCDM_O.CI_CONTACT_HISTORY ( CLIENTNUM, CELL_PACKAGE_SK,
RESPONSE_TRACKING_CD, CONTACT_HISTORY_STATUS_CD, PACKAGE_HASH_VAL, OPTIMIZATION_BACKFILL_FLG, CONTACT_DTTM,
CONTACT_DT , EXTERNAL_CONTACT_INFO_ID1, EXTERNAL_CONTACT_INFO_ID2 ) select CLIENTNUM , CELL_PACKAGE_SK,
RESPONSE_TRACKING_CD, CHSTATUS_CD, PACKAGE_HASH_VAL, OPTIMIZATION_BACKFILL_FLG, TO_TIMESTAMP(CDTTM,'YYYY-MM-DD
HH24:MI:SS.FF'), TO_DATE(ctdate,'YYYY-MM-DD'), EXTERNAL_CONTACT_INFO_ID1, EXTERNAL_CONTACT_INFO_ID2 from
RTCOMMOM_C.CI_INTABLE27840201;
- ERROR: ORACLE execute error: ORA-00001: unique constraint (RTDMCDM_O.CONT_HIST_PK) violated.
When the recovery begins, the date values are created incorrectly, as shown below:
- MPRINT(MAPRNOBS): data DBTMPLIB.CI_INTABLE27840201_err;
- MPRINT(MAPRNOBS): length RECORDNUM CDTTM_NUM CTDATE_NUM 8.;
- MPRINT(MAPRNOBS): set DBTMPLIB.CI_INTABLE27840201;
- MPRINT(MAPRNOBS): CDTTM_DT=scan(CDTTM,1,'');
- MPRINT(MAPRNOBS): CDTTM_TM=scan(CDTTM,2,'');
- MPRINT(MAPRNOBS): CDTTM_CHAR=put(input(CDTTM_DT,yymmdd10.),date9.)||':'||put(input(CDTTM_TM,time12.3),tod12.3);
- MPRINT(MAPRNOBS): CDTTM_NUM=input(CDTTM_CHAR,datetime24.3);
- MPRINT(MAPRNOBS): CTDATE_NUM=input(CTDATE,yymmdd10.);
- MPRINT(MAPRNOBS): drop CDTTM_DT CDTTM_TM CDTTM_CHAR;
- MPRINT(MAPRNOBS): RECORDNUM=_n_;
- MPRINT(MAPRNOBS): run;
In addition, the following warning occurs when the process inserts the invalid data into the contact history:
- MPRINT(PRINT_BAD_OBS): proc sql noerrorstop;
- MPRINT(PRINT_BAD_OBS): INSERT INTO RTDMCDM.CI_CONTACT_HISTORY ( CELL_PACKAGE_SK, RESPONSE_TRACKING_CD,
CLIENTNUM, CONTACT_HISTORY_STATUS_CD, CONTACT_DTTM, PACKAGE_HASH_VAL, CONTACT_DT,
OPTIMIZATION_BACKFILL_FLG, EXTERNAL_CONTACT_INFO_ID1, EXTERNAL_CONTACT_INFO_ID2 ) SELECT CELL_PACKAGE_SK,
RESPONSE_TRACKING_CD, DW_NUM_NTC , CHSTATUS_CD, CDTTM_NUM, PACKAGE_HASH_VAL,
CTDATE_NUM,OPTIMIZATION_BACKFILL_FLG, EXTERNAL_CONTACT_INFO_ID1, EXTERNAL_CONTACT_INFO_ID2 FROM BTMPLIB.CI_INTABLE27840201_err WHERE RECORDNUM=420;
- WARNING: This SQL statement is not allowed to be passed directly to the DBMS for processing because the DBIDIRECTEXEC system option is not turned on by the user or is temporarily turned off by Proc SQL.
There is no workaround for this problem.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Real-Time Decision Manager | Microsoft Windows Server 2012 Std | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 |
| Microsoft Windows Server 2012 R2 Std | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2012 R2 Datacenter | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2012 Datacenter | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2008 R2 | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2008 | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2003 for x64 | 6.1 | 9.3 TS1M2 | ||||
| Microsoft Windows Server 2003 Standard Edition | 6.1 | 9.3 TS1M2 | ||||
| Microsoft Windows Server 2003 Enterprise Edition | 6.1 | 9.3 TS1M2 | ||||
| Microsoft Windows Server 2003 Datacenter Edition | 6.1 | 9.3 TS1M2 | ||||
| Microsoft Windows 8.1 Pro 32-bit | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows 8.1 Enterprise x64 | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows 8 Pro x64 | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows 8 Pro 32-bit | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows 8 Enterprise x64 | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows 8 Enterprise 32-bit | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2008 for x64 | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows 8.1 Pro | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows 8.1 Enterprise 32-bit | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft® Windows® for x64 | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows XP Professional | 6.1 | 9.3 TS1M2 | ||||
| Windows 7 Enterprise 32 bit | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Windows 7 Enterprise x64 | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Windows 7 Home Premium 32 bit | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Windows 7 Home Premium x64 | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Windows 7 Professional 32 bit | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Windows 7 Professional x64 | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Windows 7 Ultimate 32 bit | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Windows 7 Ultimate x64 | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Windows Vista | 6.1 | 9.3 TS1M2 | ||||
| Windows Vista for x64 | 6.1 | 9.3 TS1M2 | ||||
| 64-bit Enabled AIX | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| 64-bit Enabled Solaris | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| HP-UX IPF | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Linux for x64 | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Solaris for x64 | 6.1 | 6.5 | 9.3 TS1M2 | 9.4 TS1M3 | ||
A fix for this issue for SAS Marketing Automation 6.4 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/U53.html#57068A fix for this issue for SAS Marketing Automation 6.3 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/R60.html#57068A fix for this issue for SAS Marketing Automation 6.1_M1 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/K78.html#57068| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2015-11-20 16:54:56 |
| Date Created: | 2015-11-11 16:41:26 |