A new update is available for SAS Scalable Performance Data Server , version 5.3 :
SAS Note 59376 | The message \"Error=Index needs to be repaired\" might occur during concurrent updates in a dynamic locking domain |
SAS Note 59432 | \"Segmentation Violation\" occurs when you use the DATE. format in SAS® Scalable Performance Data Server |
SAS Note 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 |
SAS Note 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 |
SAS Note 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 |
SAS Note 59621 | SAS® formats are mistaken as unknown user-defined formats by the SAS® Scalable Performance Data Server views |
SAS Note 59658 | SAS® Scalable Performance Data Server shared memory segments are not cleared after server shutdown |
SAS Note 59719 | Querying a SAS® Scalable Performance Data (SPD) Engine database for schema names with PROC FEDSQL or PROC DS2 does not return all schemas |
SAS Note 59724 | Querying SAS® Scalable Performance Data (SPD) Engine data with PROC FEDSQL or PROC DS2 does not return schemas if the schemas are lowercase |
This list of notes might be incomplete. For a complete list of issues addressed by this hot fix, visit the hot fix page for A3J001 |
Note: A comprehensive list of all SAS hot fixes is available from support.sas.com. You can use the SAS Hot Fix Analysis, Download, and Deployment (SASHFADD) tool to manage your SAS hot fixes.
Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 25. Read more here about why you should contribute and what is in it for you!