Providing software solutions since 1976
Hot Fix Downloads
Important changes to Hot Fixes!
|A3J001 was replaced by A3J004|
|A3J002 was replaced by A3J004|
|A3J003 was replaced by A3J004|
|SAS Scalable Performance Data Server 5.3|
|59376||The message "Error=Index needs to be repaired" might occur during concurrent updates in a dynamic locking domain||A3J001|
|59614||"SPDS_ERROR" occurs when you try to create an AES-encrypted table using explicit SQL pass-through with SAS® Scalable Performance Data Server 5.3||A3J001|
|59617||Assigning a SAS® Scalable Performance Data Server 5.3 LIBNAME statement to a SAS® SPD 5.1 or earlier server causes a segmentation violation||A3J001|
|59620||"Unable to communicate with SPD Server" and other errors occur when you try to start SAS® Scalable Performance Data Server 5.3 as a secure server||A3J001|
|59621||SAS® formats are mistaken as unknown user-defined formats by the SAS® Scalable Performance Data Server views||A3J001|
|59658||SAS® Scalable Performance Data Server shared memory segments are not cleared after server shutdown||A3J001|
|63141||Port vulnerability scanning software causes SAS® Scalable Performance Data Server to fail with a segmentation violation||A3J001|
|63769||Access Violation errors appear in the SAS® log after creating a wide SAS® Scalable Performance Data (SPD) Server table with the MINMAXVARLIST= option||A3J001|
|59432||"Segmentation Violation" occurs when you use the DATE. format in SAS® Scalable Performance Data Server||A3J001|
|60735||SAS® Scalable Performance Data Server 5.3 connection string displays your password when tracing is enabled||A3J001|
|59719||Querying a SAS® Scalable Performance Data (SPD) Engine database for schema names with PROC FEDSQL or PROC DS2 does not return all schemas||A3J001|
|59724||Querying SAS® Scalable Performance Data (SPD) Engine data with PROC FEDSQL or PROC DS2 does not return schemas if the schemas are lowercase||A3J001|
|60386||Creating MINMAXVARLIST in a BACKUP=YES domain might corrupt the SAS® Scalable Performance Data Server cluster table||A3J002|
|60598||"Access Violation" errors might occur when you use multiple WHEN clauses in SAS® Scalable Performance Data Server||A3J002|
|60659||Sporadic failures might occur during concurrent updates in dynamic locking domain||A3J002|
|60691||"SPDS_ERROR: Out of memory" might occur when you query a SAS® Scalable Performance Data Server table that contains a large number of columns||A3J002|
|61230||Nested ABS functions cause SAS® Scalable Performance Data Server 5.3 to end abnormally||A3J002|
|61232||In, SAS® Scalable Performance Data Server, a generic ACL that matches the full name of the resource is not recognized||A3J002|
|61257||Password shows in clear text when the PRINTLOG option is enabled in SAS® Scalable Performance Data Server||A3J002|
|60668||Connection to SAS® Scalable Performance Data Server fails if the host name exceeds 32 characters||A3J002|
|60714||SAS® Scalable Performance Data Server fails to connect to a domain with "Connection does not exist...zdcrypt local buffer too small..."||A3J002|
|60715||SAS® Enterprise Guide® cannot display Latin5 characters that come from SAS® Federation Server||A3J002|
|60726||SAS® Federation Server Manager shows invalid characters for SAS® Scalable Performance Data Server data||A3J002|
|61228||SAS® Scalable Performance Data Server data partition files are written to the primary metadata path||A3J003|
|61231||SAS® Scalable Performance Data Server cluster modification causes out-of-memory error||A3J003|
|62713||A WHERE clause with a user-defined format causes a ". . . Libname path info not found . . ." error for SAS® Scalable Performance Data Server||A3J003|
|62828||ALERT - The Parallel Group-By facility produces an incorrect count for a composite index when the COUNT(distinct value) function is used||A3J003|
|60092||An unexpected warning about the ClusterList template is generated when you run SAS® Scalable Performance Data Server 5.3||A3J003|
|63770||A SAS® Scalable Performance Data (SPD) Server table name is truncated in a log to a maximum of eight characters||A3J004|
|62607||The SAS® Scalable Performance Data Server Password Manager Utility crashes on RHEL 7.x systems when the user name contains underscores||A3J004|
|NOTE: If you install this hot fix and have SAS Threaded Kernel Drivers for Scalable Performance Data 5.3_M1 installed, you must also install hot fix A4U002.|
If you install this hot fix and have SAS Federation Server 4.2 installed, you must also install hot fix Y46013.
If you install this hot fix and have SAS Drivers for Federation Server 4.2 installed, you must also install hot fix Z51002.
If you install this hot fix and have SAS Threaded Kernel 9.4_M4 installed, you must also install hot fix A5D001.
If you install this hot fix and have SAS Threaded Kernel 9.4_M3 installed, you must also install hot fix Y81004.
If you install this hot fix and have SAS Federation Server Manager Mid-Tier 4.2 installed, you must also install hot fix A1A004.
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 © 2019 SAS Institute Inc. All Rights Reserved.