| E9BC32 for BASE SAS |
| Issue(s) Addressed: | Introduced: |
| SN-017873 |
ALERT - Extra WHERE clause may get added to query passed to databases |
E9BA31 |
| SN-017888 |
Segmentation Violation error issued when using PROC SQL and SAS/ACCESSwith a LENGTH= option larger than 32 |
E9BA31 |
| SN-018108 |
Segmentation violation when executing multiple queries against a PROCSQL view containing a LIBNAME statement |
E9BA44 |
| SN-018176 |
ALERT - Import of table through Information Map Library Engine deletes physicaltable |
E9BA48 |
| SN-020479 |
Batch jobs might end with a return code of 4 with no warning in the SASlog |
E9BA53 |
| SN-018487 |
Compress() function returns incorrect results when used on PROC SQLINSERT statement after applying SAS 9.1.3 Service Pack 4 |
E9BA53 |
| SN-016074 |
"WARNING: At least one nonessential grouping column reference has beenremoved from a GROUP BY's reference list" |
E9BA53 |
| SN-019170 |
Errors issued when integer references for column is used in a PROC SQLGROUP BY statement |
E9BA83 |
| SN-019372 |
Performance is poor in the SQL procedure when you use the COUNT(Distinctxxxx) function |
E9BB04 |
| SN-019527 |
Specifying the NOIPASSTHRU option in PROC SQL does not disable implicitpassthru |
E9BB04 |
| SN-016547 |
Correlated subqueries using column aliases may not be passed to yourdbms when using SAS/ACCESS LIBNAME statement |
E9BB10 |
| SN-019930 |
Using more than 36 tables in a UNION operation within an SQL proceduregenerates an error message |
E9BB26 |
| SN-020130 |
Aliases columns or aliased tables in the SQL procedure blocks ImplicitPass-Through |
E9BB29 |
| SN-030428 |
Aliased constant values become missing in outer joins and unions |
E9BB29 |
| SN-020126 |
SAS/ACCESS® software now provides full support of the INNER JOIN syntax |
E9BB29 |
| SN-020162 |
Using functions without parameters in WHERE clauses can block ImplicitPass-Through |
E9BB29 |
| SN-020116 |
SAS/ACCESS® software fails to use table aliases correctly when you use in-line SELECT statements |
E9BB29 |
| SN-020123 |
Incorrect SQL text is generated when inner and left joins are used |
E9BB29 |
| SN-020125 |
Using implicit pass-through might cause an incorrect table referenceassignment |
E9BB29 |
| SN-020129 |
An incorrect Implicit Pass-Through query is generated when you use acombination of inner and outer Joins |
E9BB29 |
| SN-020122 |
Performance issues occur because SQL code is not passed to the database |
E9BB29 |
| SN-030390 |
Improvements are now available in relational database optimization via the SQL procedure |
E9BB70 |
| SN-019655 |
Filter behavior inconsistent between SAS® Web Report Studio 3.1 and SAS® Information Map Studio |
E9BB70 |
| SN-020635 |
Incorrect textualization of SQL Implicit Pass-Through queries occurswhen you combine multiple inner joins with one or more outer joins |
E9BB70 |
| SN-032085 |
Incorrect SQL optimization may produce incorrect results |
E9BB76 |
| SN-030942 |
The WHERE clause strips trailing blanks from string literals that are concatenated with DBMS columns of type VARCHAR |
E9BB76 |
| SN-030923 |
Aliased summary functions in Base SAS® software are not passed to databases |
E9BB76 |
| SN-030893 |
Using an ORDER BY clause in the SQL procedure causes performance problems |
E9BB76 |
| SN-031102 |
A segmentation-violation error might occur after you apply Hot Fix E9BA83 and you access Oracle |
E9BB76 |
| SN-031191 |
Support is now available for the PROC SQL CREATE TABLE statement for the SAS® Scalable Performance Data Server® |
E9BB93 |
| SN-031122 |
SQLPLAN internal errors might occur when you select columns from an SQL view |
E9BB93 |
| SN-031121 |
Implicit Pass-Through errors occur when accessing Oracle tables |
E9BB93 |
| SN-031291 |
Errors occur in SAS® Scalable Performance Data Server® for numeric columns that are defined with the MISSING statement when it is used in WHERE processing |
E9BB99 |
| SN-031211 |
Errors occur in the SQL procedure's Implicit Pass-Through facility after you apply hot fixes E9BB72, E9BB76, and E9BB80 |
E9BB99 |
| SN-031249 |
SQLPLAN errors occur when you reference a calculated column on an SQL WHERE clause |
E9BB99 |
| SN-031905 |
Enhancements to the Implicit SQL Pass-Through facility enable more of a query to be passed to a database |
E9BC11 |
| SN-031863 |
ALERT - Using the EQT operator in the SQL procedure incorrectly classifies rows with missing values as a match |
E9BC11 |
| SN-031564 |
Performance problems occur when you use the CASE expression with DBMS tables |
E9BC11 |
| SN-031825 |
After applying hot fixes E9BB98 and E9BB99, column aliases are passed to the SQL GROUP BY clause in place of the corresponding real column names |
E9BC11 |
| SN-032636 |
A Read-access violation might be generated after you apply hot fixes E9BB80, E9BB98, and E9BB99 |
E9BC25 |
| SN-032537 |
ALERT - Incorrect query results might be generated after you apply hot fixes E9BB80, E9BB98, and E9BB99 or you run SAS® 9.2 |
E9BC25 |
| SN-032925 |
An error occurs when you use the IDXNAME= and the WHERE= data set options in an SQL procedure query |
E9BC32 |
| SN-032472 |
Concatenating libraries can result in Read-access violations in the SQL procedure |
E9BC32 |
| SN-032545 |
An SQLPLAN error might occur after you apply hot fixes E9BB98 and E9BB99 |
E9BC32 |
| SN-032406 |
Outer joins that contain a WHERE clause with the STRIP() and PUT() functions cause abnormal endings |
E9BC32 |
| SN-032542 |
An error message incorrectly appears when you use the IDXNAME= and the WHERE= option data set options together in an SQL procedure |
E9BC32 |
| Select an Available Operating System: |
| MAINFRAME: |
z/OS_(OS/390) |
| PC: |
Windows, Windows_for_IPF_(64_bit) |
| VMS: |
OpenVMS_Alpha |
| UNIX: |
HPUX, Solaris_(64-bit), AIX, Tru_64, Linux, HPUX_for_Itanium, Linux_for_Itanium |
ATTENTION (1): E9BC32 for Windows is also available for the following languages:
German, Spanish, French, Italian, Japanese, Polish, Simplified Chinese
ATTENTION (2): Customers running SAS Base SQL must also download and install SAS Base hot fixes E9BC14 and E9BC16.
Download E9BC14
Download E9BC14 for SAS with Asian Language Support (DBCS) Download E9BC16
Download E9BC16 for SAS with Asian Language Support (DBCS) |
| E9BC36 for BASE SAS |
| Issue(s) Addressed: | Introduced: |
| SN-018812 |
SAS Information Map might fail to open in SAS Enterprise Guide |
E9BA74 |
| SN-019360* |
"ERROR: Proc InfoMaps is not available on this operating system." on64-bit HP-UX and the mainframe |
E9BA97 |
| SN-020496 |
SAS Information Map Libname Engine might generate "ERROR: Write AccessViolation in Task" |
E9BB47 |
| SN-020991 |
SAS® Information Maps with more than 1000 data items might fail to open with the SAS Information Map Libname Engine (IMLE) |
E9BB69 |
| SN-031143* |
Information Map Libname Engine is not supported on Solaris x64 |
E9BB69 |
| SN-031142* |
PROC INFOMAPS is not supported on Solaris x64 |
E9BB69 |
| SN-030898 |
Slow processing when using PROC INFOMAPS |
E9BB83 |
| SN-019093 |
Measure captions are limited to 30 characters for OLAP information maps |
E9BB83 |
| SN-030897 |
Error with PROC INFOMAPS when the data source is an OLAP Cube and the password is not stored in the metadata |
E9BB83 |
| SN-032856 |
Denying ReadMetadata on a column does not always prevent denied users from seeing the column |
E9BC36 |
| * Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems. |
| Select an Available Operating System: |
| MAINFRAME: |
z/OS_(OS/390) |
| PC: |
Windows |
| UNIX: |
HPUX, Solaris_(64-bit), AIX, HPUX_for_Itanium, Solaris_for_x64 |
| E9TE06 for SAS/ACCESS INTERFACE TO TERADATA |
| Issue(s) Addressed: | Introduced: |
| SN-018170 |
Teradata FASTLOAD performance problems in SAS 9 |
E9TE01 |
| SN-018429* |
Running the Teradata MultiLoad utilty is now supported on z/OS |
E9TE02 |
| SN-019941 |
Running multiple, concurrent processes causes an error in the FastLoad utility when you use it with the SAS/ACCESS® Interface to Teradata |
E9TE03 |
| SN-019939 |
Using MULTILOAD=YES without CREATE/DROP table rights in the SAS/ACCESS® Interface to Teradata can generate an error |
E9TE03 |
| SN-020199 |
The same query produces different results when submitted using the Pass-Through Facility in SAS/ACCESS® Interface to Teradata and using Teradata BTEQ |
E9TE04 |
| SN-020515 |
An error occurs when you attempt to access a Teradata TTU 8.2 library via SAS/ACCESS® Interface to Teradata 9.1.3 Service Pack 4 |
E9TE04 |
| SN-031370 |
LDAP authentication is not supported in SAS/ACCESS® Interface to Teradata |
E9TE05 |
| SN-032796 |
An incorrect error message is sometimes generated when using MODE=Teradata |
E9TE06 |
| * Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems. |
| Select an Available Operating System: |
| MAINFRAME: |
z/OS_(OS/390) |
| PC: |
Windows |
| UNIX: |
HPUX, Solaris_(64-bit), AIX, Linux, HPUX_for_Itanium |
