| R19047 for 64-bit Enabled Solaris |
| Base SAS 9.4_M2 |
| Issue(s) Addressed: | Introduced: |
| 54321 | Enabling the DBIDIRECTEXEC LIBNAME option with the SAS/ACCESS® Interface to Impala |
R19008 |
| 56478 | An error occurs when you use the CAST=YES LIBNAME option with an ORDER BY clause or a SELECT DISTINCT clause in SAS/ACCESS® Interface to Teradata |
R19047 |
NOTE: If you install this hot fix, you must also install hot fix R19059 for Base SAS 9.4M2.
NOTE: If you install this hot fix and have SAS/ACCESS Interface to Impala 9.41 installed, you must also install hot fix R80002 for SAS/ACCESS Interface to Impala.
NOTE: If you install this hot fix and have SAS/ACCESS Interface to Hadoop 9.4_M2 installed, you must also install hot fix S64002 for SAS/ACCESS Interface to Hadoop.
NOTE: If you install this hot fix and have SAS/ACCESS Interface to Teradata 9.4_M2 installed, you must also install hot fix W07002 for SAS/ACCESS Interface to Teradata.
|
|
| R19059 for 64-bit Enabled Solaris |
| Base SAS 9.4_M2 |
| Issue(s) Addressed: | Introduced: |
| 54321 | Enabling the DBIDIRECTEXEC LIBNAME option with the SAS/ACCESS® Interface to Impala |
R19007 |
| 54127 | An ambiguous reference error might occur when you join SAS® Scalable Performance Data Server tables using implicit pass-through |
R19021 |
| 54658 | When you submit a query with a WHERE clause, you might get unexpected results |
R19021 |
| 54708 | ALERT - Incorrect results might occur when you use the SQL procedure with a DBMS table |
R19021 |
| 54915 | An abend might occur when you are accessing a SAS® Scalable Performance Data Server table on a Linux x64 system |
R19021 |
| 56978 | A Read access violation error might occur when you are running an SQL procedure query |
R19021 |
| 56256 | Querying a relational DBMS table using the IN clause operator might return unexpected results |
R19034 |
| 56478 | An error occurs when you use the CAST=YES LIBNAME option with an ORDER BY clause or a SELECT DISTINCT clause in SAS/ACCESS® Interface to Teradata |
R19045 |
| 50790 | An SQLPLAN error might occur when you query a database management system (DBMS) table and the query includes a LENGTH= modifier |
R19051 |
| 50801 | Implicit pass-through processing might be disabled, resulting in performance issues |
R19051 |
| 56977 | An incorrect query might be passed to a database when a CASE expression is used in a WHERE clause |
R19051 |
| 56979 | A segmentation violation or Read access violation might occur when you are accessing a DBMS table via the SQL procedure |
R19051 |
| 56981 | A simple join might not be not passed to the database, resulting in poor performance |
R19051 |
| 57014 | Using a PUT function with SAS/ACCESS® Interface to ODBC might cause a segmentation violation in Base SAS® |
R19051 |
| 57043 | Macro variables SYSRC, SYSERR, and SQLRC are not being set when "Error on server LIBNAME socket" occurs on the SAS® Scalable Performance Data Server |
R19056 |
| 57936 | ALERT - When used with a single argument, the COALESCE() function is not passed down to the relational database management system (RDBMS) |
R19056 |
| 57042 | An ORDER BY clause in a PROC SQL statement is ignored in rare cases |
R19059 |
NOTE: This hot fix is available for PC and UNIX platforms. Customers running on z/OS must install hot fix R19056 instead.
NOTE: If you install this hot fix, you must also install hot fix R19047 for Base SAS 9.4M2.
NOTE: If you install this hot fix and have SAS/ACCESS Interface to Impala 9.41 installed, you must also install hot fix R80002 for SAS/ACCESS Interface to Impala.
NOTE: If you install this hot fix and have SAS/ACCESS Interface to Teradata 9.4_M2 installed, you must also install hot fix W07002. |
|
| R19061 for 64-bit Enabled Solaris |
| Base SAS 9.4_M2 |
| Issue(s) Addressed: | Introduced: |
| 54246 | The error "sas.exe has stopped working" occurs when you are working in an interactive SAS® session |
R19009 |
| 54940 | In SAS® 9.4 on UNIX, a fatal error occurs when using the FILENAME PIPE engine to ftp a file with RECFM=S370VB |
R19026 |
| 55256 | In a UNIX environment, if you use a FILENAME statement to assign a fileref to a named pipe, the SAS® process might become unresponsive |
R19030 |
| 58671 | ALERT - In Linux environments, a SYSTASK statement might fail with a segmentation violation error |
R19061 |
| NOTE: Customers running on WX6 and WIN must install hot fix R86003. |
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
| R19073 for 64-bit Enabled Solaris |
| Base SAS 9.4_M2 |
| Issue(s) Addressed: | Introduced: |
| 53966 | A "Segmentation violation" error might be generated when referencing a macro variable in a %DO loop |
R19001 |
| 54549 | A SAS® program that uses PROC PRINTTO with a FILENAME that uses the EMAIL engine fails with a system 0C4 in SAS® 9.4 |
R19018 |
| 54551 | "WARNING: The data for boxes is incomplete or invalid. Some boxes will not be drawn." might be issued when you create box plots with ODS Graphics |
R19018 |
| 54723 | Large user-defined formats might cause an insufficient memory message and a message about insufficient contiguous storage |
R19029 |
| 55062 | The INTNX function sets the DATA step variable _ERROR_ to 1 if a missing value is used as an argument in SAS® 9.4 |
R19029 |
| 54989 | An error occurs when you use PROC COPY to copy a metadata-bound data set with a recorded encryption key to a non-bound library |
R19031 |
| 55332 | When you export data to Teradata from a product such as SAS® Enterprise Guide®, date and datetime values do not appear in the proper format |
R19031 |
| 57105 | The PLM procedure might end abnormally when the item store includes model variables with associated formats |
R19050 |
| 57692 | PROC REPORT data might be missing when it is replayed with PROC DOCUMENT |
R19055 |
| 52698 | A user 1319 abend occurs in a SAS/SHARE® server |
R19060 |
| 61157 | When you try to access tables in a metadata-bound library using SAS/SHARE®, the tables incorrectly require an ENCRYPTKEY to open |
R19073 |
| NOTE: If you install this hot fix and need the fix documented in SAS Note 55345, you must also install Base SAS hot fix R31004. |
|
| R19076 for 64-bit Enabled Solaris |
| Base SAS 9.4_M2 |
| Issue(s) Addressed: | Introduced: |
| 54456 | A sign-on with MP CONNECT can fail in Microsoft Windows operating environments where 8.3 filename support is disabled |
R19015 |
| 56619 | MP CONNECT sessions fail to start properly and return the error "Remote signon to RHOST canceled" |
R19043 |
| 57392 | The client becomes unresponsive when you use a simple Remote Library Services LIBNAME statement, which causes a crash in the SAS/CONNECT® server |
R19054 |
| 62319 | Connections might become disconnected and return "ERROR: Conversations terminated..." when you use SAS/CONNECT® software |
R19076 |
| 63215 | A segmentation violation occurs in a SAS/CONNECT® client session when you use the CONNECTKEEPALIVE environment variable |
R19076 |
|
| R84017 for 64-bit Enabled Solaris |
| Base SAS 9.4_M2 |
| Issue(s) Addressed: | Introduced: |
| 55199 | An upgrade of SAS® 9.4 software might fail or an out-of-memory condition might occur and result in the corruption of metadata |
R84001 |
| 53770 | An orphaned gridrun.exe process occurs when users close a SAS® Enterprise Guide® session that is running in a SAS® grid environment |
R84002 |
| 53765 | The load balancer might fail when it tries to reuse a grid-launched, pooled workspace server |
R84002 |
| 53944 | A SAS® Workspace Server connection failure can occur in SAS® Studio when you use SAS® token authentication |
R84002 |
| 54629 | SAS® Grid option sets do not work as expected |
R84002 |
| 54819 | High job submission rates might result in grid-launched workspace servers failing to start |
R84002 |
| 55021 | Clustered SAS® Metadata Servers lose their quorum status |
R84002 |
| 55014 | The SAS® import procedure fails and returns errors to the SAS® Metadata Server log file |
R84002 |
| 55945 | A SAS Metadata Server backup with the "Reorganize repositories" option enabled might damage the Foundation repository |
R84004 |
| 56029 | SAS® clients might receive a connection time-out message when you try to connect to a SAS® 9.4 Metadata Server cluster |
R84005 |
| 56186 | The object spawner might fail when you use load balancing with SAS® Cost and Profitability Management 8.1 |
R84006 |
| 56751 | SAS® 9.4 Metadata Server cluster might become unresponsive after a user bulkload program is completed |
R84008 |
| 57013 | Load-balancing problems can occur if a SAS® Stored Process Server process fails to start |
R84011 |
| 57224 | Adding a new login containing a user ID that is already associated with an existing identity damages the Foundation repository |
R84012 |
| 57367 | A SAS® 9.4 metadata user bulk load can take many hours to complete when the SAS® Metadata Server is clustered |
R84012 |
| 57428 | In a SAS® Metadata Server cluster, the master node does not send redirection requests to a slave node that is a part of the quorum |
R84013 |
| 58101 | SAS® Metadata Server abnormally terminates with an "unhandled Exception" and the traceback indicates a failure in the KeepAliveThread |
R84015 |
| 58452 | All servers stop responding in a load-balanced cluster |
R84015 |
| 55985 | The error "Too many files are open" is logged when you have clustered SAS® Metadata Servers |
R84017 |
| 59404 | A vulnerability on authorizations to metadata table objects exists in SAS® Metadata Server |
R84017 |
NOTE: You must also install hot fix R72003 for SAS Studio 3.2 to fully implement the fix for the issue described in 53944.
You must also install hot fix R33010 for SAS Threaded Kernel Grid to fully implement the fix for the issue described in 54819. |
|
| S28008 for 64-bit Enabled Solaris |
| SAS/Secure SSL 9.4_M2 hot fix for Base SAS 9.4_M2 |
| Issue(s) Addressed: | Introduced: |
| 53953 | Errors might occur when you connect to a server with SAS® clients and programs that use the Secure Sockets Layer (SSL) protocol |
S28001 |
| 54374 | ALERT - Secure Sockets Layer (SSL) capability in SAS® Foundation products is susceptible to the POODLE security vulnerability |
S28001 |
| 54073 | ALERT - OpenSSL security vulnerabilities (6 Aug 2014) exist in SAS/SECURE™ software |
S28001 |
| 56161 | Error messages appear in the SAS® log and the step terminates when you use the AUTHTLS option in the FILENAME FTP statement |
S28002 |
| 55767 | ALERT - OpenSSL security vulnerabilities (19 Mar 2015) exist in the Secure Sockets Layer (SSL) capability in SAS® Foundation products |
S28003 |
| 56385 | ALERT - OpenSSL security vulnerabilities (11 Jun 2015 and 9 Jul 2015) exist in the Secure Sockets Layer (SSL) capability in SAS® Foundation products |
S28004 |
| 57686 | OpenSSL security vulnerabilities (4 Dec 2015) exist in the Secure Sockets Layer (SSL) capability in SAS® Foundation products |
S28005 |
| 58391 | OpenSSL version 1.0.2h is available for SAS® 9.3 and 9.4 on UNIX and z/OS |
S28006 |
| 58785 | ALERT - The HTTP procedure generates an exception error |
S28006 |
| 59244 | OpenSSL vulnerabilities exist in the Secure Sockets Layer (SSL) capability in SAS® Foundation products (OpenSSL advisories through 26 September 2016) |
S28007 |
| 61700 | OpenSSL vulnerabilities exist in the Secure Sockets Layer (SSL) capability in SAS® Foundation products (OpenSSL advisories through 02 November 2017) |
S28008 |
| Released: February 16, 2018 | | D | | |
|
| IMPORTANT: Please contact SAS Technical Support for information on accessing this hot fix and reference SAS Note 61700 |
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
General Information about Hot Fixes