Problem Note 52753: The UPCASE function used in PROC SQL UPDATE might not work properly if you are using SAS/ACCESS® Interface to OLE DB
When you use a PROC SQL UPDATE statement on a database management table accessed via the OLEDB LIBNAME engine, rows that should be updated might not be updated. This issue might occur when your WHERE clause includes a function that does not get passed to the database. The UPCASE function is a good example.
libname test oledb init_string="Provider=SQLOLEDB.1;Password=db-password;User ID=db-user;Data Source=xxx";
proc sql;
update test.class
set age=15
where update(name)='ALFRED';
quit;
Instead of the database processing the WHERE clause, SAS does the processing. The data read in from the database is not transcoded correctly, resulting in matches not being found. As a result, the data is not updated as it should be.
A potential workaround for this issue is to use the LIBNAME option SQL_FUNCTIONS=ALL. This workaround results in additional SAS functions being passed down to the database.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS/ACCESS Interface to OLE DB | Microsoft® Windows® for x64 | 9.3_M2 | 9.4_M2 | 9.3 TS1M2 | 9.4 TS1M2 |
Microsoft Windows 8 Enterprise 32-bit | 9.3_M2 | 9.4_M2 | 9.3 TS1M2 | 9.4 TS1M2 |
Microsoft Windows 8 Enterprise x64 | 9.3_M2 | 9.4_M2 | 9.3 TS1M2 | 9.4 TS1M2 |
Microsoft Windows 8 Pro 32-bit | 9.3_M2 | 9.4_M2 | 9.3 TS1M2 | 9.4 TS1M2 |
Microsoft Windows 8 Pro x64 | 9.3_M2 | 9.4_M2 | 9.3 TS1M2 | 9.4 TS1M2 |
Microsoft Windows 8.1 Enterprise 32-bit | 9.3_M2 | 9.4_M2 | 9.3 TS1M2 | 9.4 TS1M2 |
Microsoft Windows 8.1 Enterprise x64 | 9.3_M2 | 9.4_M2 | 9.3 TS1M2 | 9.4 TS1M2 |
Microsoft Windows 8.1 Pro | 9.3_M2 | 9.4_M2 | 9.3 TS1M2 | 9.4 TS1M2 |
Microsoft Windows 8.1 Pro 32-bit | 9.3_M2 | 9.4_M2 | 9.3 TS1M2 | 9.4 TS1M2 |
Microsoft Windows Server 2003 Datacenter Edition | 9.3_M2 | | 9.3 TS1M2 | |
Microsoft Windows Server 2003 Enterprise Edition | 9.3_M2 | | 9.3 TS1M2 | |
Microsoft Windows Server 2003 Standard Edition | 9.3_M2 | | 9.3 TS1M2 | |
Microsoft Windows Server 2003 for x64 | 9.3_M2 | | 9.3 TS1M2 | |
Microsoft Windows Server 2008 | 9.3_M2 | 9.4_M2 | 9.3 TS1M2 | 9.4 TS1M2 |
Microsoft Windows Server 2008 R2 | 9.3_M2 | 9.4_M2 | 9.3 TS1M2 | 9.4 TS1M2 |
Microsoft Windows Server 2008 for x64 | 9.3_M2 | 9.4_M2 | 9.3 TS1M2 | 9.4 TS1M2 |
Microsoft Windows Server 2012 Datacenter | 9.3_M2 | 9.4_M2 | 9.3 TS1M2 | 9.4 TS1M2 |
Microsoft Windows Server 2012 R2 Datacenter | 9.3_M2 | 9.4_M2 | 9.3 TS1M2 | 9.4 TS1M2 |
Microsoft Windows Server 2012 R2 Std | 9.3_M2 | 9.4_M2 | 9.3 TS1M2 | 9.4 TS1M2 |
Microsoft Windows Server 2012 Std | 9.3_M2 | 9.4_M2 | 9.3 TS1M2 | 9.4 TS1M2 |
Microsoft Windows XP Professional | 9.3_M2 | | 9.3 TS1M2 | |
Windows 7 Enterprise 32 bit | 9.3_M2 | 9.4_M2 | 9.3 TS1M2 | 9.4 TS1M2 |
Windows 7 Enterprise x64 | 9.3_M2 | 9.4_M2 | 9.3 TS1M2 | 9.4 TS1M2 |
Windows 7 Home Premium 32 bit | 9.3_M2 | 9.4_M2 | 9.3 TS1M2 | 9.4 TS1M2 |
Windows 7 Home Premium x64 | 9.3_M2 | 9.4_M2 | 9.3 TS1M2 | 9.4 TS1M2 |
Windows 7 Professional 32 bit | 9.3_M2 | 9.4_M2 | 9.3 TS1M2 | 9.4 TS1M2 |
Windows 7 Professional x64 | 9.3_M2 | 9.4_M2 | 9.3 TS1M2 | 9.4 TS1M2 |
Windows 7 Ultimate 32 bit | 9.3_M2 | 9.4_M2 | 9.3 TS1M2 | 9.4 TS1M2 |
Windows 7 Ultimate x64 | 9.3_M2 | 9.4_M2 | 9.3 TS1M2 | 9.4 TS1M2 |
Windows Vista | 9.3_M2 | | 9.3 TS1M2 | |
Windows Vista for x64 | 9.3_M2 | | 9.3 TS1M2 | |
*
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: | 2014-05-01 15:37:57 |
Date Created: | 2014-04-14 11:19:01 |