| B6Q052 |
| Base SAS 9.4_M5 |
| Issue(s) Addressed: | Introduced: |
| 61614 | The METALIB procedure incorrectly adds duplicate tables in the metadata if you use a PREFIX statement |
B6Q006 |
| 60910 | An access violation occurs when you update metadata for a table that contains more than 50 indexes |
B6Q013 |
| 61891 | You might experience slow performance when updating the metadata for Oracle tables |
B6Q013 |
| 63170 | "Unable to transcode data to/from UCS-2 encoding" occurs after invalid characters are read in an Amazon Redshift, Impala, Netezza, or PostgreSQL table |
B6Q042 |
| 63180 | PROC METALIB fails with a segmentation violation or an error when you update tables with a foreign key that references a non-primary key |
B6Q042 |
| 63449 | The METALIB procedure contains a security vulnerability |
B6Q052 |
| 63593 | The METALIB procedure might fail with a segmentation violation or an error when you update tables that contain multiple foreign keys |
B6Q052 |
| NOTE: If you install this hot fix, you must also install hot fix B6Q099 for Base SAS 9.4_M5. |
|
|
| B6Q067 |
| Base SAS 9.4_M5 |
| Issue(s) Addressed: | Introduced: |
| 62323 | The KUPDATE function fails to run and returns the "Invalid argument 3 to function KUPDATE..." note when you include it in a PROC SQL step |
B6Q022 |
| 63402 | The KCOMPRESS function now supports a third argument to allow for modifiers |
B6Q055 |
| 61811 | Character variable length increases when you upload a UTF-8 data set to CAS with PROC CASUTIL |
B6Q067 |
NOTE: If you install this hot fix and need the fix documented in SAS Note 63402, you must also install hot fixes
B6Q105 for Base SAS 9.4_M5,
C1S005 for SAS Threaded Kernel 9.4_M5,
E2E001 for SAS Threaded Kernel User Functions 9.4_M5. |
|
|
| B6Q092 |
| Base SAS 9.4_M5 |
| Issue(s) Addressed: | Introduced: |
| 62411 | You cannot view BLOB or CLOB data from an Oracle table when you use a LIBNAME statement with the FEDSVR engine |
B6Q024 |
| 62582 | You encounter performance issues when you try to get a list of tables or views using the FEDSVR LIBNAME engine |
B6Q030 |
| 63320 | SAS® Federation Server does not translate the DATE format as documented for a view (DSN=BASE) created from database tables |
B6Q043 |
| 63831 | Transcoded Oracle data is truncated incorrectly by the SAS® Federation Server LIBNAME (FEDSRV) engine |
B6Q063 |
| 65920 | The PRINT procedure fails to work, and you see an error regarding the sorted data set from the SAS® Federation Server (FEDSVR) engine |
B6Q092 |
| 65954 | You see a "String data, right-truncated LOCALE…" error when trying to copy or create a table via the SAS® Federation Server (FEDSVR) engine |
B6Q092 |
NOTE: If you install this hot fix, you must also install hot fix B6Q099 for Base SAS 9.4_M5.
If you install this hot fix and have SAS Threaded Kernel Extensions for FedSQL and DS2 Standalone 9.4_M5 installed, you must also install hot fix C7Z002.
If you install this hot fix and have SAS Federation Server 4.2 installed on Linux for x64, you must also install hot fix Y46013. |
|
|
| B6Q098 |
| Base SAS 9.4_M5 |
| Issue(s) Addressed: | Introduced: |
| 61372 | Running an SQL procedure query returns "ERROR: sqlplan internal error..." |
B6Q027 |
| 61406 | Certain queries generate "ERROR: sqlplan internal error..." |
B6Q027 |
| 62364 | You receive an empty result set after you query a SAS® table or SAS view that is created from a DBMS table |
B6Q027 |
| 62403 | The SQLIPONEATTEMPT system option does not work as expected, and the PROC SQL query continues processing |
B6Q027 |
| 62560 | You receive a "Read Access Violation" error when you use a WHERE clause for a view that contains a concatenation operator |
B6Q027 |
| 62562 | An SQLPLAN error might occur when one or more variables are created in an inline view |
B6Q027 |
| 62572 | An error occurs when using a dictionary view in a DATA step with a WHERE statement that contains the IN operator |
B6Q027 |
| 62577 | ALERT - Using a WHERE clause with multiple AND conditions for a SASHELP view might return an incorrect result |
B6Q027 |
| 62752 | Incorrect results are generated when you use multiple views with the SQL procedure |
B6Q027 |
| 63203 | ALERT - Incorrect results might occur with an implicit pass-through SQL query when you use nested views to create calculated variables |
B6Q044 |
| 62789 | Applying a predicate such as a WHERE clause to a data set view outside of PROC SQL generates an unexpected warning message |
B6Q045 |
| 63344 | Queries that reference DBMS user-defined functions are not sent to the database for processing via implicit pass-through |
B6Q045 |
| 63348 | Incorrect results are returned when you use a WHERE clause in an SQL procedure to subset blanks |
B6Q045 |
| 63352 | Different queries can be passed to the database when you compare a variable to a null value |
B6Q045 |
| 63923 | An enhancement to the SAS® system option SQLIPONEATTEMPT prevents further attempts to run a query if an error occurs while the query is running |
B6Q056 |
| 63940 | Subsetting a view in SAS® 9.4M5 (TS1M5) with a comparison operator that contains an equal sign and colon (=:) returns different results than expected |
B6Q056 |
| 64015 | A memory leak occurs after multiple CONNECT and DISCONNECT statements when you use the SQL procedure with explicit pass-through |
B6Q056 |
| 64343 | A PROC SQL query that joins multiple Hive tables results in "Execute error: Error while compiling statement: FAILED: SemanticException[Error 10017]" |
B6Q071 |
| 64342 | Performance degradation might occur when you use a PROC SQL query to access SAS® Scalable Performance Data Server 5.4 |
B6Q073 |
| 64422 | A new environment variable, SAS_PRESERVE_EMPTY_STRING, provides options for the behavior when a blank or empty string is encountered |
B6Q073 |
| 62267 | ALERT - ETL jobs in the SAS® Merchandise Intelligence Suite might fail with "ERROR: File does not exist" and "Statement not executed due to NOEXEC option" |
B6Q076 |
| 64528 | Aggregate functions are not passed down through an implicit pass-through query to Apache Hive |
B6Q076 |
| 64592 | "ERROR: The SQL statement contains a UDF that is not being passed to the database" occurs with Hadoop queries that contain user-defined functions |
B6Q076 |
| 65036 | SAS® Customer Intelligence queries to five or more joined DBMS tables take a long time to execute |
B6Q087 |
| 65537 | An SQL procedure might generate incorrect results when a variable is renamed in a query |
B6Q096 |
| 65539 | A query might return incorrect results if it contains an SQL JOIN to a variable that was created in an SQL view |
B6Q096 |
| 65553 | A query passed to a database might not include the ORDER BY clause when a variable is renamed |
B6Q096 |
| 65563 | You encounter performance problems when a query passed to a database does not include a WHERE clause |
B6Q096 |
| 65581 | An SQL procedure query that creates a SAS® table returns a "Write Access Violation" error |
B6Q096 |
| 65597 | An SQL procedure query with a WHERE clause that contains multiple subselects might return incorrect results |
B6Q096 |
| 65766 | Ambiguous column or duplicate column errors might occur when running a query against a database |
B6Q096 |
| 66193 | Joining multiple DBMS tables might result in performance issues because some of the processing is done in SAS® rather than in the database |
B6Q096 |
| 67011 | A query that is passed to the database might include an incorrect variable name in the GROUP BY clause |
B6Q098 |
| NOTE: If you install this hot fix, you must also install hot fixes B6Q099 and B6Q105 for Base SAS 9.4_M5. |
|
|
| B6Q099 |
| Base SAS 9.4_M5 |
| Issue(s) Addressed: | Introduced: |
| 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 |
B6Q038 |
| 62882 | The DBCONINIT= and DBCONTERM= LIBNAME options are ignored on database connections that are opened for threaded Reads |
B6Q038 |
| 63170 | "Unable to transcode data to/from UCS-2 encoding" occurs after invalid characters are read in an Amazon Redshift, Impala, Netezza, or PostgreSQL table |
B6Q038 |
| 63230 | "ERROR: The file has too long a member name..." occurs when you try to read an Oracle table name with more than 30 bytes |
B6Q038 |
| 63320 | SAS® Federation Server does not translate the DATE format as documented for a view (DSN=BASE) created from database tables |
B6Q038 |
| 63630 | Performance issues or an ORA-01841 error might occur when you query a database management system (DBMS) table |
B6Q057 |
| 63997 | "ERROR: ORA" occurs when you try to read data from Oracle using DBCONINIT="exec " and DBSLICEPARM=ALL |
B6Q057 |
| 64422 | A new environment variable, SAS_PRESERVE_EMPTY_STRING, provides options for the behavior when a blank or empty string is encountered |
B6Q074 |
| 65789 | The "Create Date" attribute for tables in Hadoop shows as missing in SAS® Studio and in output from the CONTENTS procedure |
B6Q091 |
| 67588 | A segmentation violation occurs in SAS/ACCESS® Interface to Oracle when you use PROC SQL with the PRESERVE_COMMENTS option |
B6Q099 |
NOTE: If you install this hot fix you must also install hot fixes B6Q052, B6Q092, B6Q048, B6Q098, and B6Q105 for Base SAS 9.4_M5.
If you install this hot fix and have SAS/ACCESS Interface to Amazon Redshift 9.42 installed, you must also install hot fix C7K003.
If you install this hot fix and have SAS/ACCESS Interface to Aster 9.42 installed, you must also install hot fix D8Z001.
If you install this hot fix and have SAS/ACCESS Interface to DB2 9.42 installed, you must also install hot fix F9R001.
If you install this hot fix and have SAS/ACCESS Interface to DB2 9.42 installed on z/OS or z/OS 64-bit, you must also install hot fix B7W004.
If you install this hot fix and have SAS/ACCESS Interface to Greenplum 9.42 installed, you must also install hot fix C9M005.
If you install this hot fix and have SAS/ACCESS Interface to Hadoop 9.45 installed, you must also install hot fix D7H004.
If you install this hot fix and have SAS/ACCESS Interface to HAWQ 9.4_M2 installed, you must also install hot fix D9A001.
If you install this hot fix and have SAS/ACCESS Interface to Impala 9.44 installed, you must also install hot fix B7E004.
If you install this hot fix and have SAS/ACCESS Interface to Informix 9.43 installed, you must also install hot fix D9B001.
If you install this hot fix and have SAS/ACCESS Interface to Microsoft SQL Server 9.43 installed, you must also install hot fix B7X002.
If you install this hot fix and have SAS/ACCESS Interface to MySQL 9.4_M5 installed, you must also install hot fix B7J002.
If you install this hot fix and have SAS/ACCESS Interface to Netezza 9.42 installed, you must also install hot fix C9E003.
If you install this hot fix and have SAS/ACCESS Interface to ODBC 9.4_M5 installed, you must also install hot fix B7V003.
If you install this hot fix and have SAS/ACCESS Interface to OLE DB 9.4_M5 installed, you must also install hot fix D9C002.
If you install this hot fix and have SAS/ACCESS Interface to Oracle 9.42 installed, you must also install hot fix C7I004.
If you install this hot fix and have SAS/ACCESS Interface to PC Files 9.4_M5 installed, you must also install hot fix B7U005.
If you install this hot fix and have SAS/ACCESS Interface to the PI System 9.43 installed, you must also install hot fix D3W006.
If you install this hot fix and have SAS/ACCESS Interface to PostgreSQL 9.4_M5 installed, you must also install hot fix D6F004.
If you install this hot fix and have SAS/ACCESS Interface to R/3 4.4_M5 installed, you must also install hot fix D9D001.
If you install this hot fix and have SAS/ACCESS Interface to SAP ASE 9.4_M4 installed, you must also install hot fix D9G001.
If you install this hot fix and have SAS/ACCESS Interface to SAP HANA 9.44 installed, you must also install hot fix D9E001.
If you install this hot fix and have SAS/ACCESS Interface to SAP IQ 9.4_M4 installed, you must also install hot fix D9F001.
If you install this hot fix and have SAS/ACCESS Interface to Teradata 9.45 installed, you must also install hot fix D9H003.
If you install this hot fix and have SAS/ACCESS Interface to Vertica 9.4_M5 installed, you must also install hot fix D6G003.
|
|
|
| B6Q102 |
| Base SAS 9.4_M5 |
| Issue(s) Addressed: | Introduced: |
| 61713 | SAS® does not finish reading data sets that contain the RECFM=N DCB attribute |
B6Q009 |
| 62495 | Reading in and/or writing to a PDS GDG on z/OS fails with "WARNING: Member specified for a directory concatenation: 0..." in SAS® 9.4M5 (TS1M5) |
B6Q028 |
| 62507 | The INFILE/FILE user exit interface might fail due to changes in SAS® 9.4 TS1M5 |
B6Q033 |
| 60730 | Initialization of SAS® shows system abend 0C4 when there are more than 16 CPs |
B6Q059 |
| 64237 | "ERROR:The requested LPAR name...does not match the actual LPAR name" occurs when you run sub-capacity setinits and apply IBM security patches (APARs) |
B6Q072 |
| 67930 | A SAS/SHARE® server might not honor the operating system file permissions |
B6Q102 |
| NOTE: UNIX and Windows customers must install hot fix B6Q104 instead of hot fix B6Q102. |
|
|
| B6Q104 |
| Base SAS 9.4_M5 |
| Issue(s) Addressed: | Introduced: |
| 61355 | Clicking the Break button in the 9.4 version of Base SAS® might cause the application to fail |
B6Q001 |
| 62333 | A DATA step fails with "ERROR: Rename of temporary member for libname.data-set-name.DATA failed" |
B6Q037 |
| 63389 | Code that sets consecutive SYSTASK commands stops executing after about 6,481 consecutive attempts |
B6Q051 |
| 64207 | A segmentation violation occurs after you submit SYSTASK and WAITFOR statements repeatedly within a macro loop |
B6Q070 |
| 67930 | A SAS/SHARE® server might not honor the operating system file permissions |
B6Q101 |
| 68441 | Deleting a table from the Work library results in a Read Access Violation if the SAS® system option MEMLIB is used |
B6Q104 |
NOTE: z/OS customers must install hot fix B6Q102 instead of hot fix B6Q104.
Windows customers must also install hot fix B5M019 for SAS Threaded Kernel Core Routines 9.4_M5. |
|
|
| B6Q105 |
| Base SAS 9.4_M5 |
| Issue(s) Addressed: | Introduced: |
| 61157 | When you try to access tables in a metadata-bound library using SAS/SHARE®, the tables incorrectly require an ENCRYPTKEY to open |
B6Q004 |
| 61606 | In lockdown mode, you cannot use JAVAOBJ or the JAVAINFO procedure |
B6Q007 |
| 61881 | The system becomes unresponsive when you attempt to disable SASCMD sign-on by removing the sasxdmr.dll file |
B6Q014 |
| 62205 | You might encounter "ERROR: Error in the FILENAME statement" after lockdown processing |
B6Q017 |
| 62346 | The SAS/SHARE® server abends with a Segmentation Violation during logging operations |
B6Q026 |
| 62567 | The ANYDTDTM informat does not read values correctly |
B6Q031 |
| 63922 | The IMPORT procedure drops the time portion of a datetime value |
B6Q031 |
| 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 |
B6Q041 |
| 63295 | A SAS® session can stop working in a Microsoft Windows operating environment due to incorrect syntax for an %IF macro statement in open code |
B6Q047 |
| 62515 | Memory exhaustion and high CPU usage might occur when you set the PAGESIZE system option to a high value in SAS® 9.4M5 (TS1M5) |
B6Q049 |
| 63402 | The KCOMPRESS function now supports a third argument to allow for modifiers |
B6Q054 |
| 63508 | An application that is executed multiple times ends with an exception |
B6Q066 |
| 64175 | Model packages are not created and the report.log file shows "ERROR: ARCHIVE transport engine encountered errors while publishing the package..." |
B6Q068 |
| 64422 | A new environment variable, SAS_PRESERVE_EMPTY_STRING, provides options for the behavior when a blank or empty string is encountered |
B6Q075 |
| 64543 | The message "ERROR: Recursive Segmentation Violations" appears in the SAS® log after you run code with incorrect syntax |
B6Q077 |
| 63624 | An unpaired quotation mark in a LIBNAME statement generates the message "Error: Buffer overrun occurred" |
B6Q081 |
| 65983 | The LUA procedure contains an authorization-bypass vulnerability |
B6Q093 |
| 65606 | Using a forward slash with the %SYSLPUT or %SYSRPUT statement in SAS® 9.4M5 causes existing code to fail with "Unrecognized option..." |
B6Q097 |
| 67647 | Using PROC FORMAT with a large data set in a Linux operating environment causes an exception and a segmentation violation |
B6Q105 |
NOTE: If you install this hot fix and need the fix documented in SAS Note 62515, you must also install hot fix B6Q083 for Base SAS 9.4_M5.
If you install this hot fix and need the fix documented in SAS Note 65983, you must also install hot fix B6Q094 for Base SAS 9.4_M5 and C1S014 for SAS Threaded Kernel 9.4_M5..
If you install this hot fix and need the fix documented in SAS Note 63402, you must also install hot fixes
B6Q067 for Base SAS 9.4_M5,
C1S005 for SAS Threaded Kernel 9.4_M5,
E2E001 for SAS Threaded Kernel User Functions 9.4_M5.
If you install this hot fix and need the fix documented in SAS Note 64175, you must also install hot fixes:
B6Q069 for Base SAS 9.4_M5,
D9I002 for SAS Integration Technologies 9.4_M5.
If you install this hot fix, and need the fix documented in SAS Note 64422, you must also install hot fixes B6Q099 and B6Q098 for Base SAS 9.4_M5. |
|
|
| B8G002 |
| SAS/Secure SSL 9.41_M2 hot fix for Base SAS 9.4_M5 |
| 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) |
B8G001 |
| 66213 | Certificates that shipped in SAS® 9.4 contain an expired certificate from Sectigo AddTrust (expired on May 30, 2020) |
B8G002 |
| NOTE: Please contact SAS Technical Support for information on accessing this hot fix and reference SAS Note 61700 |
| z/OS |
Released: July 23, 2020 | | D | | |
| z/OS 64-bit |
Released: July 23, 2020 | | D | | |
| 64-bit Enabled Solaris |
Released: July 23, 2020 | | D | | |
| 64-bit Enabled AIX |
Released: July 23, 2020 | | D | | |
| HP-UX IPF |
Released: July 23, 2020 | | D | | |
| Linux for x64 |
Released: July 23, 2020 | | D | | |
| Solaris for x64 |
Released: July 23, 2020 | | D | | |
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
| C1R006 |
| Base SAS 9.4_M5 |
| Issue(s) Addressed: | Introduced: |
| 61870 | The S3 procedure fails in environments where HTTP requests must route through a forward HTTP proxy server |
C1R001 |
| 61888 | Additional Amazon Web Service (AWS) S3 regions are available in the S3 procedure |
C1R001 |
| 63006 | Server-side encryption is available in the S3 procedure |
C1R002 |
| 63524 | The PROC S3 PUT statement fails with a segmentation violation or write thread errors |
C1R003 |
| 64158 | PROC S3 PUT fails with the message "ERROR: tks3ConnectionUploadPart..." |
C1R005 |
| 65195 | A segmentation violation exception occurs when you use a PUT statement with the S3 procedure |
C1R006 |
|
|
| D2L004 |
| Base SAS 9.4_M5 |
| Issue(s) Addressed: | Introduced: |
| 61253 | The grid process launcher might overwrite the caller KRB5CCNAME environment variable |
D2L001 |
| 61738 | The object spawner intermittently fails to launch Kerberos workspace servers |
D2L001 |
| 62837 * | An improved authentication module is available for SAS® 9.4M5 on 64-bit Linux |
D2L001 |
| 61250 | The sasauth module does not correctly call pam_end() on all error conditions to end the PAM connection |
D2L001 |
| 62467 | Valid user credentials are occasionally rejected by SAS® Metadata Server when you use direct LDAP authentication |
D2L001 |
| 64111 | Authentication for SAS® 9.4 TS1M6 on Oracle Solaris returns only a user's primary group |
D2L002 |
| 64825 | New sasauth options are available for integration with MapR native authentication |
D2L003 |
| 67110 | A SUBMIT statement with the R option in the IML procedure generates errors for all R code |
D2L004 |
| * Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems. |
|
| 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