SUPPORT / SAMPLES & SAS NOTES
Problem Note 39183: Data corruption occurs when you use the SELECT DISTINCT statement in the SQL procedure to select distinct rows from a SAS table
 |  |  |  |  |
When you use the SELECT DISTINCT statement in PROC SQL to select distinct (non-duplicate) rows from a SAS table, the data becomes corrupted. This problem happens in tables that have numeric columns of varying lengths.
The SELECT DISTINCT statement uses a threaded sort routine that expects all numeric items to have a length of 8 bytes. As a result, data corruption occurs when columns of varying lengths are present.
To avoid this problem, use the NOTHREADS option.
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 | SAS Release | |
| Reported | Fixed* | |||
| SAS System | Base SAS | z/OS | 9.2 TS1M0 | 9.2 TS2M3 |
| Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.2 TS1M0 | 9.2 TS2M3 | ||
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.2 TS1M0 | 9.2 TS2M3 | ||
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.2 TS1M0 | 9.2 TS2M3 | ||
| Microsoft Windows XP 64-bit Edition | 9.2 TS1M0 | 9.2 TS2M3 | ||
| Microsoft® Windows® for x64 | 9.2 TS1M0 | 9.2 TS2M3 | ||
| Microsoft Windows Server 2003 Datacenter Edition | 9.2 TS1M0 | 9.2 TS2M3 | ||
| Microsoft Windows Server 2003 Enterprise Edition | 9.2 TS1M0 | 9.2 TS2M3 | ||
| Microsoft Windows Server 2003 Standard Edition | 9.2 TS1M0 | 9.2 TS2M3 | ||
| Microsoft Windows XP Professional | 9.2 TS1M0 | 9.2 TS2M3 | ||
| Windows Vista | 9.2 TS1M0 | 9.2 TS2M3 | ||
| 64-bit Enabled AIX | 9.2 TS1M0 | 9.2 TS2M3 | ||
| 64-bit Enabled HP-UX | 9.2 TS1M0 | 9.2 TS2M3 | ||
| 64-bit Enabled Solaris | 9.2 TS1M0 | 9.2 TS2M3 | ||
| HP-UX IPF | 9.2 TS1M0 | 9.2 TS2M3 | ||
| Linux | 9.2 TS1M0 | 9.2 TS2M3 | ||
| Linux for x64 | 9.2 TS1M0 | 9.2 TS2M3 | ||
| OpenVMS on HP Integrity | 9.2 TS1M0 | 9.2 TS2M3 | ||
| Solaris for x64 | 9.2 TS1M0 | 9.2 TS2M3 | ||