| N49013 |
| SAS Scalable Performance Data Server 5.1 |
| Issue(s) Addressed: | Introduced: |
| 49239 | Parallel Group By facility produces incorrect results for MIN/MAX of short key variables in SAS® Scalable Performance Data Server® |
N49001 |
| 51473 | National Language Support for SAS® Scalable Performance Data Server® 5.1 and later |
N49001 |
| 51809 | ALERT - UPCASE() function might return incorrect results with national characters in SAS® Scalable Performance Data Server® |
N49001 |
| 51810 | Sporadic failures might occur during concurrent updates in dynamic locking domain |
N49001 |
| 51811 | SPDSWCST=NO macro variable might not be honored in explicit pass-through |
N49001 |
| 52697 | Using implicit pass-through with SAS® Scalable Performance Data Server might result in data-integrity issues for table records larger than 32K |
N49001 |
| 52700 | Using dynamic locking with concurrent updates or queries might result in errors |
N49001 |
| 53719 | ALERT - SAS® Scalable Performance Data Server might return inconsistent results when using implicit pass-through |
N49001 |
| 53721 | SAS® Scalable Performance Data Server WHERE clause with a direct comparison might return incorrect rows |
N49001 |
| 55403 | Creating concurrent user-defined formats with SAS® Scalable Performance Data Server might result in missing or corrupted formats |
N49001 |
| 55500 | A segmentation fault occurs when you use the SPDO procedure with SAS® Scalable Performance Data Server 5.1 |
N49001 |
| 56477 | A parallel merge join fails and returns "Run function returned error: Operation aborted by software" |
N49001 |
| 56490 | "ERROR: Specified locking user does not exist" might occur when you use PROC SPDO SET USER/LOCKING |
N49001 |
| 60482 | In SAS® Scalable Performance Data Server, using a group-by operation with an inner join causes incorrect results |
N49001 |
| 60489 | A "Write failed" error and a disk-full condition occur when you perform a SORT procedure in SAS® Scalable Performance Data Server |
N49001 |
| 51823 | &SYSRC macro variable returns a value of 0 when PROC SPDO SPDSCMD fails |
N49001 |
| 60485 | Performing concurrent updates of a table in a stored process server causes SAS® Scalable Performance Data Server to stop responding |
N49001 |
| 57657 | When you use the SAS® Management Console plug-in for SAS® SPD Server 5.1 to connect to older SPD Server releases, an SPDSSERV connection error occurs |
N49001 |
| 59494 | Using the SAS® SPD Server plug-in for SAS® Management Console 5.1 to connect to an earlier server release results in "SPDSSERV- Error on connection" |
N49001 |
| 53724 | The STARJOIN optimization facility in SAS® Scalable Performance Data Server might cause a "Broken pipe" error |
N49002 |
| 53725 | Querying the SAS® Scalable Performance Data Server 5.1 DICTIONARY tables returns corrupt results |
N49002 |
| 53731 | Client session might appear unresponsive after executing a PROC SPDO step that includes a "LIST USERS;" statement |
N49002 |
| 53732 | ALERT - A PROC SQL query might return incorrect results in dynamic locking domain in SAS® Scalable Performance Data Server |
N49002 |
| 53734 | When you use PROC SQL to insert or append rows to a table, SAS® Scalable Performance Data Server might fail |
N49002 |
| 55406 | ALERT - The COALESCE function might return incorrect results when used with SAS® Scalable Performance Data Server 5.1 |
N49002 |
| 55412 | User-defined format connection logging might display an incorrect SAS® Scalable Performance Data Server username and group information |
N49002 |
| 57658 | Running concurrent tasks against SAS® Scalable Performance Data Server 5.1 tables might fail and generate subsystem errors |
N49002 |
| 55499 | Spaces in SAS® Scalable Performance Data Server domain definitions might return the error "Parse Error Lib=XXX: token=ROPTIONS" |
N49006 |
| 54300 | The error "Segmentation Violation in Task [FSEDIT]" might occur when multiple users edit the same SPD Server table and the option LOCKING=YES is used |
N49006 |
| 55469 | "SPDS_ERROR: Parse Failure" occurs when you use the INPUT function in SQL pass-through |
N49006 |
| 55670 | The &SYSERR macro variable returns a value of 0 when you use the DATASETS procedure with a DELETE statement to delete a SAS® SPD Server table |
N49006 |
| 56146 | A PROC SQL query with SELECT DISTINCT returns a pass-through error on numeric variables that have a short length |
N49007 |
| 56166 | Poor performance might occur in a view table window when you open or close a large SAS® Scalable Performance Data Server table |
N49007 |
| 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 |
N49007 |
| 56173 | WHERE constraints on SAS® Scalable Performance Data Server tables are removed when you use PROC SPDO with a TRUNCATE statement |
N49007 |
| 56175 | "ERROR: CONSTRAINT ADD did not complete, no WHERE clause received" might occur when you use WHERE constraints on SAS® SPD Server tables |
N49007 |
| 56193 | ALERT - The PRXCHANGE() function might return incorrect results in SAS® Scalable Performance Data Server |
N49007 |
| 56447 | "ERROR: Unable to init socket API" might occur when you use PROC SPDO with a LIST USERS/LOCKING statement |
N49007 |
| 56508 | Altering a table column in SAS® Scalable Performance Data Server might result in existing indexes being dropped |
N49007 |
| 56509 | When you attempt to use the COALESCEC function with the SAS® Scalable Performance Data Server, SPDS errors might occur |
N49007 |
| 56510 | The SQL procedure CASE statement might return incorrect results when used with the SAS® Scalable Performance Data Server |
N49007 |
| 56147 | SAS® Scalable Performance Data Server client incorrectly enables you to set both COMPRESS=YES and ENCRYPT=AES options when you create a table |
N49007 |
| 56177 | SAS® Scalable Performance Data Server disconnects and returns "ERROR: Error on server LIBNAME socket" |
N49007 |
| 43913 | Port vulnerability scanning software might cause SAS® Scalable Performance Data Server to fail |
N49008 |
| 57587 | A segmentation violation occurs when you restore a SAS® Scalable Performance Data Server table that has a column width wider than 64 KB |
N49008 |
| 57559 | A query on an indexed SPD Server table unexpectedly returns zero rows if the indexed column contains the same value for all rows |
N49009 |
| 57851 | Sporadic "Access Violation" errors might occur when you use the Parallel Join facility with the SAS® Scalable Performance Data Server |
N49009 |
| 57857 | The SPDSBKUP utility fails when you attempt to back up a compressed table that contains no columns |
N49009 |
| 57869 | ALERT - The COMPRESS function used with a K modifier returns incorrect results in SAS® Scalable Performance Data Server |
N49009 |
| 57992 | "Access Violation" errors might occur when multiple tables are joined with the UNION operator in SAS® Scalable Performance Data Server |
N49009 |
| 58475 | The restore utility in SAS® Scalable Performance Data Server ends abruptly on Linux systems |
N49009 |
| 58389 | Creating an index on a SAS® Scalable Performance Data Server table from which all rows have been deleted results in a corrupted index |
N49010 |
| 58477 | An invalid PROC SPDO command causes the SAS® Scalable Performance Data Server to crash |
N49010 |
| 58509 | The COALESCE function might return incorrect results when used with SAS® Scalable Performance Data Server |
N49010 |
| 59344 | Garbage characters appear in the audit log when you run SAS® Scalable Performance Data Server on a Solaris platform |
N49010 |
| 59356 | ALERT - Using a CASE WHEN clause with no ELSE clause generates incorrect results in SAS® Scalable Performance Data Server |
N49010 |
| 59376 | The message "Error=Index needs to be repaired" might occur during concurrent updates in a dynamic locking domain |
N49010 |
| 59394 | ALERT - Using a number to a power in a query might result in SAS® Scalable Performance Data Server disconnect errors |
N49010 |
| 59621 | SAS® formats are mistaken as unknown user-defined formats by the SAS® Scalable Performance Data Server views |
N49010 |
| 59625 | The message "ERROR: CONSTRAINT ADD did not complete" occurs when you use the GROUP keyword in the WHERE constraint |
N49010 |
| 58412 | The LOCALE value is displayed incorrectly in the SAS® Scalable Performance Data Server log |
N49010 |
| 59214 | A segmentation violation might occur when you use the FSEDIT or STB procedure to open an SQL view |
N49010 |
| 59432 | "Segmentation Violation" occurs when you use the DATE. format in SAS® Scalable Performance Data Server |
N49010 |
| 59259 | The SPDO procedure cluster list displays negative MINMAXVARLIST values as missing |
N49011 |
| 60386 | Creating MINMAXVARLIST in a BACKUP=YES domain might corrupt the SAS® Scalable Performance Data Server cluster table |
N49011 |
| 61231 | SAS® Scalable Performance Data Server cluster modification causes out-of-memory error |
N49011 |
| 61257 | Password shows in clear text when the PRINTLOG option is enabled in SAS® Scalable Performance Data Server |
N49011 |
| 62828 | ALERT - The Parallel Group-By facility produces an incorrect count for a composite index when the COUNT(distinct value) function is used |
N49012 |
| 52786 | SAS® Scalable Performance Data Server® plug-in does not allow connection to SPD Server on Windows if the server is configured for LDAP authentication |
N49013 |
| 52787 | SAS® Scalable Performance Data Server® might become unresponsive when performing update on tables with indexes |
N49013 |
| 55669 | The CONTENTS procedure might fail when you access a large SAS® SPD Server table that contains column ACLs |
N49013 |
| 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 |
N49013 |
| 58209 | When used with the SPDO procedure, SPDSCMD commands incorrectly set the return code value |
N49013 |
| 63769 | Access Violation errors appear in the SAS® log after creating a wide SAS® Scalable Performance Data (SPD) Server table with the MINMAXVARLIST= option |
N49013 |
| 63891 | Copying a large SAS® Scalable Performance Data Server 5.1 table with indexes using PROC COPY can corrupt the table |
N49013 |
|
|
General Information about Hot Fixes