 |
||
|
||
|
||
|
Return to 9.1.3 DBCS Hot Fix Home | |
|
||
Hot Fix Information for Solaris (64-bit)
| Fixes NOT included in the BASE SAS Hot Fix Bundle: | Introduced: | |
| SN-021021 | ALERT - Some national characters in variable names might be converted to other characters when the options VALIDVARNAME=ANY and GETNAMES=YES | E9BB71 |
| SN-034254 | How to allow a numeric value enclosed in quotation marks to be read in as numeric variable with PROC IMPORT or the IMPORT WIZARD | E9BC12 |
| SN-033414 | An error occurs when you include the ENCODING option in the FILENAME statement | E9BC43 |
| SN-033995 | Error: "IOM call failed. Internal server exception: floating point divide by zero." | E9BC58 |
| SN-033984 | Poor performance occurs in client applications when the metadata environment contains a large number of repositories | E9BC59 |
| SN-034096 | Content is added to a parent repository, even when you do not have Check In Metadata permissions | E9BC59 |
| SN-034470 | Errors can be generated when using PROC SQL to generate XML files with the XML LIBNAME engine | E9BC65 |
| SN-034466 | Specifying an invalid width for informats in an XML Map can result in missing values in the data set | E9BC65 |
| SN-034280 | A "426 Connection closed; transfer aborted" message might appear in your SAS® log when using FTP to send a transport file that was created with CPORT | E9BC68 |
| SN-034913 | The SAS® Metadata Server stops responding if a long user ID or password is submitted for authentication | E9BC69 |
| SN-034915 | Submitting a blank user ID when logging in to the SAS® Metadata Server causes the server memory usage to increase suddenly | E9BC69 |
| SN-020299 | PROC PRINT may show missing columns in HTML, LISTING or RTF output | E9BA37 |
| SN-034756 | Column data might be blank using the List Data task in SAS® Enterprise Guide® | E9BC72 |
| SN-035147 | A variable is missing from PROC PRINT output when using ODS Listing or ODS HTML | E9BC72 |
| SN-017072 | Metadata server service might show starting state but never start | E9BA19 |
| SN-031719 | Some components from version 6 of SAS/AF® software might cause a read-access violation with repeated use | E9BC09 |
| SN-031795 | Dragging the cursor to an unselected item within the Radio Box control can unexpectedly update the internal value for the unselected item | E9BC09 |
| SN-019028 | Truncation errors might occur when using Unicode SAS with UTF-8 encoding to process 8-bit characters | E9BC18 |
| SN-019330 | Problems might occur when you invoke SAS® macros using Microsoft Object Linking and Embedding (OLE) automation submit method | E9BC18 |
| SN-032096 | ERROR "SAS Error Event: Error sending status, 1, to SCM. Error 6: The handle is invalid." occurs when stopping the SAS® Metadata Server | E9BC18 |
| SN-033403 | Segmentation violation and bridge stub errors on AIX | E9BC60 |
| SN-035477 | Invalid physical name error when a FILE statement contains certain Shift-JIS characters | E9BC76 |
| SN-035481 | Java DBCS encoding on Windows uses incorrect Japanese encoding resulting in garbage characters | E9BC76 |
| SN-035112 | ALERT - Invalid binary data when tranferring SAS data sets with PROC COPY or CPORT/CIMPORT. | E9BC81 |
| SN-036111 | Potential memory leak in SORT module causes Workspace server to fail | E9BC91 |
| SN-036205 | Basic and extended ISO informats and formats 9.2 functionality retrofitted back to 9.1.3 | E9BC95 |
| SN-036214 | Segmentation violation error in masked text entry box | E9BC96 |
| SN-036269 | Inconsistent transcoding using the KCVT function produces incorrect results in SAS® 9.2 | E9BC97 |
| SN-013122 | WZX: Invalid Conversion Map Specified | E9BC37 |
| SN-035807 | Observations might be missing after you use the UPLOAD procedure to transfer data sets | E9BC52 |
| SN-033576 | SAS® Enterprise Guide® does not detect when SAS data sets are created, updated, or deleted through a grid | E9BC52 |
| SN-036081 | The UPLOAD and DOWNLOAD procedures add null values to the ends of variables when you specify a SAS view with the DATA= data set option | E9BC98 |
| SN-036254 | SAS® 9.1.3 elssrv and jproxy processes not exiting correctly on Solaris zones | E9BD02 |
| SN-020652 | NON EMPTY CROSSJOIN optimization might drop members from result set | E9BC73 |
| SN-035621 | SAS® OLAP Server appears to hang and must be frequently restarted | E9BC88 |
| SN-033970 | NON EMPTY CROSSJOIN optimization might cause slower performance with secured data | E9BC92 |
| SN-036393 | ERROR: "An OLAP server thread has failed" occurs when a drill-through query returns no records | E9BD03 |
| SN-034840 | Running PROC METALIB on a DB2 libray and attempting to update a table that has a foreign key relationship with another table might cause an error | E9BC75 |
| SN-036544 | ERROR: "Libname lref not available for use" occurs when assigning a library using the META engine | E9BD05 |
| SN-036617 | SAS® might become unresponsive if the FILEDIALOG function is called from an SCL entry on Unix platforms | E9BD11 |
| SN-035779 | The LENGTH= column modifier is handled incorrectly when you use PROC SQL to create character columns in SAS® Scalable Performance Data Server® tables | E9BC32 |
| SN-034012 | Column aliases are not passed correctly to GROUP BY or ORDER BY clauses in the SAS® Scalable Performance Data Server® | E9BC32 |
| SN-034564 | The COUNT() or N() functions return incorrect results when used in a query containing a WHERE clause or a WHERE= data set option | E9BC46 |
| SN-035011 | A Read-access violation occurs in the SQL procedure when the WHERE= data set option is placed in an ORDER BY clause | E9BC46 |
| SN-033648 | ALERT - The implicit pass-through facility does not correctly switch argument order for the DB2 LOCATE() function when you pass the INDEX() function to DB2 | E9BC62 |
| SN-034993 | An error occurs when you run an SQL query with the ORACLE LIBNAME engine | E9BC62 |
| SN-034975 | Segmentation violations might occur after you apply Hot Fix E9BC46 in queries that reference DBMS tables | E9BC62 |
| SN-034391 | An SQLPLAN error might occur when you use a calculated field to subset a table | E9BC62 |
| SN-036280 | ALERT - The SQL procedure generates incorrect results when you copy a SAS® data set from one platform to another platform | E9BC94 |
| SN-033084 | An SQLPLAN internal error might occur when reference a variable from an in-line view that created the variable from a constant | E9BC94 |
| SN-034678 | An SQLPLAN error occurs when you submit a query with a CALCULATED column reference in a CASE expression that contains a GROUP BY clause | E9BC94 |
| SN-036177 | Incorrect results might occur when you run a PROC SQL join with an additional WHERE clause against Teradata tables | E9BC94 |
| SN-036202 | SQLPLAN internal errors might occur when you reference calculated columns in an SQL procedure | E9BC94 |
| SN-036748 | The MULTI_DATASRC_OPT= option is ignored when multiple WHERE clause predicates are used in an SQL join operation | E9BD08 |
| SN-034153 | Option DBIDIRECTEXEC prevents SAS® Enterprise Guide from opening tables created by PROC SQL | E9BD13 |
| SN-034234 | Incorrect results might occur if you use the LIBNAME statement option IP=YES with an SQL procedure that contains data calculations in a WHERE clause | E9BD13 |
| SN-016338 | Using PROC APPEND to insert rows into an Oracle table may report an error as a note | E9BC57 |
| SN-033648 | ALERT - The implicit pass-through facility does not correctly switch argument order for the DB2 LOCATE() function when you pass the INDEX() function to DB2 | E9BC63 |
| SN-035895 | An error occurred Executing the Workspace Job |
E9BC90 |
| SN-035991 | A generic IOM error occurs when executing a stored process that produces graphics output | E9BC90 |
| SN-036748 | The MULTI_DATASRC_OPT= option is ignored when multiple WHERE clause predicates are used in an SQL join operation | E9BD09 |
| SN-035879 | ALERT - Data imported from a DB2 library may be corrupt | E9BD14 |
| SN-033744 | An incorrect buffer break occurs when calling a macro from an EXECUTE statement that specifies a parameter with an "at" sign (@) in the parameter name | E9BC51 |
| SN-035492 | Could not find value or Record ID (RID) to do delete on index | E9BC85 |
| SN-035117 | ANYDTDTE informat incorrectly interprets invalid date value as a SAS date | E9BC86 |
| SN-035895 | An error occurred Executing the Workspace Job |
E9BC89 |
| SN-035991 | A generic IOM error occurs when executing a stored process that produces graphics output | E9BC89 |
| SN-034012 | Column aliases are not passed correctly to GROUP BY or ORDER BY clauses in the SAS® Scalable Performance Data Server® | E9BC93 |
| SN-036280 | ALERT - The SQL procedure generates incorrect results when you copy a SAS® data set from one platform to another platform | E9BC93 |
| SN-033084 | An SQLPLAN internal error might occur when reference a variable from an in-line view that created the variable from a constant | E9BC93 |
| SN-034678 | An SQLPLAN error occurs when you submit a query with a CALCULATED column reference in a CASE expression that contains a GROUP BY clause | E9BC93 |
| SN-036177 | Incorrect results might occur when you run a PROC SQL join with an additional WHERE clause against Teradata tables | E9BC93 |
| SN-036202 | SQLPLAN internal errors might occur when you reference calculated columns in an SQL procedure | E9BC93 |
| SN-036281 | PROC REPORT output generated by the CALL EXECUTE routine does not include text or variables generated by a COMPUTE block | E9BD01 |
| SN-034018 | MPRINT output generated twice when CALL EXECUTE is used within a macro | E9BD01 |
| SN-036070 | Extraneous code might be added if CALL EXECUTE is used to generate many ODS HTML statements | E9BD01 |
| SN-036592 | ALERT - DELETE statement sometimes does not remove qualifying observations | E9BD10 |
| SN-034234 | Incorrect results might occur if you use the LIBNAME statement option IP=YES with an SQL procedure that contains data calculations in a WHERE clause | E9BD15 |
| SN-037898 | Use of 2GB or more of memory by PROC TRANSPOSE can produce incorrect results | E9BD18 |
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.