Problem Note 40017: Partitioned primary indexes are incorrectly omitted when searching for primary indexes on Teradata tables
In certain circumstances the Table Loader transformation must identify primary indexes on target tables. The code that is generated to perform this check incorrectly omits partitioned primary indexes when the target table resides in a Teradata library. Because primary indexes of this type are not properly identified, subsequently executing code to remove all non-primary indexes fails with the following error:
ERROR: Teradata execute: The user cannot create or drop a PRIMARY index.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| SAS System | SAS Data Integration Studio | Microsoft® Windows® for x64 | 4.21 | 4.3 | 9.2 TS2M0 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Datacenter Edition | 4.21 | 4.3 | 9.2 TS2M0 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Enterprise Edition | 4.21 | 4.3 | 9.2 TS2M0 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Standard Edition | 4.21 | 4.3 | 9.2 TS2M0 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 for x64 | 4.21 | 4.3 | 9.2 TS2M0 | 9.3 TS1M0 |
| Microsoft Windows Server 2008 for x64 | 4.21 | 4.3 | 9.2 TS2M0 | 9.3 TS1M0 |
| Microsoft Windows XP Professional | 4.21 | 4.3 | 9.2 TS2M0 | 9.3 TS1M0 |
| Windows Vista | 4.21 | 4.3 | 9.2 TS2M0 | 9.3 TS1M0 |
| Windows Vista for x64 | 4.21 | 4.3 | 9.2 TS2M0 | 9.3 TS1M0 |
*
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.
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2010-06-23 12:12:10 |
| Date Created: | 2010-06-16 13:08:26 |
