E9BD38 for Solaris for x64 |
Released: Aug 2010 |
Issue(s) Addressed: | Introduced: |
SN-017410 |
SASŪ OLAP Server process may crash if slicer contains infinite loop |
E9BA01 |
SN-017408 |
Permission condition memory is not released when OLAP session closed |
E9BA01 |
SN-017409 |
SASŪ OLAP Server performance enhancements available in SAS 9.1.3 Service Pack 4 |
E9BA01 |
SN-018037 |
PROC OLAP DEFINE statement can allow duplicate calculated members to be created |
E9BA34 |
SN-017931 |
NUNIQUE values may be incorrect depending on the setting for "Maximum number of region execution threads" |
E9BA34 |
SN-017445 |
Listing active queries on SASŪ OLAP Server can cause server crash |
E9BA34 |
SN-017523 |
Selecting an OLAP Session in the OLAP Server monitor may cause SASŪ Management Console to hang |
E9BA34 |
SN-018020 |
ALERT - SASŪ OLAP Server may error when empty data is passed to certain SASŪ functions |
E9BA34 |
SN-017871 |
ALERT - Drilldown may cause calculated member values to return from the SASŪ OLAP Server as missing in Service Pack 4 |
E9BA34 |
SN-018018 |
Complex MDX query within a WITH expression might generate an access violation |
E9BA34 |
SN-018030 |
SASŪ OLAP Server might abend with an OLS_NAMESPACEDELETE traceback |
E9BA34 |
SN-017907 |
ALERT - OLAP cubes with deep hierarchies may return incorrect result sets |
E9BA34 |
SN-018089 |
Detailed SASŪ OLAP Server logging now outputs SAS OLAP Server option settings |
E9BA34 |
SN-018012 |
Threadpool options for the SAS® OLAP Server are being overwritten |
E9BA34 |
SN-018198 |
TKASSERT error might be received when querying a SASŪ OLAP cube on z/OS |
E9BA34 |
SN-017449 |
NON EMPTY CROSSJOIN optimization in SASŪ OLAP Server |
E9BA47 |
SN-018254 |
MDX WHERE clause might return incorrect number of rows resulting in a performance loss |
E9BA56 |
SN-018701 |
ALERT - Session and Global calculated members might be dropped when using NonEmpty Optimization |
E9BA56 |
SN-018580 |
Disabling NonEmpty Crossjoin optimization does not have any effect |
E9BA56 |
SN-018794 |
ALERT - DrillDownMemberTop function might cause crashes in the SASŪ OLAP Server |
E9BA56 |
SN-018702 |
ALERT - Global calculated members might cause crash in SAS OLAP Server with Optimization of Non Empty Crossjoins |
E9BA56 |
SN-018795 |
ALERT - OLAP queries might return empty results if requesting missing values |
E9BA56 |
SN-018796 |
ALERT - MDX iif functions that return null values might incorrectly return empty result sets |
E9BA56 |
SN-019048 |
ALERT - Calculated measures might be dropped from the OLAP result set when using Non Empty Crossjoin Optimization |
E9BA56 |
SN-019164 |
Memory degradation or access violation could occur when querying a SAS® OLAP cube with member-level security applied |
E9BA84 |
SN-018253 |
DBCS drillthrough labels might not be rendered correctly |
E9BA89 |
SN-019226 |
ALERT - Sorted OLAP queries might return incorrect results |
E9BA89 |
SN-019314 |
Use of global MDX String functions could halt the SASŪ OLAP Server |
E9BA93 |
SN-019418 |
AGGREGATE MDX function might cause slow query performance when member-level security is defined to the OLAP cube |
E9BA99 |
SN-019725 |
AGGREGATE functions using calculated members containing NUNIQUE measures might cause SASŪ OLAP Server to crash |
E9BB07 |
SN-019820 |
ALERT - NONEMPTYCROSSJOIN function might cause data loss in an OLAP Query |
E9BB19 |
SN-020202 |
Incorrect totals calculated when aggregate has members in same dimension of the NUNIQUE measure being used |
E9BB33 |
SN-020292 |
SASŪ OLAP Server performance might be worse after applying hotfix E9BA34 or later |
E9BB38 |
SN-020291 |
ALERT - SASŪ OLAP Server AGGREGATE function might return incorrect results on certain calculated members |
E9BB38 |
SN-030537 |
SAS MDX isEmpty function will not evaluate cells containing character data |
E9BB68 |
SN-020146 |
ALERT - Total calculations might be incorrect when an NUNIQUE measure is used |
E9BB68 |
SN-013365 |
Drill-through and ROLAP aggregation tables can fail if the MDX query contains a numeric member |
E9BC15 |
SN-020028 |
Empty drillthrough result when format width for a column is too small |
E9BC15 |
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-038401 |
MDX queries using totals in SASŪ Web reports are not optimized by the SASŪ OLAP Server |
E9BD21 |
SN-038374 |
An error related to AVL trees might be returned by OLAP queries |
E9BD23 |
SN-038652 |
Performance problems might occur on SASŪ OLAP Servers that are running multiple requests |
E9BD24 |
SN-038708 |
"Internal server exception: access violation" and _pthread_body errors received during an OLAP query |
E9BD24 |
SN-040398 |
The SASŪ OLAP Server might fail on Microsoft Windows Server installations |
E9BD38 |
Install Instructions: E9BD38sx.txt |
Download: E9BD38 for
Solaris for x64   (File Size: 2.8M) |
ATTENTION: If you are running SAS Management Console 9.1.3 Service Pack 4, with Implementation-Version=9.1.20050622.20001, you must also download and install SAS Management Console hot fix 913SMC02 to address the issue described in SN-017449. The fix for the problem documented in this SAS Note will not be fully functional unless both E9BD38 and 913SMC02 are applied. You do not need to install 913SMC02 if you have any other Implementation-Version of SAS Management Console. ATTENTION: To fully implement the fix for SN-018254, you must also download and install SAS Base hot fix E9BC49. The fix for the problem documented in this SAS Note will not be fully functional unless both E9BD38 and E9BC49 are applied. |
E9SB09 for Solaris for x64 |
Released: Sep 2009 |
Issue(s) Addressed: | Introduced: |
SN-017567 |
Connection to Sybase not released when using PROC DBLOAD with the SAS/ACCESSŪ Interface to Sybase |
E9SB01 |
SN-018210 |
Incorrect amount of data may be returned when using SAS/ACCESSŪ Interface to Sybase with threads |
E9SB02 |
SN-017889 |
Notes, Warnings, or Errors not being issued when attempting to insert into a SYBASE table with triggers |
E9SB02 |
SN-018400 |
Different column Format is given when using ORDER BY and a date literal within a SELECT statement using the Sybase engine |
E9SB03 |
SN-018792 |
Text strings greater than 32767 are stored as a blank field when read into SASŪ with the DBMAX_TEXT option set |
E9SB04 |
SN-019240 |
Selecting a column that contains null values for autopartitioning when DBSLICEPARM=ALL might generate incorrect data |
E9SB04 |
SN-019099 |
SAS/ACCESSŪ Interface to Sybase with the bulkcopy feature may return a warning when an actual error was issued |
E9SB04 |
SN-019748 |
Incorrect results can occur when you use the DBSLICEPARM= option with SAS/ACCESSŪ Interface to Sybase |
E9SB05 |
SN-033901 |
An error occurs in releases of Sybase that support the data types Date and Time |
E9SB06 |
SN-033896 |
Performance degradation occurs when you run programs in SAS/ACCESSŪ Interface to Sybase after you have migrated from SASŪ 8.2 to SASŪ 9.1.3 |
E9SB06 |
SN-035927 |
ALERT - An error occurs when you append a SASŪ data set to Sybase table that has a VARCHAR column with a length greater than 255 |
E9SB08 |
SN-036626 |
ALERT - Incorrect dates are appended to the Sybase table when you use the APPEND procedure with the SASDATEFMT= and the BULKCOPY= options |
E9SB09 |
Install Instructions: E9SB09sx.txt |
( This Asian Language Support (DBCS) hot fix has post-installation requirements. Please review SN-038930 for more information. ) |
|
Download: E9SB09 for
Solaris for x64   (File Size: 737K) |