| D9T123 for Solaris for x64 |
| Base SAS 9.4_M6 |
| Issue(s) Addressed: | Introduced: |
| 63630 | Performance issues or an ORA-01841 error might occur when you query a database management system (DBMS) table |
D9T008 |
| 64417 | In-database procedures require engine-specific definitions for SQL syntax requirements |
D9T035 |
| 64422 | A new environment variable, SAS_PRESERVE_EMPTY_STRING, provides options for the behavior when a blank or empty string is encountered |
D9T035 |
| 63320 | SAS® Federation Server does not translate the DATE format as documented for a view (DSN=BASE) created from database tables |
D9T041 |
| 65789 | The "Create Date" attribute for tables in Hadoop shows as missing in SAS® Studio and in output from the CONTENTS procedure |
D9T059 |
| 65938 | Incorrect values might be written to Hadoop for columns defined with the BIGINT data type |
D9T084 |
| 66251 | A segmentation violation might occur when you join two Teradata tables on BIGINT data type columns |
D9T096 |
| 67588 | A segmentation violation occurs in SAS/ACCESS® Interface to Oracle when you use PROC SQL with the PRESERVE_COMMENTS option |
D9T123 |
NOTE: If you install this hot fix, you must also install hot fixes D9T062, D9T155, D9T130, and D9T154 for Base SAS 9.4_M6.
If you install this hot fix and have SAS Threaded Kernel Extensions for FedSQL and DS2 Standalone 9.4_M6 installed, you must also install hot fix E5Q002.
If you install this hot fix and have SAS Threaded Kernel DS2 and FedSQL Language Processors 9.41_M4 installed, you must also install hot fix E9Y008.
If you install this hot fix and have SAS Threaded Kernel 9.4_M6 installed, you must also install hot fix F8C004.
If you install this hot fix and have SAS/ACCESS Interface to Hadoop 9.46 installed, you must also install hot fix E4Y013.
If you install this hot fix and have SAS/ACCESS Interface to Teradata 9.46 installed, you must also install hot fix F1K005. |
|
| D9T130 for Solaris for x64 |
| Base SAS 9.4_M6 |
| Issue(s) Addressed: | Introduced: |
| 63831 | Transcoded Oracle data is truncated incorrectly by the SAS® Federation Server LIBNAME (FEDSRV) engine |
D9T013 |
| 63320 | SAS® Federation Server does not translate the DATE format as documented for a view (DSN=BASE) created from database tables |
D9T042 |
| 64387 | The APPEND procedure generates the error "Cannot insert into readonly column column-ID" when you access data through SAS® Federation Server |
D9T042 |
| 65920 | The PRINT procedure fails to work, and you see an error regarding the sorted data set from the SAS® Federation Server (FEDSVR) engine |
D9T083 |
| 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 |
D9T083 |
| 65995 | "ERROR: CLI prepare...Invalid descriptor" occurs when you insert data into SAS® Scalable Performance Data Server with PROC SQL and the FEDSVR engine |
D9T088 |
| 67561 | A SAS® program takes longer than expected to complete when you use the FEDSRV engine to connect to SAS® Scalable Performance Data Server |
D9T130 |
| NOTE: If you install this hot fix, you must also install hot fix D9T123 for Base SAS 9.4_M6. |
|
| D9T131 for Solaris for x64 |
| Base SAS 9.4_M6 |
| Issue(s) Addressed: | Introduced: |
| 63449 | The METALIB procedure contains a security vulnerability |
D9T015 |
| 63593 | The METALIB procedure might fail with a segmentation violation or an error when you update tables that contain multiple foreign keys |
D9T015 |
| 63869 | A segmentation violation might occur when you expand a metadata library from SAS® Enterprise Guide® or SAS® Studio or execute the DATASETS procedure |
D9T015 |
| 65449 | The METALIB procedure returns a syntax error for Google BigQuery, MongoDB, Salesforce, and Snowflake databases |
D9T066 |
| 65821 | The message "ERROR: Invalid physical name" occurs when you use a JSON Engine library and METALIB or META LIBNAME Engine |
D9T078 |
| 65900 | Registering an Oracle table to the metadata might fail and generate an error |
D9T078 |
| 66025 | ALERT - Registration of an Oracle, PostgrSQL or Amazon Redshift table to metadata might fail and could impact SAS® Customer Intelligence 6.6 solutions |
D9T078 |
| 66031 | PROC METALIB fails with "ERROR: Repository repository-ID is not registered" when table metadata is updated |
D9T091 |
| 67427 | The METALIB procedure returns the error "Invalid connection string attribute : SCHEMA is required for this datasource" |
D9T121 |
| 66894 | PROC METALIB fails with "ERROR: Expected "'" or '"'" when table metadata is updated for DB2 |
D9T131 |
|
| D9T154 for Solaris for x64 |
| Base SAS 9.4_M6 |
| Issue(s) Addressed: | Introduced: |
| 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 |
D9T007 |
| 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 |
D9T007 |
| 64015 | A memory leak occurs after multiple CONNECT and DISCONNECT statements when you use the SQL procedure with explicit pass-through |
D9T007 |
| 64342 | Performance degradation might occur when you use a PROC SQL query to access SAS® Scalable Performance Data Server 5.4 |
D9T029 |
| 64343 | A PROC SQL query that joins multiple Hive tables results in "Execute error: Error while compiling statement: FAILED: SemanticException[Error 10017]" |
D9T029 |
| 64344 | A new SAS/ACCESS® Interface to Snowflake product is available as an add-on to SAS® 9.4M6 (TS1M6) in Rev. 940_19w34 or to SAS® Viya® 3.4 (19w34) |
D9T029 |
| 64345 | A new SAS/ACCESS® Interface to Google BigQuery product is available as an add-on to SAS® 9.4TS1M6 in Rev. 940_19w34 or to SAS® Viya® 3.4 (19w34) |
D9T029 |
| 64422 | A new environment variable, SAS_PRESERVE_EMPTY_STRING, provides options for the behavior when a blank or empty string is encountered |
D9T029 |
| 64528 | Aggregate functions are not passed down through an implicit pass-through query to Apache Hive |
D9T045 |
| 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 |
D9T045 |
| 65036 | SAS® Customer Intelligence queries to five or more joined DBMS tables take a long time to execute |
D9T045 |
| 64819 | A DATA step that executes a PROC SQL view with a WHERE clause does not select the index |
D9T054 |
| 64931 | An incorrect index is selected by the SQL procedure when the number of distinct values exceed 2147483647 (2 GiB - 1) |
D9T054 |
| 65138 | The message "ERROR: Provided buffer is not large enough" occurs when you use the CONNECT TO statement with the SQL procedure |
D9T054 |
| 65537 | An SQL procedure might generate incorrect results when a variable is renamed in a query |
D9T069 |
| 65539 | A query might return incorrect results if it contains an SQL JOIN to a variable that was created in an SQL view |
D9T069 |
| 66193 | Joining multiple DBMS tables might result in performance issues because some of the processing is done in SAS® rather than in the database |
D9T069 |
| 65553 | A query passed to a database might not include the ORDER BY clause when a variable is renamed |
D9T074 |
| 65581 | An SQL procedure query that creates a SAS® table returns a "Write Access Violation" error |
D9T074 |
| 65563 | You encounter performance problems when a query passed to a database does not include a WHERE clause |
D9T077 |
| 65766 | Ambiguous column or duplicate column errors might occur when running a query against a database |
D9T077 |
| 65597 | An SQL procedure query with a WHERE clause that contains multiple subselects might return incorrect results |
D9T080 |
| 65835 | A series of PROC SQL queries might not generate a distinct set of rows |
D9T080 |
| 66214 | PROC SQL queries might generate exceptions if you use the CORRESPONDING (CORR) keyword with the EXCEPT set operator to combine tables |
D9T094 |
| 66707 | An incorrect query might be sent to a database when two like-named variables are being selected and grouped on, resulting in slow performance |
D9T094 |
| 67011 | A query that is passed to the database might include an incorrect variable name in the GROUP BY clause |
D9T113 |
| 67022 | Running an SQL procedure query to a DBMS library returns the message "ERROR: sqlplan internal error..." |
D9T113 |
| 67148 | The message "ERROR: CLI prepare error...ERROR: unterminated quoted string at or near "'\\'" occurs when you use an escape character |
D9T116 |
| 67406 | A segmentation violation might occur when you query a SAS® view with a SELECT COUNT(*) clause |
D9T120 |
| 67697 | A segmentation violation might occur when the SQL query contains a HAVING clause with a function |
D9T132 |
| 67953 | A query is sent to Oracle incorrectly when you use PROC SQL with metadata LIBNAME engine (MLE) libraries and the DBIDIRECTEXEC option |
D9T132 |
| 68150 | The message "...column-name is not valid in the context where it is used" occurs with a PROC SQL view that contains a GROUP BY clause |
D9T141 |
| 70497 | A PROC SQL GROUP BY clause might return incorrect results and "The query requires remerging summary statistics back with the original data" |
D9T154 |
NOTE: If you install this hot fix, you must also install hot fixes D9T062, D9T155 and D9T123 for Base SAS 9.4_M6.
If you install this hot fix and have SAS Threaded Kernel Extensions for FedSQL and DS2 Standalone 9.4_M6 installed, you must also install hot fix E5Q002.
If you install this hot fix and have SAS Threaded Kernel DS2 and FedSQL Language Processors 9.41_M4 installed, you must also install hot fix E9Y008.
If you install this hot fix and have SAS Threaded Kernel 9.4_M6 installed, you must also install hot fix F8C004.
If you install this hot fix and have SAS/ACCESS Interface to Teradata 9.46 installed, you must also install hot fix F1K005.
If you install this hot fix and have SAS/ACCESS Interface to Amazon Redshift 9.43 installed, you must also install hot fix J6I002. |
|
| D9T155 for Solaris for x64 |
| Base SAS 9.4_M6 |
| Issue(s) Addressed: | Introduced: |
| 63688 | Using the ODS EXCEL and ODS POWERPOINT destinations with SAS/IntrNet® software in SAS® 9.4M6 (TS1M6) generates errors |
D9T017 |
| 64028 | GRIDINSTALLLOC and GRIDRSHCOMMAND are now available as SAS® system options |
D9T020 |
| 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 |
D9T025 |
| 63508 | An application that is executed multiple times ends with an exception |
D9T025 |
| 64160 | Access methods that govern when Python can be executed from SAS® code |
D9T027 |
| 64417 | In-database procedures require engine-specific definitions for SQL syntax requirements |
D9T037 |
| 64422 | A new environment variable, SAS_PRESERVE_EMPTY_STRING, provides options for the behavior when a blank or empty string is encountered |
D9T037 |
| 64430 | The IMPORT procedure fails in SAS when you use the GUESSINGROWS=MAX option or a high value for the argument in the GUESSINGROWS= statement |
D9T040 |
| 64130 | The error "Internal error. Failed to get disked NAMESTR from hptgetdiskvarno" occurs when you access an SPD Engine data set |
D9T043 |
| 63624 | An unpaired quotation mark in a LIBNAME statement generates the message "Error: Buffer overrun occurred" |
D9T051 |
| 64651 | The error "The text expression length . . . exceeds maximum length" appears after using a %SUPERQ function and a text-string value greater than 32K |
D9T051 |
| 65288 | The metadata_setassn function does not successfully remove a user from a group even though the return code is 0 when you use the Chinese locale |
D9T060 |
| 65379 | Attempting to use a template generated by the Output Delivery System (ODS) might cause SAS® to crash |
D9T067 |
| 64543 | The message "ERROR: Recursive Segmentation Violations" appears in the SAS® log after you run code with incorrect syntax |
D9T082 |
| 65606 | Using a forward slash with the %SYSLPUT or %SYSRPUT statement in SAS® 9.4M5 causes existing code to fail with "Unrecognized option..." |
D9T082 |
| 65808 | The ODS HTML destination uses excessive memory when it is used with the TABULATE procedure |
D9T082 |
| 65983 | The LUA procedure contains an authorization-bypass vulnerability |
D9T082 |
| 65525 | Issues regarding ports occur when you try to use the SAS® FTP access method to communicate with applications like Box, Medidata, and Veeva |
D9T107 |
| 67060 | A SAS/SHARE® server unexpectedly terminates while accessing a metadata-bound library |
D9T115 |
| 67429 | Reading data input using the SYSIN card might cause a job to loop |
D9T122 |
| 67614 | Attempting to use an invalid user-defined format definition causes a SAS® program to error and close |
D9T124 |
| 67615 | A TEMPLATE procedure style template with long style names might generate a segmentation violation |
D9T124 |
| 67647 | Using PROC FORMAT with a large data set in a Linux operating environment causes an exception and a segmentation violation |
D9T126 |
| 67972 | An %IF statement in open code can insert additional semicolons in the code after the code is resolved |
D9T133 |
| 68170 | An emoji that is part of a character value is not read into a SAS® application correctly |
D9T140 |
| 68996 | The CVP engine fails on a z/OS system when you use a remote submit block of code in SAS® 9.4M3 (TS1M3) and later |
D9T142 |
| 70340 | The creation of very large log files in SAS® Studio could cause excessive and retained heap usage on SASServer2_1 |
D9T151 |
| 70494 | The IML procedure contains a security vulnerability when you specify a SUBMIT block |
D9T155 |
NOTE: If you install this hot fix and have Base SAS 9.4_M6 installed, for Windows and UNIX you must also install hot fix F1E012 and
for MVS you must also install hot fix D9T153.
You have Base SAS 9.4_M6 installed, you must also install hot fix
D9T104
D9T129
D9T123
D9T154
D9T062
D9T071
G2L009.
If you install this hot fix and have
SAS Threaded Kernel 9.4_M6 installed, you must also install hot fix E2G005.
SAS Threaded Kernel 9.4_M6 installed, you must also install hot fix F8C004.
SAS Threaded Kernel Message Passing Interface 2.82 installed, you must also install hot fix E8Y002.
SAS Threaded Kernel Extensions for FedSQL and DS2 Standalone 9.4_M6 installed, you must also install hot fix E5Q002.
SAS Threaded Kernel DS2 and FedSQL Language Processors 9.41_M4 installed, you must also install hot fix E9Y008.
SAS Threaded Kernel Components for Scalable Performance Data 9.41_M6 installed, you must also install hot fix F8U001.
SAS Threaded Kernel Drivers for Scalable Performance Data 5.3_M3 installed, you must also install hot fix F8T001.
SAS Threaded Kernel Core Routines 9.4_M6 installed, you must also install hot fix E3Q024. |
|
| F1E012 for Solaris for x64 |
| Base SAS 9.4_M6 |
| Issue(s) Addressed: | Introduced: |
| 63389 | Code that sets consecutive SYSTASK commands stops executing after about 6,481 consecutive attempts |
F1E001 |
| 63200 | Importing a CSV file with UTF-16LE encoding and TERMSTR=CRLF can result in data loss |
F1E001 |
| 63941 | The NOHPRUSERFILES option is available as a restricted option in SAS® High-Performance Risk 4.2 |
F1E001 |
| 63846 | CALL MODULE routines fail with the message "ERROR: Module module-name is not in whitelist..." when you use Kerberos Constrained Delegation |
F1E001 |
| 64028 | GRIDINSTALLLOC and GRIDRSHCOMMAND are now available as SAS® system options |
F1E001 |
| 64207 | A segmentation violation occurs after you submit SYSTASK and WAITFOR statements repeatedly within a macro loop |
F1E002 |
| 63143 | Windows Defender Credential Guard and SAS® Software |
F1E003 |
| 64580 | The SAS/SHARE® server might improperly validate user access to SAS® data sets |
F1E004 |
| 64979 | ALERT - An uninstallation of SAS® 9.4 using SAS® Deployment Manager fails with the error "A problem was encountered while uninstalling..." |
F1E005 |
| 65512 | Running a SYSTASK command results in an "Access is denied" message in the SAS® log |
F1E007 |
| 65680 | SAS/ACCESS® Interface to Oracle contains a remote code execution vulnerability |
F1E008 |
| 65825 | The error message "Connection to the server is lost" can appear in SAS® Enterprise Guide® when you are also using the ACTIVEX device driver |
F1E008 |
| 66101 | A warning might be issued for the ODS Measured RTF destination |
F1E009 |
| 66750 | The LINES or LINESTABLE option in the LSMEANS or SLICE statement in the PLM procedure might generate an error or reuse letters |
F1E009 |
| 69554 | The Select Portfolio Data window is unresponsive and returns "An HTTP error occurred (504 - error)" in SAS® Model Implementation Platform |
F1E011 |
| 70340 | The creation of very large log files in SAS® Studio could cause excessive and retained heap usage on SASServer2_1 |
F1E012 |
NOTE: If you install this hot fix, you must also install
hot fixes D9T155, D9T153, and G2L009 for Base SAS 9.4_M6,
hot fix E8Y002 for SAS Threaded Kernel Message Passing Interface 2.82,
hot fix I4X004 for SAS/STAT 15.1. |
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
| F4P007 for Solaris for x64 |
| Base SAS 9.4_M6 |
| Issue(s) Addressed: | Introduced: |
| 63143 | Windows Defender Credential Guard and SAS® Software |
F4P001 |
| 65051 | The error message ". . . Could not authenticate to the cluster" appears in the SAS® log when you use the GRDSVC_ENABLE function |
F4P002 |
| 66395 | Long user passwords that contain Unicode characters might fail to authenticate with PAM authentication |
F4P003 |
| 66696 | SAS® Workload Orchestrator crashes with a "double free or corruption (fasttop)" error message |
F4P004 |
| 69127 | Log4SAS ERROR messages might appear in the logs when you use Kerberos authentication |
F4P004 |
| 67441 | The PWENCODE procedure does not consider a blank space at the end of a password |
F4P005 |
| 67692 | SAS® Workload Orchestrator might unexpectedly stop running when you use Kerberos authentication |
F4P006 |
| 69741 | SAS® processes that use Kerberos credentials might experience a memory leak |
F4P007 |
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
| G2L009 for Solaris for x64 |
| Base SAS 9.4_M6 |
| Issue(s) Addressed: | Introduced: |
| 64363 | You modify the COLUMNS= option value to change from a multi-column format to a single-column format, but the column width is not correct in the output |
G2L001 |
| 64824 | The image that is specified with the PREIMAGE or POSTIMAGE style attribute appears in the wrong place in a PDF file |
G2L001 |
| 64847 | An ODS PDF statement with the CONTENTS=YES option creates graphs that overlap or are partially displayed |
G2L001 |
| 65214 | The error "The font 'font-name' contains a bad /BBox" appears in Adobe Acrobat Reader while opening a secured PDF created with the ODS PDF statement |
G2L001 |
| 56784 | Inline style overrides might affect spacing in the ODS PDF destination |
G2L001 |
| 64667 | You cannot click a URL link that is used with the LINK= option in TITLE and FOOTNOTE statements when it is included in PDF output from SAS/GRAPH® |
G2L001 |
| 64669 | PDF output that is created by SAS® might not print on certain printers |
G2L001 |
| 64453 | The ODS PDF destination with the REPORT procedure generates a premature page break when page orientation and page size toggle within the PDF |
G2L002 |
| 64809 | URL links that are created in a PostScript file generated by the ODS PRINTER destination are missing when the file is distilled to PDF |
G2L002 |
| 65403 | A "List items—Failed" error occurs in the accessibility checker in Adobe Acrobat regarding a tagged file that is created by the ODS PDF destination |
G2L002 |
| 65695 | You cannot print a PDF file in Adobe Acrobat Reader, and you see the message "An error occurred while printing the document" |
G2L003 |
| 65808 | The ODS HTML destination uses excessive memory when it is used with the TABULATE procedure |
G2L004 |
| 65961 | A screen reader does not read content correctly from a tagged PDF file that contains text that wraps in a table cell |
G2L005 |
| 66210 | A PROC FREQ table that exceeds one page in a tagged PDF file generates a segmentation violation |
G2L005 |
| 66425 | Links in tagged PDF files that are created by ODS PDF are not read correctly by screen readers or displayed correctly for visual consumers |
G2L005 |
| 66428 | A PDF file that is created by the SAS® Output Delivery System (ODS) on z/OS does not have a table of contents |
G2L005 |
| 66101 | A warning might be issued for the ODS Measured RTF destination |
G2L006 |
| 66496 | Titles and footnotes do not span the full width of a page when you use the COLUMNS= option with the TAGSETS.RTF_SAMPLE tagset |
G2L006 |
| 66926 | You see a segmentation violation in the SAS® log after you use the Tagsets.RTF ODS destination |
G2L007 |
| 67003 | ODS PDF creation with the BOOKMARKGEN and COMPRESS arguments seems to stop responding and uses high CPU resources |
G2L008 |
| 68045 | The Output Delivery System RTF destination might fail with insufficient memory on repeated executions |
G2L009 |
NOTE: If you install this hot fix, you must also install hot fix F1E012 for Base SAS 9.4_M6.
z/OS and z/OS 64-bit customers must install hot fix D9T153 instead of F1E012. |
|
| K1K002 for Solaris for x64 |
| Base SAS 9.4_M6 |
| Issue(s) Addressed: | Introduced: |
| 63143 | Windows Defender Credential Guard and SAS® Software |
K1K001 |
| 65013 | A grid sign-in attempt using pwd=_AUTHINFO_ fails in SAS® Viya® 3.5 |
K1K001 |
| 65144 | A security vulnerability occurs for SAS/CONNECT® server connections when the SASCLIENTPORT is recycled |
K1K001 |
| 66487 | Authentication to the CAS server fails with the error "Access denied..." when initiated on a SAS/CONNECT® server in a Microsoft Windows environment |
K1K001 |
| 67252 | A SAS/CONNECT® spawner using the NETENCRYPTALGORITHM=SSL option fails with "Resource temporarily unavailable..." after exhausting pthreads |
K1K001 |
| 63532 | You might encounter looping or an abend when you terminate a SAS® session |
K1K001 |
| 65040 | The SAS® Workload Orchestrator web interface dashboard intermittently displays an error message "Oops! An error has occurred. Please try again later" |
K1K001 |
| 66213 | Certificates that shipped in SAS® 9.4 contain an expired certificate from Sectigo AddTrust (expired on May 30, 2020) |
K1K001 |
| 69209 | Added support for the ICSFST2 internal call for AES encryption under z/OS |
K1K002 |
NOTE: If you install this hot fix to address the issue described in SAS Note 67252 for z/OS, you must also apply E8W003 for SAS/Secure SSL 9.41_M3.
If you install this hot fix to address the issue described in SAS Note 69209 for z/OS, you must also apply D9J003 for SAS/Secure 9.41_M3.
|
|
General Information about Hot Fixes