Usage Note 38412: Data that is returned from a Teradata query might not be sorted in ascending order
Data that is returned from a Teradata query might not be sorted in ascending order. The incorrect sort order is caused by a limitation of Teradata. When this happens, an error message similar to the following is generated:
ERROR: Data set LIB.test is not sorted in ascending sequence. The
current BY group has group =
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
. . .more data lines. . .
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbharry and
the next BY group has group =
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
. . .more data lines. . .
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbdick.
Teradata sorts only the first 4096 bytes of data. Therefore, if the field upon which the sort key is based is greater than that, the data might not be returned in sorted order.
The only circumvention is to use data that is not more than 4096 bytes.
Operating System and Release Information
| SAS System | SAS/ACCESS Interface to Teradata | z/OS | 9.2 TS2M0 | |
| Microsoft® Windows® for x64 | 9.2 TS2M0 | |
| Microsoft Windows Server 2003 Datacenter Edition | 9.2 TS2M0 | |
| Microsoft Windows Server 2003 Enterprise Edition | 9.2 TS2M0 | |
| Microsoft Windows Server 2003 Standard Edition | 9.2 TS2M0 | |
| Microsoft Windows XP Professional | 9.2 TS2M0 | |
| Windows Vista | 9.2 TS2M0 | |
| 64-bit Enabled AIX | 9.2 TS2M0 | |
| 64-bit Enabled HP-UX | 9.2 TS2M0 | |
| 64-bit Enabled Solaris | 9.2 TS2M0 | |
| HP-UX IPF | 9.2 TS2M0 | |
| Linux | 9.2 TS2M0 | |
| Linux for x64 | 9.2 TS2M0 | |
| Solaris for x64 | 9.2 TS2M0 | |
*
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: | Usage Note |
| Priority: | |
| Topic: | Data Management ==> Data Sources ==> External Databases ==> Teradata
|
| Date Modified: | 2010-06-15 09:51:05 |
| Date Created: | 2010-01-14 15:42:00 |
