SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 55676: The CHANNEL_CD field in the CDM CI_CELL_PACKAGE table is not populated when you execute and publish migrated campaigns

DetailsHotfixAboutRate It

After you migrate to SAS® Customer Intelligence 6.3, migrated campaigns do not populate the CHANNEL_CD field in the CI_CELL_PACKAGE table in the common data model when the campaigns are executed and published.

This issue occurs because the migration process renames the channel codes, making them unavailable for existing campaigns.

To re-create the channels, perform the following steps:

  1. Stop the web application server on which the SAS Customer Intelligence core is deployed (for example, SASServer6_1).
  2. Log on to the SAS® Content Server Administration Console, which is available from this URL: http://middle-tier-host:middle-tier-port/SASContentServer/dircontents.htm?path=/sasdav/Customer+Intelligence/NonUUIDBased/
  3. From the console, delete the All-NewChannelDefinitionPersistenceManager file.
  4. Log off from the SAS Content Server Administration Console.
  5. Start the web application server on which the SAS Customer Intelligence core is deployed (for example, SASServer6_1).
  6. Log on to SAS Customer Intelligence Studio. This action causes the channels to be re-created.

After you perform the steps above, re-create any custom channels that existed on your original system.

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



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Customer Intelligence StudioMicrosoft® Windows® for x646.36.49.4 TS1M2
Microsoft Windows 8 Enterprise 32-bit6.36.49.4 TS1M2
Microsoft Windows 8 Enterprise x646.36.49.4 TS1M2
Microsoft Windows 8 Pro 32-bit6.36.49.4 TS1M2
Microsoft Windows 8 Pro x646.36.49.4 TS1M2
Microsoft Windows 8.1 Enterprise 32-bit6.36.49.4 TS1M2
Microsoft Windows 8.1 Enterprise x646.36.49.4 TS1M2
Microsoft Windows 8.1 Pro6.36.49.4 TS1M2
Microsoft Windows 8.1 Pro 32-bit6.36.49.4 TS1M2
Microsoft Windows 95/986.3
Microsoft Windows 2000 Advanced Server6.3
Microsoft Windows 2000 Datacenter Server6.3
Microsoft Windows 2000 Server6.3
Microsoft Windows 2000 Professional6.3
Microsoft Windows NT Workstation6.3
Microsoft Windows Server 2003 Datacenter Edition6.3
Microsoft Windows Server 2003 Enterprise Edition6.3
Microsoft Windows Server 2003 Standard Edition6.3
Microsoft Windows Server 2003 for x646.3
Microsoft Windows Server 20086.36.49.4 TS1M2
Microsoft Windows Server 2008 R26.36.49.4 TS1M2
Microsoft Windows Server 2008 for x646.36.49.4 TS1M2
Microsoft Windows Server 2012 Datacenter6.36.49.4 TS1M2
Microsoft Windows Server 2012 R2 Datacenter6.36.49.4 TS1M2
Microsoft Windows Server 2012 R2 Std6.36.49.4 TS1M2
Microsoft Windows Server 2012 Std6.36.49.4 TS1M2
Microsoft Windows XP Professional6.3
Windows 7 Enterprise 32 bit6.36.49.4 TS1M2
Windows 7 Enterprise x646.36.49.4 TS1M2
Windows 7 Home Premium 32 bit6.36.49.4 TS1M2
Windows 7 Home Premium x646.36.49.4 TS1M2
Windows 7 Professional 32 bit6.36.49.4 TS1M2
Windows 7 Professional x646.36.49.4 TS1M2
Windows 7 Ultimate 32 bit6.36.49.4 TS1M2
Windows 7 Ultimate x646.36.49.4 TS1M2
Windows Millennium Edition (Me)6.3
Windows Vista6.3
Windows Vista for x646.3
64-bit Enabled AIX6.36.49.4 TS1M2
64-bit Enabled Solaris6.36.49.4 TS1M2
HP-UX IPF6.36.49.4 TS1M2
Linux for x646.36.49.4 TS1M2
Solaris for x646.36.49.4 TS1M2
* 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.