| E9BC59 for Solaris 64bit |
| Released: Dec 2008 |
| Issue(s) Addressed: | Introduced: |
| SN-017767 |
Export and Import Wizards require Metadata Server fixes |
E9BA20 |
| SN-017743 |
Login to SAS® web application fails when using an email address as the userid with LDAP authentication |
E9BA20 |
| SN-017761 |
ALERT - Jobs that are duplicated within a Project repository may lose their connection to Target objects |
E9BA20 |
| SN-017860 |
ALERT - BI Manager "Import" might cause metadata to be destroyed for all stored processes that contain parameters in SAS 9.1.3 Service Pack 4 |
E9BA20 |
| SN-017852 |
ALERT - External table objects may get inadvertently deleted from metadata when importing or exporting metadata multiple times |
E9BA20 |
| SN-017855 |
ALERT - Server code does not support exporting and importing from a metadata Project repository |
E9BA20 |
| SN-017857 |
Exception may occur while exporting a block of objects from the Data Integration Studio custom tree |
E9BA20 |
| SN-017854 |
ALERT - Incorrect behavior might occur when all items are not selected within a package when performing a metadata import |
E9BA20 |
| SN-018452 |
ALERT - Unauthorized access to metadata server content |
E9BA54 |
| SN-030465 |
ALERT - Adding new records to a metadata repository after performing a metadata restore adds multiple metadata objects with the same internal ID value |
E9BB74 |
| SN-031345 |
Metadata objects stored in a custom repository are not returned by client applications or metadata query results when they should be |
E9BC03 |
| 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 |
| Install Instructions: E9BC59s6.txt |
IMPORTANT!
You must have SAS 9.1.3 Service Pack 4
installed on your system before installing E9BC59.
Download: E9BC59 for
Solaris 64bit (File Size: 2.6M) |
| E9BC76 for Solaris 64bit |
| Released: Apr 2009 |
| Issue(s) Addressed: | Introduced: |
| SN-017667 |
ALERT - Segmentation Violation in task [ DATASETS ] using DELETE statement |
E9BA13 |
| SN-017072 |
Metadata server service might show starting state but never start |
E9BA19 |
| SN-020233 |
Increasing timeout value on UNIX may improve performance |
E9BB32 |
| SN-020274 |
Grid sign-on fails to honor the TCPPORTFIRST and the TCPPORTLAST options |
E9BB36 |
| SN-020438 |
Unix cleanwork utility does not remove UTILLOC directories |
E9BB45 |
| SN-019386 |
SAS/CONNECT may issue "Segmentation Violation In Task [ Program ]" |
E9BB58 |
| SN-020817 |
Using the JOBNAME= option to specify a job name in the GRDSVC_ENABLE call routine |
E9BB58 |
| SN-021112 |
A SAS/CONNECT® software session might result in orphaned processes on a remote UNIX server |
E9BB75 |
| 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-031400 |
Resetting system time backwards causes negative "real time" value in STIMER output |
E9BC09 |
| SN-019028 |
Truncation errors might occur when using Unicode SAS with UTF-8 encoding to process 8-bit characters |
E9BC18 |
| SN-032113 |
The $EBCDIC format/informat generates incorrect results if ENCODING=UTF8 is set |
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-032521 |
ALERT - A Multi-Processing (MP) CONNECT session might not respond in UNIX environments |
E9BC18 |
| SN-032547 |
Data sets written to tape in SAS® 8.2 are not readable in SAS 9.1.3 |
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 |
| Install Instructions: E9BC76s6.txt |
IMPORTANT!
You must have SAS 9.1.3 Service Pack 4
installed on your system before installing E9BC76.
Download: E9BC76 for
Solaris 64bit (File Size: 5.8M) |
ATTENTION (1): To obtain the complete fix for SN-020817 and SN-019386 you must also download and install SAS/CONNECT hot fix E9CT05. The issues described in SN-020817 and SN-019386 will not be fully fixed until both E9BC76 and E9CT05 are applied.
ATTENTION (2): To obtain the complete fix for SN-021112 you must also download and install SAS/ACCESS Interface to DB2 hot fix E9D214. The issue described in SN-021112 will not be fully fixed until both E9BC76 and E9D214. are applied. "ATTENTION (2)" is not applicable to z/OS sites. |
| E9BD03 for Solaris 64bit |
| Released: Jul 2009 |
| 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 |
| Install Instructions: E9BD03s6.txt |
IMPORTANT!
You must have SAS 9.1.3 Service Pack 4
installed on your system before installing E9BD03.
Download: E9BD03 for
Solaris 64bit (File Size: 3.2M) |
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 E9BD03 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 E9BD03 and E9BC49 are applied. |
| E9BD13 for Solaris 64bit |
| Released: Oct 2009 |
| Issue(s) Addressed: | Introduced: |
| SN-017873 |
ALERT - Extra WHERE clause may get added to query passed to databases |
E9BA31 |
| SN-017888 |
Segmentation Violation error issued when using PROC SQL and SAS/ACCESS® with a LENGTH= option larger than 32 |
E9BA31 |
| SN-018108 |
Segmentation violation when executing multiple queries against a PROC SQL view containing a LIBNAME statement |
E9BA44 |
| SN-018176 |
ALERT - Import of table through Information Map Library Engine deletes physical table |
E9BA48 |
| SN-020479 |
Batch jobs might end with a return code of 4 with no warning in the SAS® log |
E9BA53 |
| SN-018487 |
Compress() function returns incorrect results when used on PROC SQL INSERT statement after applying SAS® 9.1.3 Service Pack 4 |
E9BA53 |
| SN-016074 |
"WARNING: At least one nonessential grouping column reference has been removed from a GROUP BY's reference list" |
E9BA53 |
| SN-019170 |
Errors issued when integer references for column is used in a PROC SQL GROUP BY statement |
E9BA83 |
| SN-019372 |
Performance is poor in the SQL procedure when you use the COUNT(Distinct xxxx) function |
E9BB04 |
| SN-019527 |
Specifying the NOIPASSTHRU option in PROC SQL does not disable implicit passthru |
E9BB04 |
| SN-016547 |
Correlated subqueries using column aliases may not be passed to your dbms when using SAS/ACCESS LIBNAME statement |
E9BB10 |
| SN-019930 |
Using more than 36 tables in a UNION operation within an SQL procedure generates an error message |
E9BB26 |
| SN-020130 |
Aliases columns or aliased tables in the SQL procedure blocks Implicit Pass-Through |
E9BB29 |
| SN-030428 |
Aliased constant values become missing in outer joins and unions |
E9BB29 |
| SN-020162 |
Using functions without parameters in WHERE clauses can block Implicit Pass-Through |
E9BB29 |
| SN-020126 |
SAS/ACCESS® software now provides full support of the INNER JOIN syntax |
E9BB29 |
| SN-020116 |
SAS/ACCESS® software fails to use table aliases correctly when you use in-line SELECT statements |
E9BB29 |
| SN-020123 |
Incorrect SQL text is generated when inner and left joins are used |
E9BB29 |
| SN-020125 |
Using implicit pass-through might cause an incorrect table reference assignment |
E9BB29 |
| SN-020129 |
An incorrect Implicit Pass-Through query is generated when you use a combination of inner and outer Joins |
E9BB29 |
| SN-020122 |
Performance issues occur because SQL code is not passed to the database |
E9BB29 |
| SN-030390 |
Improvements are now available in relational database optimization via the SQL procedure |
E9BB70 |
| SN-019655 |
Filter behavior inconsistent between SAS® Web Report Studio 3.1 and SAS® Information Map Studio |
E9BB70 |
| SN-020635 |
Incorrect textualization of SQL Implicit Pass-Through queries occurs when you combine multiple inner joins with one or more outer joins |
E9BB70 |
| SN-032085 |
Incorrect SQL optimization may produce incorrect results |
E9BB76 |
| SN-030942 |
The WHERE clause strips trailing blanks from string literals that are concatenated with DBMS columns of type VARCHAR |
E9BB76 |
| SN-030923 |
Aliased summary functions in Base SAS® software are not passed to databases |
E9BB76 |
| SN-030893 |
Using an ORDER BY clause in the SQL procedure causes performance problems |
E9BB76 |
| SN-031102 |
A segmentation-violation error might occur after you apply Hot Fix E9BA83 and you access Oracle |
E9BB76 |
| SN-031191 |
Support is now available for the PROC SQL CREATE TABLE statement for the SAS® Scalable Performance Data Server® |
E9BB93 |
| SN-031122 |
SQLPLAN internal errors might occur when you select columns from an SQL view |
E9BB93 |
| SN-031121 |
Implicit Pass-Through errors occur when accessing Oracle tables |
E9BB93 |
| 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 |
E9BB99 |
| SN-031211 |
Errors occur in the SQL procedure's Implicit Pass-Through facility after you apply hot fixes E9BB72, E9BB76, and E9BB80 |
E9BB99 |
| SN-031249 |
SQLPLAN errors occur when you reference a calculated column on an SQL WHERE clause |
E9BB99 |
| SN-031905 |
Enhancements to the Implicit SQL Pass-Through facility enable more of a query to be passed to a database |
E9BC11 |
| SN-031863 |
ALERT - Using the EQT operator in the SQL procedure incorrectly classifies rows with missing values as a match |
E9BC11 |
| SN-031564 |
Performance problems occur when you use the CASE expression with DBMS tables |
E9BC11 |
| SN-031825 |
After applying hot fixes E9BB98 and E9BB99, column aliases are passed to the SQL GROUP BY clause in place of the corresponding real column names |
E9BC11 |
| SN-033763 |
Using the CALCULATED keyword in a WHERE clause in a PROC SQL inner join generates a cartesian product |
E9BC25 |
| SN-033649 |
Calculations that involve DBMS datetime values can return incorrect results |
E9BC25 |
| SN-033073 |
Using the CALCULATED keyword in a WHERE clause generates a Carteisan product |
E9BC25 |
| SN-032636 |
A Read-access violation might be generated after you apply hot fixes E9BB80, E9BB98, and E9BB99 |
E9BC25 |
| SN-032537 |
ALERT - Incorrect query results might be generated after you apply hot fixes E9BB80, E9BB98, and E9BB99 or you run SAS® 9.2 |
E9BC25 |
| SN-032925 |
An error occurs when you use the IDXNAME= and the WHERE= data set options in an SQL procedure query |
E9BC32 |
| SN-032472 |
Concatenating libraries can result in Read-access violations in the SQL procedure |
E9BC32 |
| SN-032545 |
An SQLPLAN error might occur after you apply hot fixes E9BB98 and E9BB99 |
E9BC32 |
| SN-032406 |
Outer joins that contain a WHERE clause with the STRIP() and PUT() functions cause abnormal endings |
E9BC32 |
| 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-032542 |
An error message incorrectly appears when you use the IDXNAME= and the WHERE= option data set options together in an SQL procedure |
E9BC32 |
| SN-011210 |
Incorrect results from PROC SQL using WHERE= option with indexed tables |
E9BC46 |
| 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-033094 |
ALERT - Incorrect results might be generated when you use the LIBNAME statement to join multiple Oracle tables |
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 |
| Install Instructions: E9BD13s6.txt |
IMPORTANT!
You must have SAS 9.1.3 Service Pack 4
installed on your system before installing E9BD13.
Download: E9BD13 for
Solaris 64bit (File Size: 1.6M) |
ATTENTION (1): E9BD13 for Windows is also available for the following languages:
German, Spanish, French, Italian, Japanese, Polish, Simplified Chinese
ATTENTION (2): Customers running SAS Base SQL must also download and install SAS Base hot fixes E9BD14 and E9BD15.
Download E9BD14
Download E9BD14 for SAS with Asian Language Support (DBCS) Download E9BD15
Download E9BD15 for SAS with Asian Language Support (DBCS) |
| E9BD15 for Solaris 64bit |
| Released: Oct 2009 |
| Issue(s) Addressed: | Introduced: |
| SN-017745 |
WHERE clause processing against an SQL view can cause Read Access or Segmentation Violations |
E9BA28 |
| SN-031607 |
Using the BY statement with the formatted ODS destinations can generate incorrect output |
E9BA36 |
| SN-017962 |
The first blank space in the name literal table names gets removed when you set the SYSLAST macro variable or _LAST_ system option |
E9BA36 |
| SN-017876 |
Creating index may cause SAS® to loop |
E9BA36 |
| SN-017981 |
ALERT - Incorrect output with WHERE and BY statements |
E9BA36 |
| SN-015813 |
Read Access Violation in Task (CONNECT) caused by long comments |
E9BA50 |
| SN-018156 |
Invoking an autocall macro which is stored as a SOURCE entry within a catalog may cause errors |
E9BA50 |
| SN-018305 |
Garbage characters in SAS log when localized DBCS SAS is used with products related to the Workspace server |
E9BA50 |
| SN-018396 |
Queries or WHERE clauses run against large data sets can cause SAS/SHARE® server to hang |
E9BA50 |
| SN-019372 |
Performance is poor in the SQL procedure when you use the COUNT(Distinct xxxx) function |
E9BB02 |
| SN-019601 |
The option VALIDVARNAME=UPCASE is not working as expected |
E9BB02 |
| SN-019978 |
Specifying LOGPARM system option may generate INSUFFICIENT AUTHORIZATION messages |
E9BB13 |
| SN-019984 |
Output in the listing is truncated using the DBCS version of SAS |
E9BB13 |
| SN-019344 |
SAS® may ignore indexes during query on 64-Bit UNIX systems |
E9BB13 |
| SN-019578 |
Update Flags from PROC SQL views are propagated by SAS® procedures with OUT= option |
E9BB13 |
| SN-020208 |
The ACCESS=READONLY option in the CATNAME statement is not working correctly |
E9BB35 |
| SN-020562 |
PROC APPEND step may damage BASE data set |
E9BB52 |
| SN-021003 |
Using the %v or #v LOGPARM path directive might cause the workspace server to fail to start and processes to stop responding |
E9BB63 |
| SN-030390 |
Improvements are now available in relational database optimization via the SQL procedure |
E9BB72 |
| SN-030428 |
Aliased constant values become missing in outer joins and unions |
E9BB72 |
| SN-019655 |
Filter behavior inconsistent between SAS® Web Report Studio 3.1 and SAS® Information Map Studio |
E9BB72 |
| SN-031300 |
Poor performance occurs when you use views that consist of inner joins from DBMS tables |
E9BB98 |
| SN-032375 |
Errors might occur reading XML files using the XML engine with very long strings |
E9BC16 |
| 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 . The server is disconnected might occur if you run a job in SAS® Enterprise Guide® |
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 |
| Install Instructions: E9BD15s6.txt |
IMPORTANT!
You must have SAS 9.1.3 Service Pack 4
installed on your system before installing E9BD15.
Download: E9BD15 for
Solaris 64bit (File Size: 3.3M) |
ATTENTION (1): To complete the installation of this hot fix, you must also download and install SAS Base hot fixes E9BD13 and E9BD14.
Download E9BD13
Download E9BD13 for SAS with Asian Language Support (DBCS) Download E9BD14
Download E9BD14 for SAS with Asian Language Support (DBCS) This hot fix will NOT be fully functional without E9BD13 and E9BD14 applied.
ATTENTION (2): For additional configuration instructions for improving relational database optimization, see Problem Note SN-030390 above. |
| E9HP05 for Solaris 64bit |
| Released: May 2009 |
| Issue(s) Addressed: | Introduced: |
| SN-032597 |
An OUTSTAT= data set is not created when fitting an over-parameterized IDM model in HPFENGINE |
E9HP03 |
| SN-032617 |
RETAINCHOOSE option in PROC HPFDIAGNOSE changes to RETAINCHOOSE=TRUE|YES|FALSE|NO |
E9HP03 |
| SN-032495 |
Running Forecast Server 2.1 on AIX can trigger an Exception Error when running HPFDIAGNOSE using outlier detection |
E9HP03 |
| SN-034221 |
ERROR: Read Access Violation in Task [HPFENGINE] when log transformation is used |
E9HP04 |
| SN-033975 |
Post-adjustments are not applied to forecasts when an Exponential Smoothing Model (ESM) is used |
E9HP04 |
| SN-033780 |
ALERT - INCORRECT STANDARD ERROR IN DEMANDS TABLE WHEN BACK= IS USED |
E9HP04 |
| SN-033779 |
A Read Access Violation might occur and processing will stop generating output from PROC HPFENGINE when ODS Graphics code is used. |
E9HP04 |
| SN-034218 |
ERROR: "Floating Point Zero Divide" may occur when analyzing nearly constant data |
E9HP04 |
| SN-033529 |
HPFENGINE options TASK=FIT | UPDATE | FORECAST do not persist when MINOBS= conditon is used to generate a _MEAN_ forecast. |
E9HP04 |
| SN-033818 |
The NOALTLIST option is ignored on the PROC HPFENGINE statement if the TASK= option is different than TASK=SELECT. |
E9HP04 |
| SN-034164 |
Invalid Operation error may occur if selected ARIMA model produces a perfect fit |
E9HP04 |
| SN-035207 |
The SAS session might stall when running PROC HPFDIAGNOSE with a near constant response |
E9HP05 |
| Install Instructions: E9HP05s6.txt |
IMPORTANT!
You must have SAS 9.1.3 Service Pack 4
installed on your system before installing E9HP05.
Download: E9HP05 for
Solaris 64bit (File Size: 5.0M) |
| ATTENTION: This hot fix should be applied ONLY to SAS High-Performance Forecasting 2.3. This hot fix should NOT be applied to SAS High-Performance Forecasting 2.2 or to any other release of SAS High-Performance Forecasting. |
| E9OD07 for Solaris 64bit |
| Released: May 2009 |
| Issue(s) Addressed: | Introduced: |
| SN-018348 |
"Data truncated" warning issued using SAS/ACCESS® Interface to ODBC to access Informix data |
E9OD01 |
| SN-017463 |
Incorrect length assigned to character variables using SAS/ACCESS® Interface to ODBC and SAS 9.1.3 SP4 |
E9OD01 |
| SN-018476 |
READBUFF setting not honored with certain SQL queries against a SAS/ACCESS® Interface to ODBC libref |
E9OD02 |
| SN-018538 |
"Error: DIAG[42000] [HP ODBC driver] ERROR [4118] The cursor query expression is not updatable. (-4118) when using HP ODBC driver SQL" |
E9OD02 |
| SN-018988 |
Netezza support for remote external tables interface for SAS/ACCESS® Interface to ODBC |
E9OD03 |
| SN-018990 |
Incorrect data inserted into DB2 column defined as "CHAR() FOR BIT DATA" |
E9OD03 |
| SN-018991 |
ALERT - Bulkloading into Microsoft SQL Server can lead to loss of precision |
E9OD03 |
| SN-019988 |
PROC DBLOAD fails to insert the correct number of rows when you use SAS/ACCESS® Interface to ODBC |
E9OD04 |
| SN-019994 |
SAS/ACCESS® Interface to ODBC has been enhanced to use the new DB2 API interface for bulk loading and importing data to DB2 |
E9OD04 |
| SN-019990 |
A floating-point exception error can occur when you use SAS® Data Integration Studio 3.4 to update table metadata in the SAS/ACCESS® Interface to ODBC |
E9OD04 |
| SN-019995 |
Accessing SYBASE IQ tables with SAS/ACCESS® Interface to ODBC appears to freeze or is extremely slow |
E9OD04 |
| SN-019970 |
SAS/ACCESS® Interface to ODBC does not properly set the SYSDBRC and SYSDBMSG automatic macro variables when a Netezza load fails |
E9OD04 |
| SN-032370 |
DBLOAD procedure does not write non-English characters to Microsoft SQL Server Unicode Field |
E9OD05 |
| SN-016094 |
Invalid characters might display when use SAS/ACCESS® Interface to ODBC to connect a SAS Unicode server to a Unicode database |
E9OD05 |
| SN-033733 |
The LIBNAME statement’s QUALIFIER= option is not honored in subsequent PROC SQL SELECT statements that include the DISTINCT option and that are run against the same libref |
E9OD06 |
| SN-035182 |
The QUALIFIER= option is ignored when you use DISTINCT in a PROC SQL SELECT statement with a libref in SAS/ACCESS® Interface to DB2 |
E9OD06 |
| SN-033148 |
An error message occurs when you connect to the HP Neoview database with the SAS/ACCESS® Interface to ODBC engine |
E9OD06 |
| SN-035971 |
An error occurs when you use SAS/ACCESS® Interface to ODBC to append data to a nonexistent DATAllegro table |
E9OD07 |
| Install Instructions: E9OD07s6.txt |
IMPORTANT!
You must have SAS 9.1.3 Service Pack 4
installed on your system before installing E9OD07.
Download: E9OD07 for
Solaris 64bit (File Size: 1.1M) |
| E9SB09 for Solaris 64bit |
| 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: E9SB09s6.txt |
IMPORTANT!
You must have SAS 9.1.3 Service Pack 4
installed on your system before installing E9SB09.
Download: E9SB09 for
Solaris 64bit (File Size: 718K) |
