Problem Note 13519: Incorrect results may occur when processing two different tables using
the same connection
The problem can occur when there is an overlap in reading the rows from
two different tables by PROC SQL. If PROC SQL opens one table and reads
a row from the table and then opens another table to read it's rows, the
open for these tables are both on the same connection to DB2. The
problem is a result in the fact that the DB2 engine issues a COMMIT
during the open processing. The effect this has is that when the second
open is done, the commit is triggering the first tables' cursor to be
marked as invalid. So when SAS goes back to retrieve another row from
the first table the result set is being regenerated. Since the result
set is regenerated, the results might not be returned in the same order
as it was done previously. The rows that SAS thinks it has already
processed are skipped so any rows that ended up at the top that were
previously at the bottom are skipped and any rows at the top that were
previously processed and now are at the bottom of the result set are
processed once again.
A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:
http://www.sas.com/techsup/download/hotfix/e9_sbcs_prod_list.html#013519
For customers running SAS with Asian Language Support (DBCS), this
fix should be downloaded from:
http://www.sas.com/techsup/download/hotfix/e9_dbcs_prod_list.html#013519
Operating System and Release Information
| SAS System | SAS/ACCESS Interface to DB2 | Microsoft Windows NT Workstation | 8.2 TS2M0 | 9.1 TS1M3 SP1 |
| Microsoft Windows XP Professional | 8.2 TS2M0 | 9.1 TS1M3 SP1 |
| Microsoft Windows 95/98 | 8.2 TS2M0 | |
| Windows Millennium Edition (Me) | 8.2 TS2M0 | |
| Microsoft Windows Server 2003 Enterprise Edition | 8.2 TS2M0 | 9.1 TS1M3 SP1 |
| Microsoft Windows Server 2003 Standard Edition | 8.2 TS2M0 | 9.1 TS1M3 SP1 |
| Microsoft Windows 2000 Server | 8.2 TS2M0 | 9.1 TS1M3 SP1 |
| Microsoft Windows Server 2003 Datacenter Edition | 8.2 TS2M0 | 9.1 TS1M3 SP1 |
| Microsoft Windows 2000 Professional | 8.2 TS2M0 | 9.1 TS1M3 SP1 |
| Microsoft Windows 2000 Datacenter Server | 8.2 TS2M0 | 9.1 TS1M3 SP1 |
| Microsoft Windows 2000 Advanced Server | 8.2 TS2M0 | 9.1 TS1M3 SP1 |
| Solaris | 8.2 TS2M0 | 9.1 TS1M3 SP1 |
| OpenVMS VAX | 8.2 TS2M0 | |
| 64-bit Enabled Solaris | 8.2 TS2M0 | 9.1 TS1M3 SP1 |
| OS/2 | 8.2 TS2M0 | |
| IRIX | 8.2 TS2M0 | |
| 64-bit Enabled HP-UX | 8.2 TS2M0 | 9.1 TS1M3 SP1 |
| HP-UX | 8.2 TS2M0 | 9.1 TS1M3 SP1 |
| ABI+ for Intel Architecture | 8.2 TS2M0 | |
| Linux | 8.2 TS2M0 | 9.1 TS1M3 SP1 |
| CMS | 8.2 TS2M0 | |
| z/OS | 8.2 TS2M0 | 9.1 TS1M3 SP1 |
| 64-bit Enabled AIX | 8.2 TS2M0 | 9.1 TS1M3 SP1 |
| OpenVMS Alpha | 8.2 TS2M0 | 9.1 TS1M3 SP1 |
| Tru64 UNIX | 8.2 TS2M0 | 9.1 TS1M3 SP1 |
| AIX | 8.2 TS2M0 | 9.1 TS1M3 SP1 |
*
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: | alert |
| Topic: | SAS Reference ==> LIBNAME Engines Data Management ==> Data Sources ==> External Databases ==> DB2
|
| Date Modified: | 2004-12-20 13:33:55 |
| Date Created: | 2004-10-01 14:49:27 |