SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 44213: Publishing a campaign might cause the errors "Transact error: Unable to commit.." or "Cannot Insert Null.."

DetailsHotfixAboutRate It

SAS® Marketing Automation might fail to publish a campaign. When this problem occurs, SAS Marketing Automation writes an error in the SASMarketingAutomationCoreversion.log file similar to one of the two errors below:

ERROR: Transact error: Unable to commit: The statement has been terminated.: The INSERT statement
conflicted with the FOREIGN KEY constraint "CELL_PKG_FK3". The conflict occurred in database.
...immediate cause: Error in the stored process or a called macro. com.sas.analytics.crm.error.client.ApplicationException: 
Macro[MACPTPUB]. SYSDBRC=[-1400] and 
SYSDBMSG=[ORACLE: ORA-01400: cannot insert NULL in "CDM_DK"."CI_CELL_PACKAGE_TREATMENT_CNT"."TREATMENT_SK"

To work around this issue, first ensure that the option Automatically publish campaigns on subsequent saves is NOT selected. This option is under Reporting Options in the SAS® Management Console Customer Intelligence plug-in when you select Business Context ► Properties ► Options.

Next, manually publish each campaign using SAS® Customer Intelligence Studio in any of the following circumstances:

  • before the initial execution of the campaign
  • before any subsequent executions if changes have been made to an already published campaign
  • after updating counts on a communication node

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 Marketing AutomationMicrosoft® Windows® for 64-Bit Itanium-based Systems5.3_M36.19.3 TS1M2
Microsoft Windows Server 2003 Datacenter 64-bit Edition5.3_M36.19.3 TS1M2
Microsoft Windows Server 2003 Enterprise 64-bit Edition5.3_M36.19.3 TS1M2
Microsoft Windows XP 64-bit Edition5.3_M36.19.3 TS1M2
Microsoft Windows 95/985.3_M3
Microsoft Windows 2000 Advanced Server5.3_M3
Microsoft Windows 2000 Datacenter Server5.3_M3
Microsoft Windows 2000 Server5.3_M3
Microsoft Windows 2000 Professional5.3_M3
Microsoft Windows NT Workstation5.3_M3
Microsoft Windows Server 2003 Datacenter Edition5.3_M36.19.3 TS1M2
Microsoft Windows Server 2003 Enterprise Edition5.3_M36.19.3 TS1M2
Microsoft Windows Server 2003 Standard Edition5.3_M36.19.3 TS1M2
Microsoft Windows Server 2003 for x645.3_M36.19.3 TS1M2
Microsoft Windows Server 20085.3_M36.19.3 TS1M2
Microsoft Windows Server 2008 for x645.3_M36.19.3 TS1M2
Microsoft Windows XP Professional5.3_M36.19.3 TS1M2
Windows 7 Enterprise 32 bit5.3_M36.19.3 TS1M2
Windows 7 Enterprise x645.3_M36.19.3 TS1M2
Windows 7 Home Premium 32 bit5.3_M36.19.3 TS1M2
Windows 7 Home Premium x645.3_M36.19.3 TS1M2
Windows 7 Professional 32 bit5.3_M36.19.3 TS1M2
Windows 7 Professional x645.3_M36.19.3 TS1M2
Windows 7 Ultimate 32 bit5.3_M36.19.3 TS1M2
Windows 7 Ultimate x645.3_M36.19.3 TS1M2
Windows Millennium Edition (Me)5.3_M3
Windows Vista5.3_M36.19.3 TS1M2
Windows Vista for x645.3_M36.19.3 TS1M2
64-bit Enabled AIX5.3_M36.19.3 TS1M2
64-bit Enabled HP-UX5.3_M36.19.3 TS1M2
64-bit Enabled Solaris5.3_M36.19.3 TS1M2
HP-UX IPF5.3_M36.19.3 TS1M2
Linux on Itanium5.3_M36.19.3 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.