Problem Note 44180: "ERROR: Read Access Violation In Task [SQL]" might occur when using the META engine on a LIBNAME statement
In an interactive SAS®
session, PROC SQL might fail with the following Read Access Violation error:
ERROR: Read Access Violation In Task [ SQL ]
Exception occurred at (0A0B6C0B)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
0A0B6C0B 0B32F414 sasiomet:\vzml.c\vzml 62 +(0x19)
0A0B2DE7 0B32FA94 sasiomet:\metpss.c\coninfo 1210 +(0x33)
0B47D550 0B32FCAC sassqlp:\sqlpfip.c\sqlpsel 1287 +(0x1D)
0B46D233 0B32FD74 sassqlp:\sqlplan.c\sqlplan 339 +(0x10)
0B496710 0B32FE24 sassqlp:\sqlprep.c\sqlprep 263 +(0x10)
0B36A94F 0B32FEA4 sassqx:\sql.c\sqlloop 801 +(0xF)
0B3699BD 0B32FF0C sassqx:\sql.c\sqlloop 146 +(0x10)
0B2A14FB 0B32FF4C sassql:\sqlmain.c\sassql 131 +(0xF)
0340782D 0B32FF74 sashost:\vvtentr.c\vvtentr 196 +(0x1C)
0340F144 0B32FF88 sashost:htthread+0x38
76843677 0B32FF94 kernel32:BaseThreadInitThunk+0x12
77269D72 0B32FFD4 ntdll:RtlInitializeExceptionChain+0x63
77269D45 0B32FFEC ntdll:RtlInitializeExceptionChain+0x36
The problem occurs if you use the META engine on a LIBNAME statement that references a SAS
®
Scalable Performance Data Server
®
library.
An example of code that demonstrates the problem can
be found in the
Full Code tab of this Note.
Select the Hot Fix tab in this Note to access the hot fix for this issue.
Operating System and Release Information
SAS System | Base SAS | Microsoft Windows Server 2008 for x64 | 9.21_M3 | 9.21_M3 | 9.2 TS2M3 | 9.2 TS2M3 |
Microsoft Windows Server 2003 for x64 | 9.21_M3 | 9.21_M3 | 9.2 TS2M3 | 9.2 TS2M3 |
Microsoft Windows Server 2003 Standard Edition | 9.21_M3 | 9.21_M3 | 9.2 TS2M3 | 9.2 TS2M3 |
Microsoft Windows Server 2003 Enterprise Edition | 9.21_M3 | 9.21_M3 | 9.2 TS2M3 | 9.2 TS2M3 |
Microsoft Windows Server 2003 Datacenter Edition | 9.21_M3 | 9.21_M3 | 9.2 TS2M3 | 9.2 TS2M3 |
Microsoft® Windows® for x64 | 9.21_M3 | 9.21_M3 | 9.2 TS2M3 | 9.2 TS2M3 |
Microsoft Windows XP 64-bit Edition | 9.21_M3 | 9.21_M3 | 9.2 TS2M3 | 9.2 TS2M3 |
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.21_M3 | 9.21_M3 | 9.2 TS2M3 | 9.2 TS2M3 |
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.21_M3 | 9.21_M3 | 9.2 TS2M3 | 9.2 TS2M3 |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.21_M3 | 9.21_M3 | 9.2 TS2M3 | 9.2 TS2M3 |
Microsoft Windows XP Professional | 9.21_M3 | 9.21_M3 | 9.2 TS2M3 | 9.2 TS2M3 |
64-bit Enabled AIX | 9.21_M3 | 9.21_M3 | 9.2 TS2M3 | 9.2 TS2M3 |
64-bit Enabled HP-UX | 9.21_M3 | 9.21_M3 | 9.2 TS2M3 | 9.2 TS2M3 |
64-bit Enabled Solaris | 9.21_M3 | 9.21_M3 | 9.2 TS2M3 | 9.2 TS2M3 |
HP-UX IPF | 9.21_M3 | 9.21_M3 | 9.2 TS2M3 | 9.2 TS2M3 |
Linux for x64 | 9.21_M3 | 9.21_M3 | 9.2 TS2M3 | 9.2 TS2M3 |
*
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.
This code demonstrates the problem described in this Note:
options metapass=""
metaport=8561
metaprotocol=bridge
metarepository="Foundation"
metaserver="hostname"
metauser="sasdemo";
libname test META library="SPD Library";
/* Table MYTABLE, in SPD Library, is registered in metadata repository */
proc sql;
create table test as
select distinct var from test.mytable;
quit;
A hot fix is available for this problem.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2011-09-06 18:26:30 |
Date Created: | 2011-09-01 04:26:47 |