![]() | ![]() | ![]() | ![]() | ![]() |
When you have a communication node exporting into two tables in Oracle, the update to the Contact History might not complete correctly.
For example:
Task #7, Export Node Name Communication SMS_1 export started - 20090317:15.43.06,15 completed - 20090317:15.43.11,36 ... Task #8, Export Node Name Communication SMS_2 export started - 20090317:15.42.58,85 completed - 20090317:15.43.02,21
... Task #9, Node Name Communication SMS ma_cdi_update_ch.sas started - 20090317:15.43.02,70 completed - 20090317:15.43.03,39 ...
Task #9 is the contact history update, Task #8 is one of the exports and Task #7 is the other one.
Note that Task #9 is dependent only on Task #8, not on Task #7, so if Task
#8 finishes before Task #7 finishes, the contact history update will start
before Task #7 export completes and the contact history will not be updated correctly.
Select the Hot Fix tab in this note to access the hot fix for this issue.
Product Family | Product | System | Product Release | SAS Release | ||
Reported | Fixed* | Reported | Fixed* | |||
SAS System | SAS Customer Intelligence Studio | Microsoft Windows 2000 Server | 5.1 | 9.1 TS1M3 SP4 | ||
Microsoft Windows 2000 Datacenter Server | 5.1 | 9.1 TS1M3 SP4 | ||||
Microsoft Windows 2000 Professional | 5.1 | 9.1 TS1M3 SP4 | ||||
Microsoft Windows NT Workstation | 5.1 | 9.1 TS1M3 SP4 | ||||
Microsoft Windows 2000 Advanced Server | 5.1 | 9.1 TS1M3 SP4 | ||||
Microsoft Windows Server 2003 Datacenter Edition | 5.1 | 5.3 | 9.1 TS1M3 SP4 | 9.2 TS2M0 | ||
Microsoft Windows Server 2003 Enterprise Edition | 5.1 | 5.3 | 9.1 TS1M3 SP4 | 9.2 TS2M0 | ||
Microsoft Windows Server 2003 Standard Edition | 5.1 | 5.3 | 9.1 TS1M3 SP4 | 9.2 TS2M0 | ||
Microsoft Windows XP Professional | 5.1 | 5.3 | 9.1 TS1M3 SP4 | 9.2 TS2M0 | ||
Windows Vista | 5.1 | 5.3 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |