SAS Institute. The Power to Know
 
 
 

Base SAS 9.4_M5

Hot Fix Downloads for Solaris for x64

* General Information about Hot Fixes

B6Q001 was replaced by B6Q104

B6Q002 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
61386 A stored process fails and errors are generated when the STP procedure is executed remotely B6Q002
Released: November 17, 2017     Documentation: B6Q002sx.html       Download: B6Q002sx.zip  
Top ^

B6Q003 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
61515 When you use the Traditional Chinese edition of SAS®, using VIEWTABLE to open a SAS® data set fails with "ERROR: No such object..." B6Q003
Released: January 17, 2018     Documentation: B6Q003sx.html       Download: B6Q003sx.zip  
Top ^

B6Q004 was replaced by B6Q105

B6Q005 was replaced by B6Q016

B6Q006 was replaced by B6Q052

B6Q007 was replaced by B6Q105

B6Q008 was replaced by B6Q094

B6Q010 was replaced by B6Q089

B6Q011 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
61766 Background image attributes that are applied with a format are not applied in PROC REPORT output that is sent to ODS PDF B6Q011
61774 The ODS Report Writing Interface does not write text over a background image B6Q011
Released: February 14, 2018     Documentation: B6Q011sx.html       Download: B6Q011sx.zip  
Top ^

B6Q013 was replaced by B6Q052

B6Q014 was replaced by B6Q105

B6Q016 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
59920 Remote Library Services to a SAS/SHARE® or SAS/CONNECT® server fail with the “OPEN DATA SET…” message B6Q005
62109 Expanding the contents of a SAS/SHARE® library might take longer than two minutes B6Q016
Released: April 09, 2018     Documentation: B6Q016sx.html       Download: B6Q016sx.zip  
Top ^

B6Q017 was replaced by B6Q105

B6Q018 was replaced by B6Q086

B6Q020 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
62037 The MD5 and SHA256 functions produce an error when used with %SYSFUNC in SAS® 9.4 TS1M5 B6Q020
Released: May 16, 2018     Documentation: B6Q020sx.html       Download: B6Q020sx.zip  
Top ^

B6Q022 was replaced by B6Q067

B6Q023 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
62353 A segmentation violation error might occur when you use the OPENTIMES argument with the SCAPROC procedure through a REMOTE engine B6Q023
Released: May 24, 2018     Documentation: B6Q023sx.html       Download: B6Q023sx.zip  
Top ^

B6Q024 was replaced by B6Q092

B6Q025 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
62417 Spaces are replaced with semicolons in pathnames specified with the DATAPATH= option in LIBNAME statements defining SAS® SPD Engine libraries B6Q025
Released: July 05, 2018     Documentation: B6Q025sx.html       Download: B6Q025sx.zip  
Top ^

B6Q026 was replaced by B6Q105

B6Q027 was replaced by B6Q098

B6Q029 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
62622 The meta options are ignored in METADATA_* calls when you use the DOSUBL macro function B6Q029
Released: July 19, 2018     Documentation: B6Q029sx.html       Download: B6Q029sx.zip  
Top ^

B6Q030 was replaced by B6Q092

B6Q031 was replaced by B6Q105

B6Q034 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
62687 Emails might not be sent if values for the email parameters FROM= and SENDER= are invalid B6Q034
Released: August 09, 2018     Documentation: B6Q034sx.html       Download: B6Q034sx.zip  
Top ^

B6Q036 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
63045 PROC IMPORT with the DBMS=CSV option might not format dates correctly B6Q036
Released: November 16, 2018     Documentation: B6Q036sx.html       Download: B6Q036sx.zip  
Top ^

B6Q037 was replaced by B6Q104

B6Q038 was replaced by B6Q099

B6Q040 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
57881 When you use PROC SORT to sort encrypted data stored in a metadata-bound library, you receive "ERROR: Missing ENCRYPTKEY option on member..." B6Q040
Released: November 05, 2018     Documentation: B6Q040sx.html       Download: B6Q040sx.zip  
Top ^

B6Q041 was replaced by B6Q105

B6Q042 was replaced by B6Q052

B6Q043 was replaced by B6Q092

B6Q045 was replaced by B6Q098

B6Q046 was replaced by B6Q086

B6Q047 was replaced by B6Q105

B6Q048 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
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 B6Q048
NOTE: If you install this hot fix, you must also install hot fix B6Q099 for Base SAS 9.4_M5.
z/OS and z/OS 64-bit customers must install hot fix B6Q085 instead of hot fix B6Q048.
Released: January 02, 2019     Documentation: B6Q048sx.html       Download: B6Q048sx.zip  
Top ^

B6Q049 was replaced by B6Q105

B6Q050 was replaced by B6Q083

B6Q051 was replaced by B6Q104

B6Q052 for Solaris for x64
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.
Released: May 16, 2019     Documentation: B6Q052sx.html       Download: B6Q052sx.zip  
Top ^

B6Q053 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
63542 SAS® 8 clients are unable to connect to a SAS/SHARE® server that runs SAS®9 B6Q053
Released: January 24, 2019     Documentation: B6Q053sx.html       Download: B6Q053sx.zip  
Top ^

B6Q054 was replaced by B6Q105

B6Q055 was replaced by B6Q067

B6Q056 was replaced by B6Q098

B6Q057 was replaced by B6Q099

B6Q062 was replaced by B6Q088

B6Q063 was replaced by B6Q092

B6Q065 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
64117 You encounter error messages when you try to use the IMPORT procedure B6Q065
Released: May 21, 2019     Documentation: B6Q065sx.html       Download: B6Q065sx.zip  
Top ^

B6Q066 was replaced by B6Q105

B6Q067 for Solaris for x64
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.
Released: May 17, 2019     Documentation: B6Q067sx.html       Download: B6Q067sx.zip  
Top ^

B6Q068 was replaced by B6Q105

B6Q069 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
64175 Model packages are not created and the report.log file shows "ERROR: ARCHIVE transport engine encountered errors while publishing the package..." B6Q069
NOTE: If you install this hot fix and have Base SAS 9.4_M5 installed, you must also install hot fix B6Q105.
If you install this hot fix and have SAS Integration Technologies 9.4_M5 installed, you must also install hot fix D9I002.
Released: June 11, 2019     Documentation: B6Q069sx.html       Download: B6Q069sx.zip  
Top ^

B6Q070 was replaced by B6Q104

B6Q073 was replaced by B6Q098

B6Q074 was replaced by B6Q099

B6Q075 was replaced by B6Q105

B6Q076 was replaced by B6Q098

B6Q077 was replaced by B6Q105

B6Q079 was replaced by B6Q105

B6Q081 was replaced by B6Q105

B6Q083 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
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) B6Q050
64980 The PRINT procedure contains a buffer-overrun vulnerability B6Q083
NOTE: If you install this hot fix and need the fix documented in SAS Note 62515, you must also install hot fix B6Q105 for Base SAS 9.4_M5.
Released: October 18, 2019     Documentation: B6Q083sx.html       Download: B6Q083sx.zip  
Top ^

B6Q086 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
62319 Connections might become disconnected and return "ERROR: Conversations terminated..." when you use SAS/CONNECT® software B6Q018
63215 A segmentation violation occurs in a SAS/CONNECT® client session when you use the CONNECTKEEPALIVE environment variable B6Q046
65079 The SAS/SHARE® server stops responding and writes VQTCP messages to the server.log file B6Q086
Released: November 19, 2019     Documentation: B6Q086sx.html       Download: B6Q086sx.zip  
Top ^

B6Q088 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
63839 FILENAME FTP using TLS fails with an SSL/TLS error on the FTP data connection B6Q062
NOTE: If you install this hot fix, you must also install hot fix B6Q089 for Base SAS 9.4_M5.
Released: January 06, 2020     Documentation: B6Q088sx.html       Download: B6Q088sx.zip  
Top ^

B6Q089 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
61736 Viewtable Hide/Unhide window is blank and program halts for some Asian language SAS® images B6Q010
NOTE: If you install this hot fix, you must also install hot fix B6Q088 for Base SAS 9.4_M5.
Released: January 06, 2020     Documentation: B6Q089sx.html       Download: B6Q089sx.zip  
Top ^

B6Q090 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
65245 Read Access Violation errors or a warning occur when you route output to ODS destinations in a DBCS environment and a custom translation table is used B6Q090
Released: December 18, 2019     Documentation: B6Q090sx.html       Download: B6Q090sx.zip  
Top ^

B6Q091 was replaced by B6Q099

B6Q092 for Solaris for x64
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.
Released: May 19, 2020     Documentation: B6Q092sx.html       Download: B6Q092sx.zip  
Top ^

B6Q093 was replaced by B6Q105

B6Q094 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
61677 Specifying a 64-bit integer in PROC LUA can cause math exception errors B6Q008
65983 The LUA procedure contains an authorization-bypass vulnerability B6Q094
NOTE: If you install this hot fix and need the fix documented in SAS Note 65983, you must also install hot fix B6Q105 for Base SAS 9.4_M5 and C1S014 for SAS Threaded Kernel 9.4_M5.
Released: May 18, 2020     Documentation: B6Q094sx.html       Download: B6Q094sx.zip  
Top ^

B6Q096 was replaced by B6Q098

B6Q097 was replaced by B6Q105

B6Q098 for Solaris for x64
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.
Released: December 18, 2020     Documentation: B6Q098sx.html       Download: B6Q098sx.zip  
Top ^

B6Q099 for Solaris for x64
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.

Released: March 19, 2021     Documentation: B6Q099sx.html       Download: B6Q099sx.zip  
Top ^

B6Q100 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
67741 The SGRENDER procedure might produce incorrect X-axis labels B6Q100
Released: April 08, 2021     Documentation: B6Q100sx.html       Download: B6Q100sx.zip  
Top ^

B6Q101 was replaced by B6Q104

B6Q103 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
68045 The Output Delivery System RTF destination might fail with insufficient memory on repeated executions B6Q103
Released: June 24, 2021     Documentation: B6Q103sx.html       Download: B6Q103sx.zip  
Top ^

B6Q104 for Solaris for x64
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.
Released: October 29, 2021     Documentation: B6Q104sx.html       Download: B6Q104sx.zip  
Top ^

B6Q105 for Solaris for x64
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.
Released: March 15, 2023     Documentation: B6Q105sx.html       Download: B6Q105sx.zip  
Top ^

B8G001 was replaced by B8G002

B8G002 for Solaris for x64
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
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.
Top ^

C1R001 was replaced by C1R006

C1R002 was replaced by C1R006

C1R003 was replaced by C1R006

C1R005 was replaced by C1R006

C1R006 for Solaris for x64
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
Released: December 11, 2019     Documentation: C1R006sx.html       Download: C1R006sx.zip  
Top ^

C9V001 was replaced by C9V002

C9V002 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
62529 An HTTP procedure might fail when you use the AUTH_NEGOTIATE argument C9V001
63910 Segmentation violations occur when you create large tables in Apache Hadoop through an Apache Knox Gateway server C9V002
Released: April 09, 2019     Documentation: C9V002sx.html       Download: C9V002sx.zip  
Top ^

D2L001 was replaced by D2L004

D2L002 was replaced by D2L004

D2L003 was replaced by D2L004

D2L004 for Solaris for x64
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
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
Released: March 05, 2021     Documentation: D2L004sx.html D       Download: D2L004sx.zip  
D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment.
Top ^

E9U001 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
63973 An update provides support for the Reiwa era in NENGO and JNENGO formats and informats E9U001
Released: April 24, 2019     Documentation: E9U001sx.html       Download: E9U001sx.zip  
Top ^

G2J001 for Solaris for x64
Base SAS 9.4_M5
Issue(s) Addressed:Introduced:
61766 Background image attributes that are applied with a format are not applied in PROC REPORT output that is sent to ODS PDF G2J001
61774 The ODS Report Writing Interface does not write text over a background image G2J001
64824 The image that is specified with the PREIMAGE or POSTIMAGE style attribute appears in the wrong place in a PDF file G2J001
64847 An ODS PDF statement with the CONTENTS=YES option creates graphs that overlap or are partially displayed G2J001
Released: October 03, 2019     Documentation: G2J001sx.html       Download: G2J001sx.zip  
Top ^



PLEASE CAREFULLY READ THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT ("AGREEMENT") BEFORE DOWNLOADING MATERIALS FROM THIS SITE. BY DOWNLOADING ANY MATERIALS FROM THIS SITE, YOU ARE AGREEING TO THESE TERMS.
You are downloading software code ("Code") which will become part of a product ("Software") you currently have licensed from SAS Institute Inc. or one of its subsidiaries ("the Institute"). this Code is designed to either correct an error in the Software or to add functionality to the Software. The code is governed by the same agreement which governs the Software. If you do not have an existing agreement with the Institute governing the Software, you may not download the Code.
SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. ® indicates USA registration. Other brand and product names are registered trademarks or trademarks of their respective companies.
Copyright © SAS Institute Inc. All Rights Reserved.