| B25106 for Linux |
| Base SAS 9.21_M3 |
| Issue(s) Addressed: | Introduced: |
| 39517 | "Read Access Violation" or "Segmentation Violation" errors might be generated when creating ODS RTF output |
B25008 |
| 12601 | ODS PRINTER generates "out of memory" errors |
B25062 |
| 38109 | Justification, font, color, and height specifications do not replay to non-Listing ODS destinations when using PROC DOCUMENT |
B25062 |
| 40140 | URLs generated on the mainframe when you use the ODS HTML or the ODS TAGSETS.MVSHTML destination are incorrect in SAS® 9.2 |
B25062 |
| 41024 | Row headings might overwrite in PROC TABULATE output with ODS PRINTER (PCL/PDF/PS) destinations |
B25062 |
| 41445 | Memory issues might occur when more than 19 DEFINE statements contain style options in PROC REPORT |
B25062 |
| 42238 | Reports generated with SAS® Enterprise Guide or the SAS® Add-in for Microsoft Office with DBCS data might contain spaces in labels or cell values |
B25106 |
NOTE: If you install this hot fix, you must also install hot fixes B25183 and B25107 for Base SAS 9.21_M3.
|
|
| B25183 for Linux |
| Base SAS 9.21_M3 |
| Issue(s) Addressed: | Introduced: |
| 39807 | Global macro variable values and scope may be set incorrectly when PROC RISK is within a macro |
B25007 |
| 40220 | EFI, PROC IMPORT and IMPORT WIZARD read a quoted 4 digit number incorrectly |
B25007 |
| 40252 | R interface in Proc IML does not work on 64-bit Windows Operating Systems |
B25012 |
| 40382 | CALL SYMPUT may not update existing global macro variable |
B25023 |
| 40438 | Extremely wide data sets created on a 64-bit operating system produce incorrect or missing values on 32-bit operating systems |
B25026 |
| 40521 | SAS appears to hang in an endless loop if you use Cross Environment Data Access (CEDA) and select a large number of variables |
B25026 |
| 40449 | ANYDTDTE doesn't read a period value properly |
B25034 |
| 40737 | Calling user defined functions using %SYSFUNC can result in an error or termination of SAS |
B25036 |
| 41114 | WHERE clauses that reference functions will execute slowly in SCL code |
B25058 |
| 41119 | Multiple WHERE ALSO statements in the DATA Step returns incorrect results or errors |
B25058 |
| 39768 | Existing client connections to SAS Workspace Servers are closed when the SAS Object Spawner is stopped or refreshed. |
B25086 |
| 41651 | Grid test found exposure to segmentation violation |
B25086 |
| 42252 | ALERT - DATA step views are not accessible when you submit and pass them to a SAS grid from SAS® Enterprise Guide® |
B25086 |
| 31887 | Problems with macro variables Created in an AUTOEXEC.SAS file when executing SAS on a workspace server |
B25112 |
| 42925 | You cannot audit SAS® library Open objects in the standard SAS logging facility |
B25112 |
| 43537 | The last character of a double-byte character set variable is truncated when the variable length is 257 |
B25138 |
| 43671 | A memory leak may occur in SAS® Integration Technologies server processes. |
B25138 |
| 43967 | Indexes on data sets can become corrupt when run against the same data multiple times |
B25149 |
| 44190 | Unicode server performance is degraded when character literals in a WHERE clause are not passed to a database correctly |
B25158 |
| 39846 | Errors occur in a Foundation SAS® session when you try to connect with a SAS® Integration Technologies Server |
B25166 |
| 44674 | Referencing an autocall macro stored in a catalog causes a message window to appear upon exiting SAS |
B25170 |
| 45589 | An index might be ignored in BY processing after importing the indexed data set from transport format from another operating system |
B25183 |
NOTE: If you install this hot fix, you must also install hot fix B25202 for Base SAS 9.21_M3.
NOTE: SAS Integration Technologies customers must also install hot fix B25184 to fully implement the fix for the issue described in SN-39768.
NOTE: SAS Enterprise Guide customers must also install hot fix B99008 to fully implement the fix for the issue described in SN-42252. |
|
| B25184 for Linux |
| Base SAS 9.21_M3 |
| Issue(s) Addressed: | Introduced: |
| 38906 | The SAS metadata engine LIBNAME statement fails to interpret access password specification for the the Remote Engine Library server |
B25020 |
| 40125 | A slow response might occur when you connect to a SAS application server from client applications |
B25020 |
| 40366 | ALERT - The error "Libname _PMTA01_ is not assigned" occurs when you try to update metadata for a work table |
B25020 |
| 39371 | SAS® Stored Process Server might hang during shut down if the SAS Workspace Server is being monitored |
B25031 |
| 40920 | You are denied access to the SAS Workspace Server after you use SAS® Enterprise Guide® to connect to the SAS® Metadata Server |
B25039 |
| 39768 | Existing client connections to SAS Workspace Servers are closed when the SAS Object Spawner is stopped or refreshed. |
B25054 |
| 41542 | ALERT - SAS Object Spawner may crash when shutting down a SAS Pooled Workspace Server. |
B25054 |
| 41921 | ERROR: ORACLE connection error: ORA-01017: invalid username/password; logon denied. |
B25077 |
| 42178 | SAS Workspace server connections may fail when the SAS® Grid Manager load balancing algorithm is used. |
B25118 |
| 42746 | Performance degradation in the SAS 9.2 Pooled Workspace Server when querying SAS® Information Maps |
B25118 |
| 43110 | SAS® OLAP Server might stop responding when the number of connected clients is high |
B25121 |
| 43204 | The TIMEOUTSECONDS parameter might cause the SAS® OLAP Server to stop responding |
B25130 |
| 43690 | Library allocation messages are incorrectly reported at the WARN level instead of INFO |
B25140 |
| 43570 | If one of the peers in a load balanced cluster of 3 or more peers is refreshed or restarted it causes load balancing to behave incorrectly. |
B25142 |
| 45627 | Improved functionality to detect and shutdown orphaned SAS Workspace Server processes |
B25184 |
| 45661 | Load balanced SAS® OLAP Servers may abend and hang on shutdown |
B25184 |
NOTE: If you install this hot fix and need the fix documented in SAS Note 41921, you must also install Base SAS hot fix B25111.
If you install this hot fix and need the fix documented in SAS Note 43204, you must also install hot fix B25171 (z/OS only).
If you install this hot fix and need the fix documented in SAS Note 40125, you must also install Base SAS hot fix B25205.
If you install this hot fix and need the fix documented in SAS Note 39768, you must also install hot fix B25183. |
|
| B25195 for Linux |
| Base SAS 9.21_M3 |
| Issue(s) Addressed: | Introduced: |
| 39997 | A database error can occur when you submit an SQL query with a LIBNAME statement that uses the MULTI_DATASRC_OPT=IN_CLAUSE option |
B25028 |
| 41745 | Accessing DB2 can result in System abend 0C4 in module SASIODB2 |
B25066 |
| 41748 | Using the LIBNAME option MULTI_DATASRC_OPT=IN_CLAUSE can result in an error |
B25066 |
| 43275 | A CLI error occurs when you access DB2 via SAS/ACCESS® 9.2 Interface to ODBC and PROC SQL implicit pass-through processing |
B25117 |
| 45162 | ALERT - Slow performance and incorrect results might occur if you use DBCREATE_TABLE_OPTS to create a primary index for a Teradata table |
B25195 |
NOTE: If you install this hot fix, you should also install Base SAS 9.21_M3 hot fix B25202.
Customers running SAS/ACCESS Interface to DB2 9.21_M2 must also install hot fix B94015.
Customers running SAS/ACCESS Interface to Teradata 9.21_M2 must also install hot fix C71006.
Customers running SAS/ACCESS Interface to Teradata 9.21_M1 on Windows for x64 must also install hot fix D35005.
Customers running SAS/ACCESS Interface to Oracle 9.21_M2 must also install hot fix C36004. |
|
| B25202 for Linux |
| Base SAS 9.21_M3 |
| Issue(s) Addressed: | Introduced: |
| 39125 | An SQLPLAN error might occur when you use a new column variable in a correlated subquery |
B25021 |
| 39129 | Formatting a newly created, missing numeric variable might result in a "Format not found" error |
B25021 |
| 39304 | SQL views of DBMS tables may not return aliased column names |
B25021 |
| 39984 | An SQL procedure view does not return any rows when it is used in DATA step or a PRINT procedure |
B25021 |
| 40714 | SQL procedure queries might take longer to run in SAS® 9.2 TS2M2 and TS2M3 |
B25021 |
| 41875 | SAS/ACCESS® Interface to DB2 might produce incorrect results when left joining two or more DB2 tables |
B25053 |
| 41619 | Using PROC FORMAT in conjunction with PROC SQL to access a database gives different results between SAS® 9.1.3 and SAS® 9.2 |
B25060 |
| 41785 | Read Access Violation errors occur when creating a long macro variable with the PROC SQL / INTO: macro interface |
B25060 |
| 34687 | ALERT - Incorrect results might occur if you use the PUT() function in a WHERE clause to convert a DB2 timestamp to a character value |
B25083 |
| 38759 | An error can occur when you run a query against a DBMS and the query contains a column that is renamed and that is then used in a GROUP BY clause |
B25083 |
| 42093 | Using the PROC SQL BTRIM() function causes insufficient memory errors |
B25083 |
| 43970 | Errors occur when you use input() or put() in a JOIN operation with a database table in a remote library |
B25083 |
| 44688 | An INPUT() function used in PROC SQL might return incorrect results |
B25083 |
| 42425 | SQLPLAN error might occur when creating a new variable based on another new variable |
B25116 |
| 43021 | The SAS® System might not consider the DBKEY= data set option when you join a SAS data set and a DBMS table |
B25116 |
| 43262 | Queries that reference tables in libraries that are assigned using the META libname engine might perform poorly |
B25134 |
| 42737 | ALERT - Incorrect results occur in implicit pass-through when you use CALCULATED keyword on GROUP BY statement |
B25157 |
| 43787 | Performance is adversely affected by SQL queries that use unique indexes through SAS/SHARE® software |
B25157 |
| 44069 | Performance might be affected if your query joins multiple tables or views in which variables are being renamed |
B25157 |
| 44190 | Unicode server performance is degraded when character literals in a WHERE clause are not passed to a database correctly |
B25157 |
| 45162 | ALERT - Slow performance and incorrect results might occur if you use DBCREATE_TABLE_OPTS to create a primary index for a Teradata table |
B25196 |
| 45689 | The SAS® Stored Process Server might stop functioning properly if you cancel a request that is running PROC SQL code |
B25202 |
NOTE: If you install this hot fix, you should also install Base SAS 9.21_M3 hot fixes B25205, B25183, and B25195.
Customers running SAS/ACCESS Interface to Teradata 9.21_M2 must also install hot fix C71006.
Customers running SAS/ACCESS Interface to Teradata 9.21_M1 on Windows for x64 must also install hot fix D35005.
Customers running SAS/ACCESS Interface to Oracle 9.21_M2 must also install hot fix C36004. |
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
| B25205 for Linux |
| Base SAS 9.21_M3 |
| Issue(s) Addressed: | Introduced: |
| 38906 | The SAS metadata engine LIBNAME statement fails to interpret access password specification for the the Remote Engine Library server |
B25018 |
| 40125 | A slow response might occur when you connect to a SAS application server from client applications |
B25018 |
| 40231 | "ERROR: Libname _PMTA01_ is not assigned" occurs when running the METALIB procedure |
B25018 |
| 40366 | ALERT - The error "Libname _PMTA01_ is not assigned" occurs when you try to update metadata for a work table |
B25018 |
| 39550 | A Read access violation occurs when you use the METALIB procedure to import or register database tables into the SAS® Metadata Repository |
B25056 |
| 38707 | An error occurs when you add the DBSASTYPE= option to a database table in SAS® Management Console and you run a query that uses the metadata engine |
B25123 |
| 43224 | An error message appears in your SAS® log if you use the METALIB procedure to register or update a view that is defined in a Sybase database |
B25123 |
| 43262 | Queries that reference tables in libraries that are assigned using the META libname engine might perform poorly |
B25123 |
| 44153 | Libraries referenced in PROC METALIB or a META LIBNAME statement look for DBMS credentials in metadata even when Authentication Type is "NONE" |
B25159 |
| 44180 | "ERROR: Read Access Violation In Task [SQL]" might occur when using the META engine on a LIBNAME statement |
B25159 |
| 41093 | An error occurs and you cannot access an Oracle table when you use a schema name or a user ID that contains a dollar sign ($) |
B25205 |
| 46153 | The META libname engine ignores the Default Login associated with a relational database library |
B25205 |
| 46405 | META libname engine no longer reports column length inconsistencies when it should |
B25205 |
| 46408 | Access to third party database tables via the META libname engine fails when the userid contains special characters |
B25205 |
| NOTE: If you install this hot fix, you should also install Base SAS 9.21_M3 hot fixes B25184 and B25202. |
|
| B25206 for Linux |
| Base SAS 9.21_M3 |
| Issue(s) Addressed: | Introduced: |
| 40822 | Specifying the SAS® system option OPLIST may cause a segmentation violation error in the UNIX environment |
B25046 |
| 41013 | Errors might occur when you use the SASTRACE= system option with the SAS/ACCESS® engines |
B25046 |
| 41510 | Installation fails if hostname does not match SID file or if hostname is longer than 11 characters on Unix platforms |
B25061 |
| 41115 | Loading a large SAS data file into memory can cause macro slowdown |
B25078 |
| 41574 | Double-byte character sets (DBCS) might not display properly in the ARM log |
B25078 |
| 42240 | The LIBNAME statement's FILELOCKWAIT= option might not check for a lock in all cases |
B25078 |
| 42857 | Poor performance when reading non-local files with SAS® 9.2 on OpenVMS on HP Integrity |
B25109 |
| 43126 | CPU time limit set via ulimit -t is ignored |
B25124 |
| 43920 | Specifying the Albany AMT font when creating SAS/GRAPH® output can cause SAS® to fail |
B25148 |
| 39397 | Using SYSTASK statement to submit UNIX command causes error if SHELL= is specified |
B25161 |
| 44472 | Overwriting a SAS® data set in a UNIX operating environment removes any existing ACL |
B25165 |
| 44584 | SAS® Enterprise Guide® does not import UTF-16 files correctly using a UTF-8 SAS® server |
B25167 |
| 44729 | FULLSTIMER statistics for Memory usage are not correct when using SAS® Enterprise Guide to connect to a UNIX server |
B25167 |
| 45369 | "Utility file open failed" might appear when attempting to build a SAS® OLAP cube |
B25178 |
| 45507 | FILEEXIST causes an infinite loop on Unix if path equates to the root directory |
B25199 |
| 45225 | Installation with a sub-capacity license fails if hyper-threading has been enabled |
B25201 |
| 46251 | Directories cannot be created under the Files folder in SAS® Enterprise Guide® |
B25206 |
|
| B25207 for Linux |
| Base SAS 9.21_M3 |
| Issue(s) Addressed: | Introduced: |
| 39480 | Queries that contain the PROPERTIES function might return a formula error on some operating systems |
B25002 |
| 39955 | ALERT - VisualTotals and other calculated members might return unexpected values in OLAP-based reporting |
B25006 |
| 40077 | MDX to-date functions might return incorrect values when used with other calculated members |
B25006 |
| 40091 | AGGREGATE_TOTAL function in the SAS® OLAP Server can restrict access to members with unexpected results |
B25032 |
| 40549 | Optimization code might cause additional queries when accessing aggregation data |
B25032 |
| 40550 | VisualTotals with MDX functions using the .CURRENTMEMBER function can return unexpected results |
B25032 |
| 40551 | Performance issues might occur when using flattened results from MDX queries after appying hot fix B25006 |
B25032 |
| 41005 | Use of the NONEMPTYCROSSJOIN function and multiple-selection filters might result in missing rows |
B25063 |
| 41078 | Queries to SAS OLAP cubes that are built using ROLAP or external aggregations might perform slowly |
B25063 |
| 41175 | SECURITY_SUBSET not honored for totals after import of cube metadata |
B25063 |
| 41234 | The NonEmptyCrossjoin function might return incorrect results after applying hot fix B25032 |
B25063 |
| 41637 | Large memory usage might occur on Solaris machines when an invalid dimension name is used in the VisualTotals_Behavior property |
B25063 |
| 41642 | Multiple member filters on the hidden dimension or slicer axis might return incorrect results when totals are displayed on both rows and columns |
B25063 |
| 40911 | Do not use reserved words in dimension names when working with external aggregations |
B25103 |
| 41577 | Queries might perform slowly if ties are included when using TOPCOUNT |
B25103 |
| 41939 | Columns for categorical data that contain only missing values might be removed from the output of a flattened OLAP query |
B25103 |
| 42160 | Variables with more than 16777215 unique values cause a floating point exception in PROC OLAP |
B25103 |
| 37161 | SAS® OLAP Data Provider does not allow users to disable the "Include Hidden Items in totals" option in Microsoft Excel |
B25136 |
| 42406 | SAS® session might stop responding when using the DISABLE CUBES statement |
B25136 |
| 42827 | Drill-through to detail data for an OLAP cube might fail if UTF-8 encoding is used and member values contain non-English characters |
B25136 |
| 43542 | "The server encountered an error accessing a source data table" received when macro references exist in a member caption for a ROLAP cube |
B25136 |
| 43554 | PROC OLAPOPERATE and other administrative calls to the SAS® OLAP Server could cause the OLAP Server to fail |
B25136 |
| 43556 | Options NECJPERCENTTOTAL and NECJWHEREMAX have been added to the SAS® OLAP Server to help disable NONEMPTY CROSSJOIN optimization for dense data |
B25136 |
| 43557 | SQL range optimization is bypassed for data ordered by formatted values for a SAS® OLAP cube |
B25136 |
| 44260 | Continuous DISABLE CUBE operations might cause the SAS® OLAP Server to stop responding |
B25155 |
| 44267 | MDX ORDER function might generate a large number of subqueries |
B25155 |
| 44277 | Final subquery to satisfy a query against a SAS® OLAP cube might be unnecessary and impact performance |
B25155 |
| 44715 | Performance enhancement enables the underlying data source to calculate TOPCOUNT and BOTTOMCOUNT for an OLAP query |
B25168 |
| 44742 | General performance improvements for SAS® OLAP cubes are included with Hot Fix B25168 for the third maintenance release for SAS 9.2 (TS2M3) |
B25168 |
| 44751 | Poor performance when drilling to detail data from a SAS® OLAP cube |
B25168 |
| 42667 | Empty results from a non empty crossjoin query might result in slow performance from the SAS® OLAP Server |
B25192 |
| 45266 | Visual totals might be incorrect when single member on slicer and two hierarchies from the same dimension are on different axes |
B25192 |
| 45491 | "Error: Insufficient memory" might appear when very large sets are crossjoined and the maximum number of members is exceeded |
B25192 |
| 45608 | "Read Access Violation" using DATAPATH or INDEXPATH options creating SPDE library |
B25192 |
| 45633 | Read Access Violation might be generated for PROC OLAP when there are many levels in a dimension with multiple hierarchies |
B25192 |
| 46447 | The ORDER function might return incorrect results when the default measure is used in both the set and the numeric expression parameters |
B25207 |
| 46550 | The SAS® OLAP Server might stop responding after a client attempts to cancel a query that is running on the SAS OLAP Server |
B25207 |
|
| IMPORTANT: You must also install hot fixes B25169, B25176 and D28008 to fully implement the fixes for the issues addressed in this hot fix. |
Important changes to Hot Fixes!