| U88005 for 64-bit Enabled Solaris |
| SAS Scalable Performance Data Server 5.2 |
| Issue(s) Addressed: | Introduced: |
| 56146 | A PROC SQL query with SELECT DISTINCT returns a pass-through error on numeric variables that have a short length |
U88001 |
| 56166 | Poor performance might occur in a view table window when you open or close a large SAS® Scalable Performance Data Server table |
U88001 |
| 56167 | The error "WRAP_ERROR: WINIOWRAP open file limit 8192 exceeded" occurs when you process a large SAS® SPD Server table on a Windows platform |
U88001 |
| 56173 | WHERE constraints on SAS® Scalable Performance Data Server tables are removed when you use PROC SPDO with a TRUNCATE statement |
U88001 |
| 56175 | "ERROR: CONSTRAINT ADD did not complete, no WHERE clause received" might occur when you use WHERE constraints on SAS® SPD Server tables |
U88001 |
| 56193 | ALERT - The PRXCHANGE() function might return incorrect results in SAS® Scalable Performance Data Server |
U88001 |
| 56447 | "ERROR: Unable to init socket API" might occur when you use PROC SPDO with a LIST USERS/LOCKING statement |
U88001 |
| 56506 | SAS® Scalable Performance Data Server 5.2 cluster tables are not compatible with member tables from earlier SPD Server releases |
U88001 |
| 56508 | Altering a table column in SAS® Scalable Performance Data Server might result in existing indexes being dropped |
U88001 |
| 56509 | When you attempt to use the COALESCEC function with the SAS® Scalable Performance Data Server, SPDS errors might occur |
U88001 |
| 56510 | The SQL procedure CASE statement might return incorrect results when used with the SAS® Scalable Performance Data Server |
U88001 |
| 57587 | A segmentation violation occurs when you restore a SAS® Scalable Performance Data Server table that has a column width wider than 64 KB |
U88001 |
| 60491 | When you use SQL pass-through with SAS® Scalable Performance Data Server 5.1, the HADOOP table and macro options are ignored |
U88001 |
| 60492 | Using the TRIM or STRIP functions as input to another function might return incorrect results when used with SAS® Scalable Performance Data Server 5.1 |
U88001 |
| 60493 | Clustering SAS® Scalable Performance Data Server 5.2 tables with older tables causes "ERROR: Member table not compatible with other cluster member" |
U88001 |
| 56147 | SAS® Scalable Performance Data Server client incorrectly enables you to set both COMPRESS=YES and ENCRYPT=AES options when you create a table |
U88001 |
| 56177 | SAS® Scalable Performance Data Server disconnects and returns "ERROR: Error on server LIBNAME socket" |
U88001 |
| 57559 | A query on an indexed SPD Server table unexpectedly returns zero rows if the indexed column contains the same value for all rows |
U88002 |
| 57851 | Sporadic "Access Violation" errors might occur when you use the Parallel Join facility with the SAS® Scalable Performance Data Server |
U88002 |
| 57857 | The SPDSBKUP utility fails when you attempt to back up a compressed table that contains no columns |
U88002 |
| 57869 | ALERT - The COMPRESS function used with a K modifier returns incorrect results in SAS® Scalable Performance Data Server |
U88002 |
| 57992 | "Access Violation" errors might occur when multiple tables are joined with the UNION operator in SAS® Scalable Performance Data Server |
U88002 |
| 58209 | When used with the SPDO procedure, SPDSCMD commands incorrectly set the return code value |
U88002 |
| 58378 | "Access Violation" errors might occur when you use the STARJOIN optimization facility in SAS® Scalable Performance Data Server |
U88002 |
| 58388 | Submitting a WHERE clause that contains a LIKE operator might cause SAS® Scalable Performance Data Server to perform poorly |
U88002 |
| 58389 | Creating an index on a SAS® Scalable Performance Data Server table from which all rows have been deleted results in a corrupted index |
U88002 |
| 58413 | The SPDSCLEAN utility might fail to delete SAS® Scalable Performance Data Server log files |
U88002 |
| 58429 | Importing users in the SAS® Scalable Performance Data Server password database generates a core file on Red Hat Enterprise Linux 7.x systems |
U88002 |
| 58475 | The restore utility in SAS® Scalable Performance Data Server ends abruptly on Linux systems |
U88002 |
| 58477 | An invalid PROC SPDO command causes the SAS® Scalable Performance Data Server to crash |
U88002 |
| 58479 | A "Missing mandatory argument" error occurs when you try to execute the SAS® Scalable Performance Data Server performance monitor (spdsperf) |
U88002 |
| 58509 | The COALESCE function might return incorrect results when used with SAS® Scalable Performance Data Server |
U88002 |
| 58543 | TIMEOUT PERIOD and ALLOWED FAILURES fields might not retain their value when you import users in the SAS® SPD Server password database |
U88002 |
| 59259 | The SPDO procedure cluster list displays negative MINMAXVARLIST values as missing |
U88002 |
| 59260 | Querying SAS® Scalable Performance Data Server dictionary tables might result in server disconnect errors |
U88002 |
| 59261 | Starting the SAS® Scalable Performance Data Server with the LOG option causes the server to core dump |
U88002 |
| 60464 | SAS® Scalable Performance Data Server (spdsperf) fails to start if you specify -log at start-up |
U88002 |
| 58412 | The LOCALE value is displayed incorrectly in the SAS® Scalable Performance Data Server log |
U88002 |
| 59344 | Garbage characters appear in the audit log when you run SAS® Scalable Performance Data Server on a Solaris platform |
U88003 |
| 59356 | ALERT - Using a CASE WHEN clause with no ELSE clause generates incorrect results in SAS® Scalable Performance Data Server |
U88003 |
| 59376 | The message "Error=Index needs to be repaired" might occur during concurrent updates in a dynamic locking domain |
U88003 |
| 59394 | ALERT - Using a number to a power in a query might result in SAS® Scalable Performance Data Server disconnect errors |
U88003 |
| 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 |
U88003 |
| 59621 | SAS® formats are mistaken as unknown user-defined formats by the SAS® Scalable Performance Data Server views |
U88003 |
| 59625 | The message "ERROR: CONSTRAINT ADD did not complete" occurs when you use the GROUP keyword in the WHERE constraint |
U88003 |
| 59658 | SAS® Scalable Performance Data Server shared memory segments are not cleared after server shutdown |
U88003 |
| 60386 | Creating MINMAXVARLIST in a BACKUP=YES domain might corrupt the SAS® Scalable Performance Data Server cluster table |
U88003 |
| 60659 | Sporadic failures might occur during concurrent updates in dynamic locking domain |
U88003 |
| 61228 | SAS® Scalable Performance Data Server data partition files are written to the primary metadata path |
U88003 |
| 61231 | SAS® Scalable Performance Data Server cluster modification causes out-of-memory error |
U88003 |
| 61257 | Password shows in clear text when the PRINTLOG option is enabled in SAS® Scalable Performance Data Server |
U88003 |
| 62828 | ALERT - The Parallel Group-By facility produces an incorrect count for a composite index when the COUNT(distinct value) function is used |
U88003 |
| 63769 | Access Violation errors appear in the SAS® log after creating a wide SAS® Scalable Performance Data (SPD) Server table with the MINMAXVARLIST= option |
U88003 |
| 59432 | "Segmentation Violation" occurs when you use the DATE. format in SAS® Scalable Performance Data Server |
U88003 |
| 60092 | An unexpected warning about the ClusterList template is generated when you run SAS® Scalable Performance Data Server 5.3 |
U88003 |
| 64510 | Sporadic "Server has disconnected" errors might occur while reading a SAS® Scalable Performance Data (SPD) Server table |
U88004 |
| 65678 | A "Parse Failure" error message occurs in the SAS® log when you use a concatenated library with the SAS® Scalable Performance Data Server |
U88005 |
|
General Information about Hot Fixes