 |
||
|
||
|
||
|
Return to 9.1.3 DBCS Hot Fix Home | |
|
||
What's New?
| Hot Fix Releases for the Week of: February 8, 2010 |
| E9NZ02 for SAS/ACCESS INTERFACE TO NETEZZA | ||
| Issue(s) Addressed: | Introduced: | |
| SN-033362* | uploading the MATables in Netezza fails to complete | E9NZ01 |
| SN-030556 | The BULKUNLOAD= option is ONLY used as a data set option in SAS/ACCESS® Interface to Netezza | E9NZ01 |
| SN-030464 | Japanese characters do not display successfully in SAS® Enterprise Guide® when you access Netezza with SAS/ACCESS® Interface to ODBC or SAS/ACCESS® Interface to Netezza | E9NZ01 |
| SN-035799 | An error occurs when you use the Netezza engine in a LIBNAME statement to access Netezza release 4.6 | E9NZ02 |
| * Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems. | ||
| Select an Available Operating System: | ||
| PC: | Windows | |
| UNIX: | HPUX, Solaris_(64-bit), AIX, Linux, HPUX_for_Itanium | |
|
| Top ^ |
| Hot Fix Releases for the Week of: February 1, 2010 |
| E9BD20 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/ACCESS® with a LENGTH= option larger than 32 | E9BA31 |
| SN-018108 | Segmentation violation when executing multiple queries against a PROC SQL view containing a LIBNAME statement | E9BA44 |
| SN-018176 | ALERT - Import of table through Information Map Library Engine deletes physical table | E9BA48 |
| SN-020479 | Batch jobs might end with a return code of 4 with no warning in the SAS® log | E9BA53 |
| SN-018487 | Compress() function returns incorrect results when used on PROC SQL INSERT statement after applying SAS® 9.1.3 Service Pack 4 | E9BA53 |
| SN-016074 | "WARNING: At least one nonessential grouping column reference has been removed from a GROUP BY's reference list" | E9BA53 |
| SN-019170 | Errors issued when integer references for column is used in a PROC SQL GROUP BY statement | E9BA83 |
| SN-019372 | Performance is poor in the SQL procedure when you use the COUNT(Distinct xxxx) function | E9BB04 |
| SN-019527 | Specifying the NOIPASSTHRU option in PROC SQL does not disable implicit passthru | E9BB04 |
| SN-016547 | Correlated subqueries using column aliases may not be passed to your dbms when using SAS/ACCESS LIBNAME statement | E9BB10 |
| SN-019930 | Using more than 36 tables in a UNION operation within an SQL procedure generates an error message | E9BB26 |
| SN-020130 | Aliases columns or aliased tables in the SQL procedure blocks Implicit Pass-Through | E9BB29 |
| SN-030428 | Aliased constant values become missing in outer joins and unions | E9BB29 |
| SN-020162 | Using functions without parameters in WHERE clauses can block Implicit Pass-Through | E9BB29 |
| SN-020126 | SAS/ACCESS® software now provides full support of the INNER JOIN syntax | 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 reference assignment | E9BB29 |
| SN-020129 | An incorrect Implicit Pass-Through query is generated when you use a combination 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 occurs when 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-033763 | Using the CALCULATED keyword in a WHERE clause in a PROC SQL inner join generates a cartesian product | E9BC25 |
| SN-033649 | Calculations that involve DBMS datetime values can return incorrect results | E9BC25 |
| SN-033073 | Using the CALCULATED keyword in a WHERE clause generates a Carteisan product | E9BC25 |
| 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-035779 | The LENGTH= column modifier is handled incorrectly when you use PROC SQL to create character columns in SAS® Scalable Performance Data Server® tables | E9BC32 |
| SN-034012 | Column aliases are not passed correctly to GROUP BY or ORDER BY clauses in the SAS® Scalable Performance Data Server® | 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 |
| SN-011210 | Incorrect results from PROC SQL using WHERE= option with indexed tables | E9BC46 |
| SN-034564 | The COUNT() or N() functions return incorrect results when used in a query containing a WHERE clause or a WHERE= data set option | E9BC46 |
| SN-035011 | A Read-access violation occurs in the SQL procedure when the WHERE= data set option is placed in an ORDER BY clause | E9BC46 |
| SN-033094 | ALERT - Incorrect results might be generated when you use the LIBNAME statement to join multiple Oracle tables | E9BC46 |
| SN-033648 | ALERT - The implicit pass-through facility does not correctly switch argument order for the DB2 LOCATE() function when you pass the INDEX() function to DB2 | E9BC62 |
| SN-034993 | An error occurs when you run an SQL query with the ORACLE LIBNAME engine | E9BC62 |
| SN-034975 | Segmentation violations might occur after you apply Hot Fix E9BC46 in queries that reference DBMS tables | E9BC62 |
| SN-034391 | An SQLPLAN error might occur when you use a calculated field to subset a table | E9BC62 |
| SN-036280 | ALERT - The SQL procedure generates incorrect results when you copy a SAS® data set from one platform to another platform | E9BC94 |
| SN-033084 | An SQLPLAN internal error might occur when reference a variable from an in-line view that created the variable from a constant | E9BC94 |
| SN-034678 | An SQLPLAN error occurs when you submit a query with a CALCULATED column reference in a CASE expression that contains a GROUP BY clause | E9BC94 |
| SN-036177 | Incorrect results might occur when you run a PROC SQL join with an additional WHERE clause against Teradata tables | E9BC94 |
| SN-036202 | SQLPLAN internal errors might occur when you reference calculated columns in an SQL procedure | E9BC94 |
| SN-036748 | The MULTI_DATASRC_OPT= option is ignored when multiple WHERE clause predicates are used in an SQL join operation | E9BD08 |
| SN-034153 | Option DBIDIRECTEXEC prevents SAS® Enterprise Guide from opening tables created by PROC SQL | E9BD13 |
| SN-034234 | Incorrect results might occur if you use the LIBNAME statement option IP=YES with an SQL procedure that contains data calculations in a WHERE clause | E9BD13 |
| SN-037611* | Incorrect results are possible when you use the INDEX function without a comparison in the z/OS environment | E9BD13 |
| SN-038458 | SQLPLAN internal errors might occur when you reference a view in a query that has variables that are defined with the the LENGTH= column modifier | E9BD20 |
| SN-037846* | A segmentation violation occurs in the SAS® 9.1.3 SQL procedure after you apply hot fixes E9BD08, E9BD09, and E9BD10 in the AIX operating environment | E9BD20 |
| * 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, Windows_for_IPF_(64_bit) | |
| UNIX: | HPUX, Solaris_(64-bit), AIX, Tru_64, Linux, HPUX_for_Itanium, Linux_for_Itanium | |
| ATTENTION (1): E9BD20 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 E9BD14 and E9BD15. Download E9BD14 Download E9BD14 for SAS with Asian Language Support (DBCS) Download E9BD15 Download E9BD15 for SAS with Asian Language Support (DBCS) |
||
|
| Top ^ |
You are downloading software code ("Code") which will become part of a product ("Software") you currently have licensed from SAS Institute Inc. or one of its subsidiaries ("the Institute"). this Code is designed to either correct an error in the Software or to add functionality to the Software. The code is governed by the same agreement which governs the Software. If you do not have an existing agreement with the Institute governing the Software, you may not download the Code.
SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. ® indicates USA registration. Other brand and product names are registered tradema rks or trademarks of their respective companies.