SUPPORT / SAMPLES & SAS NOTES
Problem Note 60703: A Write lock occurs when you publish multiple campaigns to the SAS® Customer Intelligence Common Data Model that resides in the Teradata database
 |  |  |  |  |
A Write lock on row hash values in Treatment tables might occur when you publish multiple campaigns to the Common Data Model, which is held in the Teradata database.
When this situation occurs, the Treatment tables block Read access to these tables. You might also see deadlock errors in the SASCustIntellCore6.x.log file, as shown below:
ERROR: Teradata insert: Transaction ABORTed due to Deadlock. SQL statement was:
USING ("PACKAGE_SK" DECIMAL(15),"PACKAGE_HASH_VAL" VARCHAR (32),"TREATMENT_SK"
DECIMAL(15),"CONTRIBUTING_CELL_PACKAGE_SK" DECIMAL(15),"SEQUENCE_NO"
DECIMAL(6))INSERT INTO CDM."CI_PACKAGE_X_TREATMENT"
USING ("PACKAGE_SK" DECIMAL(15),"PACKAGE_HASH_VAL" VARCHAR (32),"TREATMENT_SK"
DECIMAL(15),"CONTRIBUTING_CELL_PACKAGE_SK" DECIMAL(15),"SEQUENCE_NO"
DECIMAL(6))INSERT INTO CDM."CI_PACKAGE_X_TREATMENT"
To work around this issue, avoid the execution of many campaigns concurrently. Spreading out the executions of the campaigns avoids the numerous concurrent inserts that occur in the Treatment tables, and it should reduce the number of deadlocks that occur.
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 Customer Intelligence Reporting Mid-Tier | Solaris for x64 | 6.3 | 9.4 TS1M1 | ||
| Linux for x64 | 6.3 | 9.4 TS1M1 | ||||
| HP-UX IPF | 6.3 | 9.4 TS1M1 | ||||
| 64-bit Enabled Solaris | 6.3 | 9.4 TS1M1 | ||||
| 64-bit Enabled AIX | 6.3 | 9.4 TS1M1 | ||||
| Microsoft® Windows® for x64 | 6.3 | 9.4 TS1M1 | ||||