| A3Z054 |
| Base SAS 9.4_M4 |
| Issue(s) Addressed: | Introduced: |
| 59557 | ALERT - Incorrect results occur when you subset a relational database management system table based on a date variable |
A3Z005 |
| 60066 | You might experience slow performance when you run PROC DS2 with large formats |
A3Z005 |
| 59529 | Remote Library Services library allocation fails with "ERROR: Invalid libref..." |
A3Z012 |
| 60086 | "ERROR: An exception has been encountered" occurs when registering a table in a concatenated library that contains a SAS® metadata-bound library |
A3Z012 |
| 20666 | The CONTENTS=YES option in the ODS PDF statement generates errors or incorrect output |
A3Z016 |
| 61157 | When you try to access tables in a metadata-bound library using SAS/SHARE®, the tables incorrectly require an ENCRYPTKEY to open |
A3Z029 |
| 61411 | Zero rows are returned for a WHERE expression |
A3Z033 |
| 61515 | When you use the Traditional Chinese edition of SAS®, using VIEWTABLE to open a SAS® data set fails with "ERROR: No such object..." |
A3Z033 |
| 61606 | In lockdown mode, you cannot use JAVAOBJ or the JAVAINFO procedure |
A3Z036 |
| 61881 | The system becomes unresponsive when you attempt to disable SASCMD sign-on by removing the sasxdmr.dll file |
A3Z040 |
| 47301 | Creating a model package gives "ERROR: ARCHIVE transport engine encountered errors while publishing the package" |
A3Z041 |
| 62567 | The ANYDTDTM informat does not read values correctly |
A3Z050 |
| 63922 | The IMPORT procedure drops the time portion of a datetime value |
A3Z050 |
| 62724 | ALERT - A WHERE clause that contains an OR condition returns incorrect results when the first two arguments of the OR condition are the same |
A3Z053 |
| 63050 | An error occurs when SAS/CONNECT® is not licensed and either a %SYSLPUT or %SYSRPUT statement (or both) is in the compiled code |
A3Z054 |
NOTE: If you install this hot fix and have Base SAS 9.4_M4 installed, you must also install hot fix A3Z057.
If you install this hot fix and have Base SAS 9.4_M4 installed, you must also install hot fix A3Z052.
If you install this hot fix and have Base SAS 9.4_M4 installed, you must also install hot fix A3Z042.
If you install this hot fix and have SAS Integration Technologies 9.4_M4 installed, you must also install hot fix B4I002. |
|
|
| A3Z056 |
| Base SAS 9.4_M4 |
| Issue(s) Addressed: | Introduced: |
| 61075 | Column lengths on the same table are different when you use different schema names in FEDSVR library |
A3Z027 |
| 63170 | "Unable to transcode data to/from UCS-2 encoding" occurs after invalid characters are read in an Amazon Redshift, Netezza, or PostgreSQL table |
A3Z056 |
NOTE: If you install this hot fix, you must also install hot fix A3Z062 for Base SAS 9.4_M4.
If you install this hot fix, you must also install hot fix A3Z057 for Base SAS 9.4_M4. |
|
|
| A3Z057 |
| Base SAS 9.4_M4 |
| Issue(s) Addressed: | Introduced: |
| 47303 | PROC METALIB returns meaningless text and the error "No metadata objects found matching the specified URI" |
A3Z004 |
| 59529 | Remote Library Services library allocation fails with "ERROR: Invalid libref..." |
A3Z004 |
| 59785 | Updating an Oracle table via the META engine results in a U1335 error |
A3Z004 |
| 60051 | Running PROC METALIB deletes column mappings from SAS® Data Integration Studio jobs |
A3Z004 |
| 60564 | Running the METALIB procedure results in a segmentation violation and duplicate index objects |
A3Z021 |
| 61614 | The METALIB procedure incorrectly adds duplicate tables in the metadata if you use a PREFIX statement |
A3Z035 |
| 60910 | An access violation occurs when you update metadata for a table that contains more than 50 indexes |
A3Z039 |
| 63170 | "Unable to transcode data to/from UCS-2 encoding" occurs after invalid characters are read in an Amazon Redshift, Netezza, or PostgreSQL table |
A3Z057 |
| NOTE: If you install this hot fix, you must also install hot fixes A3Z062, A3Z054, and A3Z056 for Base SAS 9.4_M4. |
|
|
| A3Z058 |
| Base SAS 9.4_M4 |
| Issue(s) Addressed: | Introduced: |
| 54751 | The BETWEEN operator might re-order values, possibly leading to unexpected results in a linguistic-sensitive environment |
A3Z008 |
| 58657 | A performance issue occurs when you join a SAS® table with a DBMS table and you have a CALCUALTED column in the WHERE clause |
A3Z008 |
| 59609 | Performance enhancements have been made to PROC SQL views |
A3Z008 |
| 59871 | When using a numeric value instead of a date constant to subset a DBMS table, unexpected results or performance problems occur |
A3Z008 |
| 61621 | Performance issues or an ORA-01841 error might occur when querying a DBMS table |
A3Z008 |
| 52906 | An error might occur when you are using the INDEX or FIND function in a WHERE clause and you query DICTIONARY tables |
A3Z034 |
| 59247 | When you rename a date column and use it in date calculations, "ERROR: sqlplan internal error..." occurs |
A3Z034 |
| 61406 | Certain queries generate "ERROR: sqlplan internal error..." |
A3Z034 |
| 61413 | SAS® Data Integration Studio might hang and throw access violation errors when you scroll through output data |
A3Z034 |
| 61414 | ALERT - Incorrect results are returned when you use a DISTINCT or COUNT(*) function in an SQL procedure |
A3Z034 |
| 61534 | "The SAS task name is [SQL]...Segmentation Violation" might occur when you use the INPUT function in the SQL pass-through |
A3Z034 |
| 61372 | Running an SQL procedure query returns "ERROR: sqlplan internal error..." |
A3Z047 |
| 62364 | You receive an empty result set after you query a SAS® table or SAS view that is created from a DBMS table |
A3Z047 |
| 62403 | The SQLIPONEATTEMPT system option does not work as expected, and the PROC SQL query continues processing |
A3Z047 |
| 62560 | You receive a "Read Access Violation" error when you use a WHERE clause for a view that contains a concatenation operator |
A3Z047 |
| 62562 | An SQLPLAN error might occur when one or more variables are created in an inline view |
A3Z047 |
| 62572 | An error occurs when using a dictionary view in a DATA step with a WHERE statement that contains the IN operator |
A3Z047 |
| 62577 | ALERT - Using a WHERE clause with multiple AND conditions for a SASHELP view might return an incorrect result |
A3Z047 |
| 62752 | Incorrect results are generated when you use multiple views with the SQL procedure |
A3Z047 |
| 64819 | A DATA step that executes a PROC SQL view with a WHERE clause does not select the index |
A3Z058 |
|
|
| A3Z059 |
| Base SAS 9.4_M4 |
| Issue(s) Addressed: | Introduced: |
| 59542 | Attempting to open a data set in VIEWTABLE fails with "ERROR: No such object. Parameters passed to method _SETCOLUMNCONFORMTHRESHOLD" |
A3Z002 |
| 63562 | The COMPARE procedure can generate an exception error if the locale is set to German |
A3Z059 |
| NOTE: This hot fix is applicable to systems with one or more of the following languages installed:
Chinese Traditional (Taiwan), French, German, Italian, Polish |
|
|
| A3Z062 |
| Base SAS 9.4_M4 |
| Issue(s) Addressed: | Introduced: |
| 61307 | Using the CONNECTION=GLOBAL option sometimes causes a deadlock |
A3Z030 |
| 61486 | Hadoop jobs containing a WHERE clause encounter a sporadic "...ABORT: SAS/TK is aborting..." error |
A3Z032 |
| 61658 | Cells might not be properly reinitialized when you read SAS/ACCESS® Interface to Hadoop data in SAS® Enterprise Guide® |
A3Z032 |
| 62004 | The SAS/ACCESS® engine ignores blank values when you use the WHERE clause with PROC SQL |
A3Z043 |
| 62176 | A ParseException occurs when you use SAS® system option DBIDIRECTEXEC with the LIBNAME option DBCREATE_TABLE_OPTS= |
A3Z043 |
| 62565 | You receive "ERROR: ORACLE prepare error: ORA-00907: missing right parenthesis. . ." after you use PROC SQL to join a SAS table to an Oracle table |
A3Z051 |
| 62882 | The DBCONINIT= and DBCONTERM= LIBNAME options are ignored on database connections that are opened for threaded Reads |
A3Z051 |
| 63170 | "Unable to transcode data to/from UCS-2 encoding" occurs after invalid characters are read in an Amazon Redshift, Netezza, or PostgreSQL table |
A3Z051 |
| 63630 | Performance issues or an ORA-01841 error might occur when you query a database management system (DBMS) table |
A3Z062 |
| 63997 | "ERROR: ORA" occurs when you try to read data from Oracle using DBCONINIT="exec " and DBSLICEPARM=ALL |
A3Z062 |
NOTE: If you install this hot fix you must also install hot fixes A3Z056 and A3Z057 for Base SAS 9.4_M4.
If you install this hot fix and have SAS/ACCESS Interface to Amazon Redshift 9.41 installed, you must also install hot fix C7J002.
If you install this hot fix and have SAS/ACCESS Interface to Aster 9.41 installed, you must also install hot fix D9K001.
If you install this hot fix and have SAS/ACCESS Interface to DB2 9.41 installed, you must also install hot fix B5Z004.
If you install this hot fix and have SAS/ACCESS Interface to Greenplum 9.41 installed, you must also install hot fix D9M002.
If you install this hot fix and have SAS/ACCESS Interface to Hadoop 9.44 installed, you must also install hot fix A7J005.
If you install this hot fix and have SAS/ACCESS Interface to HAWQ 9.4_M1 installed, you must also install hot fix D9N001.
If you install this hot fix and have SAS/ACCESS Interface to Impala 9.43 installed, you must also install hot fix B7D003.
If you install this hot fix and have SAS/ACCESS Interface to Informix 9.42 installed, you must also install hot fix D9P001.
If you install this hot fix and have SAS/ACCESS Interface to Microsoft SQL Server 9.42 installed, you must also install hot fix B7T001.
If you install this hot fix and have SAS/ACCESS Interface to MySQL 9.4_M4 installed, you must also install hot fix B7B002.
If you install this hot fix and have SAS/ACCESS Interface to Netezza 9.41 installed, you must also install hot fix A7C004.
If you install this hot fix and have SAS/ACCESS Interface to ODBC 9.4_M4 installed, you must also install hot fix B7S002.
If you install this hot fix and have SAS/ACCESS Interface to OLE DB 9.4_M4 installed, you must also install hot fix C9F002.
If you install this hot fix and have SAS/ACCESS Interface to Oracle 9.41 installed, you must also install hot fix B4F004.
If you install this hot fix and have SAS/ACCESS Interface to PC Files 9.4_M4 installed, you must also install hot fix A7I007.
If you install this hot fix and have SAS/ACCESS Interface to PostgreSQL 9.4_M4 installed, you must also install hot fix D6E001.
If you install this hot fix and have SAS/ACCESS Interface to R/3 4.4_M4 installed, you must also install hot fix B6X002.
If you install this hot fix and have SAS/ACCESS Interface to SAP ASE 9.4_M3 installed, you must also install hot fix D9R001.
If you install this hot fix and have SAS/ACCESS Interface to SAP HANA 9.43 installed, you must also install hot fix C9B002.
If you install this hot fix and have SAS/ACCESS Interface to SAP IQ 9.4_M3 installed, you must also install hot fix D9Q001.
If you install this hot fix and have SAS/ACCESS Interface to Teradata 9.44 installed, you must also install hot fix C3N004.
If you install this hot fix and have SAS/ACCESS Interface to Vertica 9.4_M4 installed, you must also install hot fix D9S001. |
|
|
| A3Z064 |
| Base SAS 9.4_M4 |
| Issue(s) Addressed: | Introduced: |
| 60456 * | Using memory-based libraries might cause a wrong page to be returned or the data set to appear in the wrong library |
A3Z009 |
| 60654 * | PROC CONTENTS might generate a "Read Access Violation" error if the data set is stored on a remote drive |
A3Z022 |
| 60701 | When you use the SYSTASK COMMAND in SAS® 9.4 TS1M4, standard out (stdout) and standard error (stderr) are not written to the SAS® log |
A3Z023 |
| 64207 | A segmentation violation occurs after you submit SYSTASK and WAITFOR statements repeatedly within a macro loop |
A3Z064 |
| * Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems. |
| NOTE: If you install this hot fix, you must also install hot fix A5F002 for SAS Threaded Kernel Core Routines 9.4_M4. |
|
|
| B8H001 |
| SAS/Secure SSL 9.41_M1 hot fix for Base SAS 9.4_M4 |
| Issue(s) Addressed: | Introduced: |
| 61700 | OpenSSL vulnerabilities exist in the Secure Sockets Layer (SSL) capability in SAS® Foundation products (OpenSSL advisories through 02 November 2017) |
B8H001 |
| NOTE: Please contact SAS Technical Support for information on accessing this hot fix and reference SAS Note 61700 |
| z/OS |
Released: February 16, 2018 | | D | | |
| z/OS 64-bit |
Released: February 16, 2018 | | D | | |
| 64-bit Enabled Solaris |
Released: February 16, 2018 | | D | | |
| 64-bit Enabled AIX |
Released: February 16, 2018 | | D | | |
| HP-UX IPF |
Released: February 16, 2018 | | D | | |
| Linux for x64 |
Released: February 16, 2018 | | D | | |
| Solaris for x64 |
Released: February 16, 2018 | | D | | |
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
| C1Q004 |
| Base SAS 9.4_M4 |
| Issue(s) Addressed: | Introduced: |
| 61074 | Using the PROC S3 LIST statement to list buckets in the EU Frankfurt region (REGION=eufrankfurt) might cause a segmentation violation |
C1Q001 |
| 61870 | The S3 procedure fails in environments where HTTP requests must route through a forward HTTP proxy server |
C1Q001 |
| 61888 | Additional Amazon Web Service (AWS) S3 regions are available in the S3 procedure |
C1Q001 |
| 63524 | The PROC S3 PUT statement fails with a segmentation violation or write thread errors |
C1Q002 |
| 63674 | The HTTP procedure applies percent encoding in a URL that includes a comma within a set of parentheses |
C1Q003 |
| 64157 | PROC S3 operations fail with an exception |
C1Q004 |
|
|
Important changes to Hot Fixes!