What's New?

 

Hot Fix Releases for the Week of: January 16, 2012

E9BD61 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 occur when you use a WHERE= option with indexed tables in the SQL procedure	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-040951	Arithemetic performed on DATA and TIME data types is not passed to the underlying DBMS in SAS/ACCESS® 9.1.3 software	E9BD20
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-040492	Incorrect textualization of SQL Implicit Pass-Through queries occurs when you combine multiple inner joins with the UNION operator	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
SN-038519	Specifying both the DBSLICPARM= and the MULTI_DATASRC_OPT= options might generate incorrect results	E9BD26
SN-039304	SQL views of DBMS tables may not return aliased column names	E9BD26
SN-039129	Formatting a newly created, missing numeric variable might result in a "Format not found" error	E9BD32
SN-039125	An SQLPLAN error might occur when you use a new column variable in a correlated subquery	E9BD32
SN-039271	ALERT - Outer join condition may not appear on WHERE clause when performing query against Oracle	E9BD32
SN-039984	An SQL procedure view does not return any rows when it is used in DATA step or a PRINT procedure	E9BD43
SN-041785	Read Access Violation errors occur when creating a long macro variable with the PROC SQL / INTO: macro interface	E9BD43
SN-042030	Oracle PREPARE error issued when SAS table is empty and no keys are in the WHERE clause	E9BD47
SN-044069	Performance might be affected if your query joins multiple tables or views in which variables are being renamed	E9BD61
* 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
Released January 16, 2012 on Tru 64, Linux Released October 4, 2011 on HPUX, Solaris (64-bit), AIX, HPUX for Itanium, Linux for Itanium, Windows, Windows for IPF (64 bit), z/OS (OS/390)
ATTENTION (1): E9BD61 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 E9BD42 and E9BD48. Download E9BD42 Download E9BD42 for SAS with Asian Language Support (DBCS) Download E9BD48 Download E9BD48 for SAS with Asian Language Support (DBCS) ATTENTION (3): OpenVMS Alpha customers should install SAS BASE hot fix E9BD32. Download E9BD32

Top ^

Hot Fix Releases for the Week of: December 19, 2011

E9BD59 for BASE SAS
Issue(s) Addressed:		Introduced:
SN-017514*	Job submissions to grid manager increasingly slow	E9BA05
SN-017233*	Poor performance with large DATA step and many missing values	E9BA07
SN-017667*	ALERT - Segmentation Violation in task [ DATASETS ] using DELETE statement	E9BA13
SN-017653*	-SGIO option generates I/O error message when ODS or procedure output is to an existing SAS data set	E9BA15
SN-017072	Metadata server service might show starting state but never start	E9BA19
SN-010866*	Text Pad cannot store a single character value in column 1	E9BA29
SN-017847*	SUM function and statement give incorrect output on HP Itanium	E9BA38
SN-013525*	ALERT - File>Open and File>Save might cause SAS to lock up with Jaws screen reader in SAS 9.1	E9BA55
SN-018540*	SAS Display Manager keys fail when you select Tools=>Options=>Output while using the JAWS screen reader with SAS® 9.1.3 on the Windows platform	E9BA55
SN-018790*	SAS® fails when running a very large DATA step on AIX	E9BA69
SN-019040*	Double-byte text strings are truncated when using the host WMF device driver	E9BA76
SN-018929*	Font type WingDings might not work on DBCS SAS® 9.1.3 with the GPLOT procedure	E9BA76
SN-019225*	DDE stops working after hotfix E9BA55 is installed	E9BA85
SN-019224*	PROC APPEND fails with SGIO option on Windows operating systems	E9BA85
SN-019345*	Increased LRECL support for SAS® on MS Windows	E9BA95
SN-019608*	SAS® Metadata server fails to start when system restarted	E9BB05
SN-019640*	HTML output is incorrect when ODS output is appended to an HTML file created by a DATA Step	E9BB14
SN-020233*	Increasing timeout value on UNIX may improve performance	E9BB32
SN-020274	Grid sign-on fails to honor the TCPPORTFIRST and the TCPPORTLAST options	E9BB36
SN-020438*	Unix cleanwork utility does not remove UTILLOC directories	E9BB45
SN-019386	SAS/CONNECT may issue "Segmentation Violation In Task [ Program ]"	E9BB58
SN-020817	Using the JOBNAME= option to specify a job name in the GRDSVC_ENABLE call routine	E9BB58
SN-020870*	SIGNON attempts to SAS® Grid Manager might fail	E9BB58
SN-020646*	Moving the cursor off of a selected Radio Box item before releasing the mouse can incorrectly show updated selection	E9BB75
SN-021112*	A SAS/CONNECT® software session might result in orphaned processes on a remote UNIX server	E9BB75
SN-031368*	Poor performance with complex merges on AIX	E9BB95
SN-031098*	ALERT - A SAS® server might become unresponsive on highly loaded systems	E9BB95
SN-031719	Some components from version 6 of SAS/AF® software might cause a read-access violation with repeated use	E9BC09
SN-031795	Dragging the cursor to an unselected item within the Radio Box control can unexpectedly update the internal value for the unselected item	E9BC09
SN-031400	Resetting system time backwards causes negative "real time" value in STIMER output	E9BC09
SN-019028	Truncation errors might occur when using Unicode SAS with UTF-8 encoding to process 8-bit characters	E9BC18
SN-032113	The $EBCDIC format/informat generates incorrect results if ENCODING=UTF8 is set	E9BC18
SN-019330	Problems might occur when you invoke SAS® macros using Microsoft Object Linking and Embedding (OLE) automation submit method	E9BC18
SN-032096	ERROR "SAS Error Event: Error sending status, 1, to SCM. Error 6: The handle is invalid." occurs when stopping the SAS® Metadata Server	E9BC18
SN-032521	ALERT - A Multi-Processing (MP) CONNECT session might not respond in UNIX environments	E9BC18
SN-032547	Data sets written to tape in SAS® 8.2 are not readable in SAS® 9.1.3	E9BC18
SN-032945*	On HP Integrity systems, SAS® 9.1.3 SP4 installation process hangs if memory page size has been set higher than 8Kb	E9BC30
SN-032672*	DDE error "Physical file does not exist, excel|system." occurs after applying hot fix bundle E9BX03 for SAS® 9.1.3 SP4	E9BC30
SN-033403	Segmentation violation and bridge stub errors on AIX	E9BC60
SN-036130	Running large SQL queries in the AIX operating environment can generate results with missing values	E9BC60
SN-033581*	Program with a large number of ELSE statements produces incorrect results on AIX	E9BC60
SN-034651	Using a Japanese or DBCS character in a pathname may cause truncation of file name	E9BC67
SN-035477*	Invalid physical name error when a FILE statement contains certain Shift-JIS characters	E9BC83
SN-034955	The SAS® Metadata Server stops accepting new client connections and returns an error when too many files are open	E9BD12
SN-040822*	Specifying the SAS® system option OPLIST may cause a segmentation violation error in the UNIX environment	E9BD41
SN-041361	Modification datetime stamp is changed on existing version of a SAS® data set when you create a new data set with same name	E9BD44
SN-031894*	The SAS® Metadata Server might appear to hang during a period of high activity	E9BD56
SN-040494*	ALERT - A SAS/SHARE® server fails or does not respond when it is run as a Microsoft Windows service	E9BD59
* 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,   Windows_for_IPF_(64_bit)
ATTENTION (1): To obtain the complete fix for SN-020817 and SN-019386 you must also download and install SAS/CONNECT hot fix E9CT05. The issues described in SN-020817 and SN-019386 will not be fully fixed until both E9BD56 and E9CT05 are applied. ATTENTION (2): To obtain the complete fix for SN-021112 you must also download and install SAS/ACCESS Interface to DB2 hot fix E9D216. The issue described in SN-021112 will not be fully fixed until both E9BD56 and E9D216 are applied. This is not applicable to z/OS sites. Customers running on VMS should download E9BD44. Customers running on Unix and MVS should download E9BD56.

Top ^