SUPPORT / SAMPLES & SAS NOTES
Problem Note 60435: Concurrent exports to a single Teradata table fail with a duplicate, unique prime-key error
 |  |  |  |  |
Concurrent SAS® Customer Intelligence campaign exports that are appended to a single Teradata database table might fail with the following error:
ERROR: Teradata connection: Duplicate unique prime key error in
EXPRTLIB.TABLE_NAME_RS. Correct error and restart as an APPEND process with
option TPT_RESTART=YES. Since no checkpoints were taken, if the previous run
used FIRSTOBS=n, use the same value in the restart
EXPRTLIB.TABLE_NAME_RS. Correct error and restart as an APPEND process with
option TPT_RESTART=YES. Since no checkpoints were taken, if the previous run
used FIRSTOBS=n, use the same value in the restart
This error might occur when the the Append to table options field for the business context is set to MULTISTMT=YES TPT_PACKMAXIMUM=YES and when the export LIBNAME statement is defined similar to the one shown below:
libname explib teradata server="teradata-server" schema=export-schema sql_functions=all
connection=unique read_lock_type=table read_mode_wait=yes read_isolation_level=write
update_lock_type=table update_mode_wait=yes update_isolation_level=access
user=export-user PASSWORD=your-password;
To work around this issue, schedule your campaigns to execute one after the other rather than concurrently.
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 Processes | Microsoft® Windows® for x64 | 6.5 | |||
| 64-bit Enabled AIX | 6.5 | |||||
| 64-bit Enabled Solaris | 6.5 | |||||
| HP-UX IPF | 6.5 | |||||
| Linux for x64 | 6.5 | |||||
| Solaris for x64 | 6.5 | |||||