| The following fixes are included in the E9BX03 Bundle for SOLARIS 64BIT: | Introduced in BUNDLE: | ||
| E9BA02 | |||
| SN-017049 | Deleted observations can get added to new data set when migrating | E9BX01 | |
| E9BA03 | |||
| SN-017176 | JDBC connection to SAS/SHARE Server encounters transcoding error fornon-English locale | E9BX03 * | |
| E9BA09 | |||
| SN-017440 | SQRT function now supported in MDX code for SAS OLAP Server | E9BX01 | |
| E9BA12 | |||
| SN-017694 | Missing Output when specifying APPLEVEL parameter on IOM Serverdefinition in SAS Management Console or OBJECTSERVERPARMS SAS Option | E9BX01 | |
| E9BA17 | |||
| SN-012817 | Drill-through in MDDB Report Viewer fails with multiple filtered items | E9BX01 | |
| SN-017825 | Microsoft Security patch may cause errors with MDDB Report Viewer graphs | E9BX01 | |
| E9BA26 | |||
| SN-017800 | WHERE clause is not allowed with preset index | E9BX01 | |
| E9BA27 | |||
| SN-017801 | XMLSELECT with OMI_MATCH_CASE does not honor multiple attributes in asearch | E9BX01 | |
| E9BA30 | |||
| SN-017581 | ERROR: Invalid physical name for library XXXX is displayed when usingUpdate Table Metadata or PROC METALIB with concatenated libraries | E9BX01 | |
| SN-017580 | ERROR: This Library is already assigned or cannot be reassigned | E9BX01 | |
| SN-017849 | PROC METALIB fails to update an SPDS library table metadata with "Error:Invalid Option User." | E9BX01 | |
| E9BA32 | |||
| SN-017241 | "ERROR: System abend 0C4 occurred in module SASYHRE8 function YHRMHMR atoffset 000420" | E9BX01 | |
| E9BA37 | |||
| SN-017976 | Error about running out of space using PROC PRINT in certain situations | E9BX01 | |
| E9BA42 | |||
| SN-018019 | The default value for the FTEXT= graphics option with the Japanese orKorean install is incorrectly set | E9BX01 | |
| E9BA43 | |||
| SN-013603 | IRR and INTRR function may generate INVALID ARGUMENT message in SAS 9.1 | E9BX01 | |
| E9BA45 | |||
| SN-017208 | A long format length may cause a system error in PROC REPORT | E9BX01 | |
| SN-018200 | FLOW option on DEFINE statement may cause system error | E9BX01 | |
| E9BA57 | |||
| SN-018011 | SPECIFIED RESOURCE DOES NOT EXIST message with ENCODING=(W5|W6|W9)and SPDE engine | E9BX01 | |
| SN-018254 | MDX WHERE clause might return incorrect number of rows resulting in aperformance loss | E9BX01 | |
| SN-018911 | "ERROR: System Exiting Status=401" message occurs when multipleprocesses update a SPD Engine data set | E9BX01 | |
| E9BA70 | |||
| SN-018857 | WebDAV FILENAME needs additional functionality | E9BX01 | |
| E9BA72 | |||
| SN-018969 | Specifying an encoding for the _WEBOUT fileref does not work when yourun a stored process with the Stored Process Server | E9BX01 | |
| E9BA81 | |||
| SN-019166 | Possible memory-related failures when using the CATALOG access method | E9BX01 | |
| E9BA86 | |||
| SN-019227 | NOWARN option for PROC APPEND | E9BX01 | |
| E9BA92 | |||
| SN-017785 | Combo Box Control placed in an Extended Table object generates programhalt | E9BX01 | |
| SN-019176 | Models in SAS/AF software that support multiple interfaces onlyrecognize one interface | E9BX01 | |
| E9BA96 | |||
| SN-018202 | 'Cannot start remote process' or 'spawner prompt not found' errors mightoccur when connecting to a UNIX spawner program (sastcpd) | E9BX02 | |
| SN-019354 | An error occurs when you use SAS/CONNECT® software to sign on to a remote UNIX machine that is running a UNIX spawner program | E9BX01 | |
| E9BB08 | |||
| SN-019525 | Startup of elssrv may fail with 'ERROR: Cannot start thread supportservice' or 'ERROR: Communication error with launch server' on UNIX | E9BX02 | |
| E9BB11 | |||
| SN-019773 | Abend U1314 or traceback notes and messages attempting to read amigrated view from SAS® 8 | E9BX02 | |
| E9BB17 | |||
| SN-019231 | JAVAOBJ component object fails to free semaphores | E9BX02 | |
| SN-019812 | Values are quoted when DBCS value has same hex code as delimiter character | E9BX02 | |
| E9BB18 | |||
| SN-019486 | "ERROR: Invalid memptr" and SAS session hangs when trying to access aview via a libref with the META LIBNAME engine | E9BX02 | |
| E9BB23 | |||
| SN-020755 | SAS® Enterprise Guide® might generate memory leaks under UNIX | E9BX03 * | |
| E9BB50 | |||
| SN-020578 | PROC CIMPORT generates warning: "This transport file is from an earlierSAS release" | E9BX03 * | |
| SN-017841 | Extraneous characters appear for catalog entry descriptions when usingPROC CIMPORT | E9BX03 * | |
| SN-020673 | Using PROC CIMPORT in DBCS version of SAS may result in errors orgarbage characters if transport file contains data with indexes | E9BX03 * | |
| SN-020675 | Garbage characters may result when using PROC CIMPORT to import atransport file containing double-byte character set data | E9BX03 * | |
| E9BB61 | |||
| SN-019223 | New SASMSG function added to support internationalization | E9BX02 | |
| SN-019946 | SASMSG FUNCTION causes memory leaks | E9BX02 | |
| SN-021045 | The SASMSG function cannot differentiate traditional Chinese fromSimplified Chinese | E9BX03 * | |
| SN-021044 | The SASMSG function causes an access violation in batch mode when calledwith %SYSFUNC | E9BX03 * | |
| SN-021046 | An access violation might occur if the input data set is not created asexpected | E9BX03 * | |
| E9BB65 | |||
| SN-019742 | Attempting to connect to the SAS® Metadata Server when the METAUSER system option contains an embedded space generates an error | E9BX03 * | |
| E9BB66 | |||
| SN-021053 | The SAS® Stored Process Server and SAS® Workspace Server load balancing is not distributed across hosts with thelowest cost algorithm | E9BX03 * | |
| E9BB68 | |||
| SN-017410 | SAS OLAP Server process may crash if slicer contains infinite loop | E9BX01 | |
| SN-017408 | Permission condition memory is not released when OLAP session closed | E9BX01 | |
| SN-017409 | SAS OLAP Server performance enhancements available in SAS 9.1.3 ServicePack 4 | E9BX01 | |
| SN-018037 | PROC OLAP DEFINE statement can allow duplicate calculated members to becreated | E9BX01 | |
| SN-017931 | NUNIQUE values may be incorrect depending on the setting for "Maximumnumber of region execution threads" | E9BX01 | |
| SN-017445 | Listing active queries on SAS OLAP Server can cause server crash | E9BX01 | |
| SN-017523 | Selecting an OLAP Session in the OLAP Server monitor may cause SASManagement Console to hang | E9BX01 | |
| SN-018020 | SAS OLAP Server may error when empty data is passed to certain SASfunctions | E9BX01 | |
| SN-017871 | Drilldown may cause calculated member values to return from the SASOLAP Server as missing in Service Pack 4 | E9BX01 | |
| SN-018018 | Complex MDX query within a WITH expression may generate an AccessViolation | E9BX01 | |
| SN-018030 | SAS OLAP Server may abend with an OLS_NAMESPACEDELETE traceback | E9BX01 | |
| SN-017907 | OLAP cubes with deep hierarchies may return incorrect result sets | E9BX01 | |
| SN-018089 | Detailed SAS OLAP Server logging now outputs SAS OLAP Server optionsettings | E9BX01 | |
| SN-018012 | Threadpool options for the SAS OLAP Server are being overwritten | E9BX01 | |
| SN-018198 | TKASSERT error might be received when querying an OLAP cube on Z/OS | E9BX01 | |
| SN-017449 | NON EMPTY CROSSJOIN optimization in SAS OLAP Server | E9BX01 | |
| SN-018254 | MDX WHERE clause might return incorrect number of rows resulting in aperformance loss | E9BX01 | |
| SN-018701 | Session and Global calculated members might be dropped when using NonEmptyOptimization | E9BX01 | |
| SN-018580 | Disabling NonEmpty Crossjoin optimization does not have any effect | E9BX01 | |
| SN-018794 | DrillDownMemberTop function might cause crashes in the SAS® OLAP Server | E9BX01 | |
| SN-018702 | Global calculated members might cause crash in SAS OLAP Server withOptimization of Non Empty Crossjoins | E9BX01 | |
| SN-018795 | OLAP queries might return empty results if requesting missing values | E9BX01 | |
| SN-018796 | MDX iif functions that return null values might incorrectly returnempty result sets | E9BX01 | |
| SN-019048 | Calculated measures might be dropped from the OLAP result set when usingNon Empty Crossjoin Optimization | E9BX01 | |
| SN-019164 | Memory degradation or Access Violation could occur when querying an OLAPcube with Member Level Security applied | E9BX01 | |
| SN-018253 | DBCS drillthrough labels might not be rendered correctly | E9BX01 | |
| SN-019226 | Sorted OLAP queries might return incorrect results | E9BX01 | |
| SN-019314 | Use of global MDX String functions could halt the SAS OLAP Server | E9BX01 | |
| SN-019418 | AGGREGATE MDX function might cause slow query performance when memberlevel security is defined to the OLAP cube | E9BX01 | |
| SN-019725 | AGGREGATE functions using calculated members containing NUNIQUE measures might cause SAS® OLAP Server to crash | E9BX02 | |
| SN-019820 | NONEMPTYCROSSJOIN function might cause data loss in an OLAP Query | E9BX02 | |
| SN-020202 | Incorrect totals calculated when aggregate has members in same dimensionof the NUNIQUE measure being used | E9BX02 | |
| SN-020292 | SAS® OLAP Server performance might be worse after applying hotfix E9BA34 or later | E9BX02 | |
| SN-020291 | SAS® OLAP Server AGGREGATE function might return incorrect results on certain calculated members | E9BX02 | |
| SN-030537 | SAS MDX isEmpty function will not evaluate cells containing character data | E9BX03 * | |
| SN-020146 | Total calculations might be incorrect when an NUNIQUE measure is used | E9BX02 | |
| E9BB69 | |||
| SN-018812 | SAS Information Map might fail to open in SAS Enterprise Guide | E9BX01 | |
| SN-020496 | SAS Information Map Libname Engine might generate "ERROR: Write AccessViolation in Task" | E9BX03 * | |
| SN-020991 | SAS® Information Maps with more than 1000 data items might fail to open with the SAS Information Map Libname Engine (IMLE) | E9BX03 * | |
| E9BB73 | |||
| SN-017784 | Item in Verion 6 Legacy Radio Box might become unselectable on Linux | E9BX03 * | |
| SN-019976 | Delete key not working when maskCharacter attribute set for Text Entry Control | E9BX03 * | |
| E9BB74 | |||
| SN-017767 | Export and Import Wizards require Metadata Server fixes | E9BX01 | |
| SN-017743 | Login to SAS web application fails when using an email address as theuserid with LDAP authentication | E9BX01 | |
| SN-017761 | Jobs that are duplicated within a Project repository may lose theirconnection to Target objects | E9BX01 | |
| SN-017860 | BI Manager "Import" might cause metadata to be destroyed for all stored processes that contain parameters in SAS 9.1.3 Service Pack 4 | E9BX01 | |
| SN-017852 | External table objects may get inadvertently deleted from metadata whenimporting or exporting metadata multiple times | E9BX01 | |
| SN-017855 | Server code does not support exporting and importing from a metadata Project repository | E9BX01 | |
| SN-017857 | Exception may occur while exporting a block of objects from the DataIntegration Studio custom tree | E9BX01 | |
| SN-017854 | Incorrect behavior might occur when all items are not selected within apackage when performing a metadata import | E9BX01 | |
| SN-018452 | Unauthorized access to metadata server content | E9BX01 | |
| SN-030465 | Adding new records to a metadata repository after performing a metadata restore adds multiple metadata objects with the same internal ID value | E9BX03 * | |
| E9BB77 | |||
| SN-019947 | Writing a SAS® data set to a WebDAV library may fail | E9BX02 | |
| SN-020153 | "ERROR: An I/O error has occurred on file" when WebDAV server sends backan invalid or unexpected response | E9BX02 | |
| SN-030802 | A memory overwrite occurs when using WebDAV LIBNAME or FILENAME with hot fix E9BB30 applied | E9BX03 * | |
| E9BB78 | |||
| SN-015924 | DATETIMEw.d format can produce incorrect results | E9BX01 | |
| SN-030622 | Error generated when MDYAMPM format is used in a FOOTNOTE | E9BX03 * | |
| E9BB80 | |||
| SN-016428 | DBSLICEPARM creates incorrect syntax when DB2DECPT=, | E9BX01 | |
| SN-020687 | Support for Oracle TIMESTAMP data types added in SAS 9.1.3 | E9BX03 * | |
| SN-030942 | The WHERE clause strips trailing blanks from string literals that are concatenated with DBMS columns of type VARCHAR | E9BX03 * | |
| E9BB81 | |||
| SN-018463 | Access Violation or 0C4 abend in module SASSFM01 when using proceduresthat use multi-label formats | E9BX01 | |
| SN-020189 | Statistic labels in PROC TABULATE not displayed in uppercase in tableoutput | E9BX02 | |
| SN-020444 | Error in PROC TABULATE NLS versions after applying hot fix E9BB28 | E9BX02 | |
| SN-020359 | Variable labels that contain multi-byte character set strings do notsplit correctly | E9BX02 | |
| SN-030679 | Page dimension "and" in PROC TABULATE not displayed in uppercase in table output | E9BX03 * | |
| E9BB91 | |||
| SN-018909 | "ClassFormatError exception is thrown" Java runtime error when string constants contain umlaut characters | E9BX01 | |
| E9BB94 | |||
| SN-020378 | A segmentation violation might occur during execution of the DOWNLOADprocedure | E9BX03 * | |
| SN-031087 | A floating-point exception error might occur if you use the DOWNLOAD procedure to move a file that is larger than 2 GB | E9BX03 * | |
| E9BB95 | |||
| SN-017667 | Segmentation Violation in task [ DATASETS ] using DELETE statement | E9BX01 | |
| SN-017072 | Metadata server service might show starting state but never start | E9BX03 * | |
| SN-020233 | Increasing timeout value on UNIX may improve performance | E9BX02 | |
| SN-020274 | Grid sign-on fails to honor the TCPPORTFIRST and the TCPPORTLAST options | E9BX02 | |
| SN-020438 | Unix cleanwork utility does not remove UTILLOC directories | E9BX02 | |
| SN-019386 | SAS/CONNECT may issue "Segmentation Violation In Task [ Program ]" | E9BX03 * | |
| SN-020817 | Using the JOBNAME= option to specify a job name in the GRDSVC_ENABLE call routine | E9BX03 * | |
| SN-021112 | A SAS/CONNECT® software session might result in orphaned processes on a remote UNIX server | E9BX03 * | |
| E9BB96 | |||
| SN-017704 | An update to ensure proper authentication logging on to an IntegrationTechnology Server | E9BX01 | |
| SN-020384 | If your z/OS user ID begins with special characters, you cannot see pre-assigned libraries from SAS® Enterprise Guide® 4.1 | E9BX02 | |
| SN-020418 | "ACCESS DENIED" authentication error is not displayed as expected whenthe Metadata server using a Japanese version of Windows | E9BX02 | |
| SN-031165 | IOM messages are truncated in the SAS® Metadata Server log | E9BX03 * | |
| E9BB97 | |||
| SN-017915 | Memory leak in transcoding routine from MBCS to MBCS | E9BX03 * | |
| SN-019088 | KCVT function has problem handling trailing null character | E9BX01 | |
| SN-020676 | PROC CIMPORT may fail or generate errors when the file contains SBCSKatakana data | E9BX03 * | |
| SN-030987 | Performance problems occur in DBCS SAS® software when you use the RLINK or DLM= options in the FILENAME statement | E9BX03 * | |
| E9BB98 | |||
| SN-017745 | WHERE clause processing against an SQL view can cause Read Access orSegmentation Violations | E9BX01 | |
| SN-017962 | The first blank space in the name literal table names gets removed whenyou set the SYSLAST macro variable or _LAST_ system option | E9BX01 | |
| SN-017876 | Creating index may cause SAS to loop | E9BX01 | |
| SN-017981 | Incorrect output with WHERE and BY statements | E9BX01 | |
| SN-015813 | Read Access Violation in Task (CONNECT) caused by long comments | E9BX01 | |
| SN-018156 | Invoking an autocall macro which is stored as a SOURCE entry within acatalog may cause errors | E9BX01 | |
| SN-018305 | Garbage characters in SAS log when localized DBCS SAS is used withproducts related to the Workspace server | E9BX01 | |
| SN-018396 | Queries or WHERE clauses run against large data sets can causeSAS/SHARE server to hang | E9BX01 | |
| SN-019372 | Performance is poor in the SQL procedure when you use the COUNT(Distinctxxxx) function | E9BX02 | |
| SN-019601 | The option VALIDVARNAME=UPCASE is not working as expected | E9BX02 | |
| SN-019978 | Specifying LOGPARM system option may generate INSUFFICIENTAUTHORIZATION messages | E9BX02 | |
| SN-019984 | Output in the listing is truncated using the DBCS version of SAS | E9BX02 | |
| SN-019344 | SAS may ignore indexes during query on 64-Bit UNIX systems | E9BX02 | |
| SN-019578 | Update Flags from PROC SQL views are propagated by SAS procedures withOUT= option | E9BX02 | |
| SN-020208 | The ACCESS=READONLY option in the CATNAME statement is not workingcorrectly | E9BX02 | |
| SN-020562 | PROC APPEND step may damage BASE data set | E9BX02 | |
| SN-021003 | The LOGPARM path directive %v or #v might result in an unresponsiveprocesses | E9BX03 * | |
| SN-030428 | Aliased constant values become missing in outer joins and unions | E9BX03 * | |
| SN-030390 | Improvements are now available in relational database optimization via PROC SQL | E9BX03 * | |
| SN-019655 | Filter behavior inconsistent between SAS® Web Report Studio 3.1 and SAS® Information Map Studio | E9BX03 * | |
| SN-031300 | Poor performance occurs when you use views that consist of inner joins from DBMS tables | E9BX03 * | |
| E9BB99 | |||
| SN-017873 | Extra WHERE clause may get added to query passed to databases | E9BX01 | |
| SN-017888 | Segmentation Violation error issued when using PROC SQL and SAS/ACCESSwith a LENGTH= option larger than 32 | E9BX01 | |
| SN-018108 | Segmentation violation when executing multiple queries against a PROCSQL view containing a LIBNAME statement | E9BX01 | |
| SN-018176 | Import of table through Information Map Library Engine deletes physicaltable | E9BX01 | |
| SN-020479 | Batch jobs might end with a return code of 4 with no warning in the SASlog | E9BX03 * | |
| SN-018487 | Compress() function returns incorrect results when used on PROC SQLINSERT statement after applying SAS 9.1.3 Service Pack 4 | E9BX01 | |
| SN-016074 | "WARNING: At least one nonessential grouping column reference has beenremoved from a GROUP BY's reference list" | E9BX01 | |
| SN-019170 | Errors issued when integer references for column is used in a PROC SQLGROUP BY statement | E9BX01 | |
| SN-019372 | Performance is poor in the SQL procedure when you use the COUNT(Distinctxxxx) function | E9BX02 | |
| SN-019527 | Specifying the NOIPASSTHRU option in PROC SQL does not disable implicitpassthru | E9BX02 | |
| SN-016547 | Correlated subqueries using column aliases may not be passed to yourdbms when using SAS/ACCESS LIBNAME statement | E9BX02 | |
| SN-019930 | Using more than 36 tables in a UNION operation within an SQL proceduregenerates an error message | E9BX02 | |
| SN-020130 | Aliases columns or aliased tables in the SQL procedure blocks ImplicitPass-Through | E9BX03 * | |
| SN-030428 | Aliased constant values become missing in outer joins and unions | E9BX03 * | |
| SN-020116 | SAS/ACCESS® software fails to use table aliases correctly when you use in-line SELECT statements | E9BX03 * | |
| SN-020162 | Using functions without parameters in WHERE clauses can block ImplicitPass-Through | E9BX03 * | |
| SN-020126 | SAS/ACCESS® software now provides full support of the INNER JOIN syntax | E9BX03 * | |
| SN-020123 | Incorrect SQL text is generated when inner and left joins are used | E9BX03 * | |
| SN-020125 | Using implicit pass-through might cause an incorrect table referenceassignment | E9BX03 * | |
| SN-020129 | An incorrect Implicit Pass-Through query is generated when you use acombination of inner and outer Joins | E9BX03 * | |
| SN-020122 | Performance issues occur because SQL code is not passed to the database | E9BX03 * | |
| SN-030390 | Improvements are now available in relational database optimization via PROC SQL | E9BX03 * | |
| SN-019655 | Filter behavior inconsistent between SAS® Web Report Studio 3.1 and SAS® Information Map Studio | E9BX03 * | |
| SN-020635 | Incorrect textualization of SQL Implicit Pass-Through queries occurswhen you combine multiple inner joins with one or more outer joins | E9BX03 * | |
| SN-030942 | The WHERE clause strips trailing blanks from string literals that are concatenated with DBMS columns of type VARCHAR | E9BX03 * | |
| SN-030923 | Aliased summary functions in Base SAS® software are not passed to databases | E9BX03 * | |
| SN-030893 | Using an ORDER BY clause in the SQL procedure causes performance problems | E9BX03 * | |
| SN-031102 | A segmentation-violation error might occur after you apply Hot Fix E9BA83 and you access Oracle | E9BX03 * | |
| SN-031191 | Support is now available for the PROC SQL CREATE TABLE statement for the SAS® Scalable Performance Data Server® | E9BX03 * | |
| SN-031122 | SQLPLAN internal errors might occur when you select columns from an SQL view | E9BX03 * | |
| SN-031121 | Implicit Pass-Through errors occur when accessing Oracle tables | E9BX03 * | |
| SN-031291 | Errors occur in SAS® Scalable Performance Data Server® for numeric columns that are defined with the MISSING statement when it is used in WHERE processing | E9BX03 * | |
| SN-031211 | Errors occur in the SQL procedure's Implicit Pass-Through facility after you apply hot fixes E9BB72, E9BB76, and E9BB80 | E9BX03 * | |
| SN-031249 | SQLPLAN errors occur when you reference a calculated column on an SQL WHERE clause | E9BX03 * | |
| E9BC02 | |||
| SN-019115 | TRANWRD() function has different performance in SAS 6, and SAS 8 and SAS9.1.3 | E9BX01 | |
| SN-031391 | Transcoding problem occurs between SAS® Japanese encoding shift-jis and EUC | E9BX03 * | |
| E9BC05 | |||
| SN-017270 | Style not applied properly when sending ODS email | E9BX01 | |
| SN-017354 | SMTP email only uses the e-mail user ID (rather than the full e-mail address) for authentication | E9BX01 | |
| SN-007782 | Time stamp calculation when emailing from OS/390 | E9BX01 | |
| SN-019638 | Sending e-mail attachments using SMTP causes a read-access violation | E9BX02 | |
| SN-020323 | SAS® 9.1.3 and earlier SMTP e-mails do not timeout when block waiting for a response from a SMTP server | E9BX02 | |
| SN-018044 | Using SMTP e-mail with SAS® 9.1.3 (English version with DBCS and Unicode support) might cause truncated or missing e-mail output | E9BX03 * | |
| SN-031148 | Unable to authenticate e-mail on z/OS | E9BX03 * | |
| E9BX03 * | Indicates fixes that are appearing in a bundle for the first time. |
Back to the Main Hot Fix Downloads Page
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 tradema rks or trademarks of their respective companies.