| E9BD61 for BASE SAS |
| 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 occur when you use a WHERE= option with indexed tables in the SQL procedure |
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 |
| SN-037611* |
Incorrect results are possible when you use the INDEX function without a comparison in the z/OS environment |
E9BD13 |
| SN-040951 |
Arithemetic performed on DATA and TIME data types is not passed to the underlying DBMS in SAS/ACCESS® 9.1.3 software |
E9BD20 |
| SN-038458 |
SQLPLAN internal errors might occur when you reference a view in a query that has variables that are defined with the the LENGTH= column modifier |
E9BD20 |
| SN-040492 |
Incorrect textualization of SQL Implicit Pass-Through queries occurs when you combine multiple inner joins with the UNION operator |
E9BD20 |
| SN-037846* |
A segmentation violation occurs in the SAS® 9.1.3 SQL procedure after you apply hot fixes E9BD08, E9BD09, and E9BD10 in the AIX operating environment |
E9BD20 |
| SN-038519 |
Specifying both the DBSLICPARM= and the MULTI_DATASRC_OPT= options might generate incorrect results |
E9BD26 |
| SN-039304 |
SQL views of DBMS tables may not return aliased column names |
E9BD26 |
| SN-039129 |
Formatting a newly created, missing numeric variable might result in a "Format not found" error |
E9BD32 |
| SN-039125 |
An SQLPLAN error might occur when you use a new column variable in a correlated subquery |
E9BD32 |
| SN-039271 |
ALERT - Outer join condition may not appear on WHERE clause when performing query against Oracle |
E9BD32 |
| SN-039984 |
An SQL procedure view does not return any rows when it is used in DATA step or a PRINT procedure |
E9BD43 |
| SN-041785 |
Read Access Violation errors occur when creating a long macro variable with the PROC SQL / INTO: macro interface |
E9BD43 |
| SN-042030 |
Oracle PREPARE error issued when SAS table is empty and no keys are in the WHERE clause |
E9BD47 |
| SN-044069 |
Performance might be affected if your query joins multiple tables or views in which variables are being renamed |
E9BD61 |
| * Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems. |
| Select an Available Operating System: |
| MAINFRAME: |
z/OS_(OS/390) |
| PC: |
Windows, Windows_for_IPF_(64_bit) |
| UNIX: |
HPUX, Solaris_(64-bit), AIX, Tru_64, Linux, HPUX_for_Itanium, Linux_for_Itanium |
Released January 16, 2012 on Tru 64, Linux
Released October 4, 2011 on HPUX, Solaris (64-bit), AIX, HPUX for Itanium, Linux for Itanium, Windows, Windows for IPF (64 bit), z/OS (OS/390)
|
ATTENTION (1): E9BD61 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 E9BD42 and E9BD48.
Download E9BD42
Download E9BD42 for SAS with Asian Language Support (DBCS) Download E9BD48
Download E9BD48 for SAS with Asian Language Support (DBCS) ATTENTION (3): OpenVMS Alpha customers should install SAS BASE hot fix E9BD32.
Download E9BD32 |
| E9BD59 for BASE SAS |
| Issue(s) Addressed: | Introduced: |
| SN-017514* |
Job submissions to grid manager increasingly slow |
E9BA05 |
| SN-017233* |
Poor performance with large DATA step and many missing values |
E9BA07 |
| SN-017667* |
ALERT - Segmentation Violation in task [ DATASETS ] using DELETE statement |
E9BA13 |
| SN-017653* |
-SGIO option generates I/O error message when ODS or procedure output is to an existing SAS data set |
E9BA15 |
| SN-017072 |
Metadata server service might show starting state but never start |
E9BA19 |
| SN-010866* |
Text Pad cannot store a single character value in column 1 |
E9BA29 |
| SN-017847* |
SUM function and statement give incorrect output on HP Itanium |
E9BA38 |
| SN-013525* |
ALERT - File>Open and File>Save might cause SAS to lock up with Jaws screen reader in SAS 9.1 |
E9BA55 |
| SN-018540* |
SAS Display Manager keys fail when you select Tools=>Options=>Output while using the JAWS screen reader with SAS® 9.1.3 on the Windows platform |
E9BA55 |
| SN-018790* |
SAS® fails when running a very large DATA step on AIX |
E9BA69 |
| SN-019040* |
Double-byte text strings are truncated when using the host WMF device driver |
E9BA76 |
| SN-018929* |
Font type WingDings might not work on DBCS SAS® 9.1.3 with the GPLOT procedure |
E9BA76 |
| SN-019225* |
DDE stops working after hotfix E9BA55 is installed |
E9BA85 |
| SN-019224* |
PROC APPEND fails with SGIO option on Windows operating systems |
E9BA85 |
| SN-019345* |
Increased LRECL support for SAS® on MS Windows |
E9BA95 |
| SN-019608* |
SAS® Metadata server fails to start when system restarted |
E9BB05 |
| SN-019640* |
HTML output is incorrect when ODS output is appended to an HTML file created by a DATA Step |
E9BB14 |
| 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-020870* |
SIGNON attempts to SAS® Grid Manager might fail |
E9BB58 |
| SN-020646* |
Moving the cursor off of a selected Radio Box item before releasing the mouse can incorrectly show updated selection |
E9BB75 |
| SN-021112* |
A SAS/CONNECT® software session might result in orphaned processes on a remote UNIX server |
E9BB75 |
| SN-031368* |
Poor performance with complex merges on AIX |
E9BB95 |
| SN-031098* |
ALERT - A SAS® server might become unresponsive on highly loaded systems |
E9BB95 |
| 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-032945* |
On HP Integrity systems, SAS® 9.1.3 SP4 installation process hangs if memory page size has been set higher than 8Kb |
E9BC30 |
| SN-032672* |
DDE error "Physical file does not exist, excel|system." occurs after applying hot fix bundle E9BX03 for SAS® 9.1.3 SP4 |
E9BC30 |
| SN-033403 |
Segmentation violation and bridge stub errors on AIX |
E9BC60 |
| SN-036130 |
Running large SQL queries in the AIX operating environment can generate results with missing values |
E9BC60 |
| SN-033581* |
Program with a large number of ELSE statements produces incorrect results on AIX |
E9BC60 |
| SN-034651 |
Using a Japanese or DBCS character in a pathname may cause truncation of file name |
E9BC67 |
| SN-035477* |
Invalid physical name error when a FILE statement contains certain Shift-JIS characters |
E9BC83 |
| SN-034955 |
The SAS® Metadata Server stops accepting new client connections and returns an error when too many files are open |
E9BD12 |
| SN-040822* |
Specifying the SAS® system option OPLIST may cause a segmentation violation error in the UNIX environment |
E9BD41 |
| SN-041361 |
Modification datetime stamp is changed on existing version of a SAS® data set when you create a new data set with same name |
E9BD44 |
| SN-031894* |
The SAS® Metadata Server might appear to hang during a period of high activity |
E9BD56 |
| SN-040494* |
ALERT - A SAS/SHARE® server fails or does not respond when it is run as a Microsoft Windows service |
E9BD59 |
| * Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems. |
| Select an Available Operating System: |
| PC: |
Windows, Windows_for_IPF_(64_bit) |
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 E9BD56 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 E9D216. The issue described in SN-021112 will not be fully fixed until both E9BD56 and E9D216 are applied. This is not applicable to z/OS sites.
Customers running on VMS should download E9BD44.
Customers running on Unix and MVS should download E9BD56. |
| E9BD56 for BASE SAS |
| Issue(s) Addressed: | Introduced: |
| SN-017514* |
Job submissions to grid manager increasingly slow |
E9BA05 |
| SN-017233* |
Poor performance with large DATA step and many missing values |
E9BA07 |
| SN-017667* |
ALERT - Segmentation Violation in task [ DATASETS ] using DELETE statement |
E9BA13 |
| SN-017653* |
-SGIO option generates I/O error message when ODS or procedure output is to an existing SAS data set |
E9BA15 |
| SN-017072 |
Metadata server service might show starting state but never start |
E9BA19 |
| SN-010866* |
Text Pad cannot store a single character value in column 1 |
E9BA29 |
| SN-017847* |
SUM function and statement give incorrect output on HP Itanium |
E9BA38 |
| SN-013525* |
ALERT - File>Open and File>Save might cause SAS to lock up with Jaws screen reader in SAS 9.1 |
E9BA55 |
| SN-018540* |
SAS Display Manager keys fail when you select Tools=>Options=>Output while using the JAWS screen reader with SAS® 9.1.3 on the Windows platform |
E9BA55 |
| SN-018790* |
SAS® fails when running a very large DATA step on AIX |
E9BA69 |
| SN-019040* |
Double-byte text strings are truncated when using the host WMF device driver |
E9BA76 |
| SN-018929* |
Font type WingDings might not work on DBCS SAS® 9.1.3 with the GPLOT procedure |
E9BA76 |
| SN-019225* |
DDE stops working after hotfix E9BA55 is installed |
E9BA85 |
| SN-019224* |
PROC APPEND fails with SGIO option on Windows operating systems |
E9BA85 |
| SN-019345* |
Increased LRECL support for SAS® on MS Windows |
E9BA95 |
| SN-019608* |
SAS® Metadata server fails to start when system restarted |
E9BB05 |
| SN-019640* |
HTML output is incorrect when ODS output is appended to an HTML file created by a DATA Step |
E9BB14 |
| 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-020870* |
SIGNON attempts to SAS® Grid Manager might fail |
E9BB58 |
| SN-020646* |
Moving the cursor off of a selected Radio Box item before releasing the mouse can incorrectly show updated selection |
E9BB75 |
| SN-021112* |
A SAS/CONNECT® software session might result in orphaned processes on a remote UNIX server |
E9BB75 |
| SN-031368* |
Poor performance with complex merges on AIX |
E9BB95 |
| SN-031098* |
ALERT - A SAS® server might become unresponsive on highly loaded systems |
E9BB95 |
| 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-032945* |
On HP Integrity systems, SAS® 9.1.3 SP4 installation process hangs if memory page size has been set higher than 8Kb |
E9BC30 |
| SN-032672* |
DDE error "Physical file does not exist, excel|system." occurs after applying hot fix bundle E9BX03 for SAS® 9.1.3 SP4 |
E9BC30 |
| SN-033403 |
Segmentation violation and bridge stub errors on AIX |
E9BC60 |
| SN-036130 |
Running large SQL queries in the AIX operating environment can generate results with missing values |
E9BC60 |
| SN-033581* |
Program with a large number of ELSE statements produces incorrect results on AIX |
E9BC60 |
| SN-034651 |
Using a Japanese or DBCS character in a pathname may cause truncation of file name |
E9BC67 |
| SN-035477* |
Invalid physical name error when a FILE statement contains certain Shift-JIS characters |
E9BC83 |
| SN-034955 |
The SAS® Metadata Server stops accepting new client connections and returns an error when too many files are open |
E9BD12 |
| SN-040822* |
Specifying the SAS® system option OPLIST may cause a segmentation violation error in the UNIX environment |
E9BD41 |
| SN-041361 |
Modification datetime stamp is changed on existing version of a SAS® data set when you create a new data set with same name |
E9BD44 |
| SN-031894* |
The SAS® Metadata Server might appear to hang during a period of high activity |
E9BD56 |
| * Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems. |
| Select an Available Operating System: |
| MAINFRAME: |
z/OS_(OS/390) |
| UNIX: |
HPUX, Solaris_(64-bit), AIX, Linux, HPUX_for_Itanium, Linux_for_Itanium |
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 E9BD56 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 E9D216. The issue described in SN-021112 will not be fully fixed until both E9BD56 and E9D216 are applied. This is not applicable to z/OS sites.
Customers running on VMS should download E9BD44.
Customers running on Windows should download E9BD59. |
| E9BD54 for BASE SAS |
| Issue(s) Addressed: | Introduced: |
| SN-017147 |
Output to RECFM=FB SASLIST file may contain carriage control |
E9BA11 |
| SN-017380 |
Client TSO session loops while processing FSBROWSE on library allocated to a SAS/SHARE® server |
E9BA11 |
| SN-019281 |
PROC CIMPORT fails when the transport file is a member of an uncataloged partitioned data set |
E9BA41 |
| SN-017797 |
"ERROR: Physical file does not exist, SYS06144.T115731.RA000.N389610T.INCL.H04" message from %INCLUDE |
E9BA41 |
| SN-018423 |
Control incorrectly appears to return to SAS/AF® application when sorting data on the mainframe |
E9BA52 |
| SN-013425 |
Autoexec may continue processing when leaving MENU entry defined to SHARE server in SAS/AF |
E9BA52 |
| SN-013720 |
TSO may hang when leaving SAS after running SAS/AF application with SAS/SHARE |
E9BA52 |
| SN-016476 |
System abend 0C4 in module SASTK |
E9BA52 |
| SN-018430 |
ERROR: Unable to initialize TCP/IP subsystem returns Condition Code 0 |
E9BA52 |
| SN-019299 |
Division-by-zero processing causes severe performance degradation |
E9BA75 |
| SN-020327 |
Contents of a variable change when you pass the variable to the FILEEXIST function |
E9BB03 |
| SN-018637 |
ALTLOG and ALTLIST files may be missing if directed to HFS |
E9BB03 |
| SN-019065 |
DISP is ignored in LIBNAME statement when existing allocation already exists |
E9BB03 |
| SN-019522 |
The FILENAME function for an HFS pathSAS argument generates incorrect results |
E9BB03 |
| SN-017038 |
Limited support in SAS® 9.1.3 SP4 for DSNTYPE=LARGE data sets when running under z/OS Releases V1R7 and later |
E9BB25 |
| SN-019842 |
SAS® 9 software reads all generations of a generation data group controlled by the Storage Management Subsystem |
E9BB25 |
| SN-020035 |
The RELEASE procedure can damage a currently assigned SAS® data library, resulting in an I/O error or U315 abnormal ending message |
E9BB34 |
| SN-020459 |
Performance issues found in SAS® software memory management on the z/OS platform |
E9BB44 |
| SN-020583 |
Concatenation of 257 physical sequential data sets fails when you run SAS® software on z/OS |
E9BB57 |
| SN-020905 |
Warning messages might appear when you read a large file from a UNIX file system |
E9BB67 |
| SN-030981 |
MP CONNECT (multi-process CONNECT) might fail when you use the XMS Access Method in Base SAS® in the z/OS environment |
E9BB90 |
| SN-010972 |
An error occurs when you use the %INCLUDE statement with a fileref that begins with an underscore |
E9BC06 |
| SN-033865 |
Base SAS® software might enter a loop after an input/output (I/O) error or “out of space†error occurs |
E9BC53 |
| SN-032798 |
The system ends abnormally with an S0C4 abend code during SAS termination |
E9BC53 |
| SN-033040 |
A %INCLUDE statement for an explicit path of a cataloged disk data set might fail in Base SAS® in the z/OS environment |
E9BC53 |
| SN-034459 |
Using the NODLTRUNCK option to process truncated libraries can result in data loss |
E9BC64 |
| SN-033892 |
A SAS/SHARE® server does not free a library when a client times out |
E9BC70 |
| SN-035332 |
The message "Libname libref is not assigned" might appear if you do not specify an engine |
E9BC82 |
| SN-035116 |
An error might occur when using ODS on the z/OS operating system after application of hot fix E9BC53 or E9BC70 |
E9BC82 |
| SN-035225 |
An error might occur when using ODS on the z/OS operating system after application of hot fix E9BC53 or E9BC70 |
E9BC82 |
| SN-036164 |
ERROR: "Library data set temp.dataset.name does not comply with RECFM=FS requirements or is truncated" |
E9BD04 |
| SN-037166 |
An abend occurs when you specify a user exit in an INFILE or FILE statement or with the ENGINE= option in the FILENAME statement |
E9BD16 |
| SN-039847 |
The error "...NO UNIT AVAILABLE" occurs when you allocate an existing data set |
E9BD31 |
| SN-041191 |
The FILEVAR= option in the INFILE or FILE statement does not work properly with the INFILE/FILE user exit |
E9BD45 |
| SN-041261 |
ALERT - A SAS® job that is running in a z/OS 1.12 operating environment might stop responding when an external file I/O error occurs |
E9BD45 |
| SN-041220* |
Mixed-case passwords that are submitted to a SAS® server in a z/OS operating environment return a security verification failure to the client |
E9BD54 |
| * Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems. |
| Select an Available Operating System: |
| MAINFRAME: |
z/OS_(OS/390) |
| ATTENTION: To fully implement the fix for SN-041220, you must also download and install SAS Base hot fix E9BD55. The fix for the problem documented in this SAS Note will not be fully functional unless both E9BD54 and E9BD55 are applied. |
| E9BD50 for BASE SAS |
| Issue(s) Addressed: | Introduced: |
| SN-031241 |
"ERROR: Library LIBREF is not assigned" when running the METALIB procedure |
E9BA08 |
| SN-017581 |
ERROR: Invalid physical name for library XXXX is displayed when using Update Table Metadata or PROC METALIB with concatenated libraries |
E9BA08 |
| SN-017580 |
ERROR: This Library is already assigned or cannot be reassigned |
E9BA08 |
| SN-017849 |
PROC METALIB fails to update an SPDS library table metadata with "Error: Invalid Option User." |
E9BA30 |
| SN-019486 |
"ERROR: Invalid memptr" occurs and the SAS® session becomes unresponsive when trying to access a view via a libref with the META LIBNAME engine |
E9BB18 |
| SN-020460 |
Joining two tables can cause your system to stop responding or can cause an access-violation problem |
E9BB46 |
| SN-031002 |
Database passwords are displayed in the SAS® log in clear text |
E9BC24 |
| SN-032284 |
A Read-access violation occurs when running PROC METALIB to update tables that originate from an Adabas database |
E9BC24 |
| SN-016116 |
Pre-Assigned Library fails with an unexpected error has occurred |
E9BC42 |
| SN-032376 |
Access violation occurs when updating metadata for a table that contains multiple indexes with long index names |
E9BC66 |
| 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-038292 |
Libname X not available for use error when password for WebDAV library is more than nine characters |
E9BD19 |
| SN-039550 |
A Read access violation occurs when you use the METALIB procedure to import or register database tables into the SAS® Metadata Repository |
E9BD28 |
| SN-042180 |
Support for implicit pass-through facility with SAS® Scalable Performance Data Server when using the META engine on the LIBNAME statement |
E9BD50 |
| Select an Available Operating System: |
| MAINFRAME: |
z/OS_(OS/390) |
| PC: |
Windows, Windows_for_IPF_(64_bit) |
| UNIX: |
HPUX, Solaris_(64-bit), AIX, Tru_64, Linux, HPUX_for_Itanium, Linux_for_Itanium |
ATTENTION: OpenVMS Alpha customers should install SAS BASE hot fix E9BD28.
Download E9BD28 |
| E9BD44 for BASE SAS |
| Issue(s) Addressed: | Introduced: |
| SN-017514* |
Job submissions to grid manager increasingly slow |
E9BA05 |
| SN-017233* |
Poor performance with large DATA step and many missing values |
E9BA07 |
| SN-017667* |
ALERT - Segmentation Violation in task [ DATASETS ] using DELETE statement |
E9BA13 |
| SN-017653* |
-SGIO option generates I/O error message when ODS or procedure output is to an existing SAS data set |
E9BA15 |
| SN-017072 |
Metadata server service might show starting state but never start |
E9BA19 |
| SN-010866* |
Text Pad cannot store a single character value in column 1 |
E9BA29 |
| SN-017847* |
SUM function and statement give incorrect output on HP Itanium |
E9BA38 |
| SN-013525* |
ALERT - File>Open and File>Save might cause SAS to lock up with Jaws screen reader in SAS 9.1 |
E9BA55 |
| SN-018540* |
SAS Display Manager keys fail when you select Tools=>Options=>Output while using the JAWS screen reader with SAS® 9.1.3 on the Windows platform |
E9BA55 |
| SN-018790* |
SAS® fails when running a very large DATA step on AIX |
E9BA69 |
| SN-019040* |
Double-byte text strings are truncated when using the host WMF device driver |
E9BA76 |
| SN-018929* |
Font type WingDings might not work on DBCS SAS® 9.1.3 with the GPLOT procedure |
E9BA76 |
| SN-019225* |
DDE stops working after hotfix E9BA55 is installed |
E9BA85 |
| SN-019224* |
PROC APPEND fails with SGIO option on Windows operating systems |
E9BA85 |
| SN-019345* |
Increased LRECL support for SAS® on MS Windows |
E9BA95 |
| SN-019608* |
SAS® Metadata server fails to start when system restarted |
E9BB05 |
| SN-019640* |
HTML output is incorrect when ODS output is appended to an HTML file created by a DATA Step |
E9BB14 |
| 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-020870* |
SIGNON attempts to SAS® Grid Manager might fail |
E9BB58 |
| SN-020646* |
Moving the cursor off of a selected Radio Box item before releasing the mouse can incorrectly show updated selection |
E9BB75 |
| SN-021112* |
A SAS/CONNECT® software session might result in orphaned processes on a remote UNIX server |
E9BB75 |
| SN-031368* |
Poor performance with complex merges on AIX |
E9BB95 |
| SN-031098* |
ALERT - A SAS® server might become unresponsive on highly loaded systems |
E9BB95 |
| 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-032945* |
On HP Integrity systems, SAS® 9.1.3 SP4 installation process hangs if memory page size has been set higher than 8Kb |
E9BC30 |
| SN-032672* |
DDE error "Physical file does not exist, excel|system." occurs after applying hot fix bundle E9BX03 for SAS® 9.1.3 SP4 |
E9BC30 |
| SN-033403 |
Segmentation violation and bridge stub errors on AIX |
E9BC60 |
| SN-033581* |
Program with a large number of ELSE statements produces incorrect results on AIX |
E9BC60 |
| SN-035477* |
Invalid physical name error when a FILE statement contains certain Shift-JIS characters |
E9BC76 |
| SN-034955 |
The SAS® Metadata Server stops accepting new client connections and returns an error when too many files are open |
E9BD12 |
| SN-041361 |
Modification datetime stamp is changed on existing version of a SAS® data set when you create a new data set with same name |
E9BD44 |
| * Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems. |
| Select an Available Operating System: |
| VMS: |
OpenVMS_Alpha |
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): This hot fix is available for VMS only.
Customers running on PC should download E9BD12 (or E9BD12 for SAS with Asian Language Support).
Customers running on z/OS (OS/390) and Tru_64 should download E9BC76 (or E9BC76 for SAS with Asian Language Support).
Customers running on all other UNIX hosts should download E9BD41 (or E9BD41 for SAS with Asian Lanuage Support). |
| E9BD42 for BASE SAS |
| 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-015882* |
A DBCS character that contains the hexadecimal value for a single or double quote might be misinterpreted by the SAS® tokenizer |
E9BA67 |
| 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-030428 |
Aliased constant values become missing in outer joins and unions |
E9BB72 |
| SN-030390 |
Improvements are now available in relational database optimization via the SQL procedure |
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-036281 |
PROC REPORT output generated by the CALL EXECUTE routine does not include text or variables generated by a COMPUTE block |
E9BC61 |
| SN-034018 |
MPRINT output generated twice when CALL EXECUTE is used within a macro |
E9BC61 |
| 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 message 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-040951 |
Arithemetic performed on DATA and TIME data types is not passed to the underlying DBMS in SAS/ACCESS® 9.1.3 software |
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-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-038698 |
SAS® Enterprise Guide® becomes unresponsive and the SAS® Workspace Server log grows extremely large |
E9BD22 |
| SN-040558 |
Invoking nested autocall macros using des= option causes error |
E9BD42 |
| * Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems. |
| Select an Available Operating System: |
| MAINFRAME: |
z/OS_(OS/390) |
| PC: |
Windows, Windows_for_IPF_(64_bit) |
| UNIX: |
HPUX, Solaris_(64-bit), AIX, Tru_64, Linux, HPUX_for_Itanium, Linux_for_Itanium |
ATTENTION (1): To complete the installation of this hot fix, you must also download and install SAS Base hot fixes E9BD61 and E9BD48.
Download E9BD61
Download E9BD61 for SAS with Asian Language Support (DBCS) Download E9BD48
Download E9BD48 for SAS with Asian Language Support (DBCS) This hot fix will NOT be fully functional without E9BD61 and E9BD48 applied.
ATTENTION (2): For additional configuration instructions for improving relational database optimization, see Problem Note SN-030390 above. |
| E9BD38 for BASE SAS |
| 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 |
| Select an Available Operating System: |
| MAINFRAME: |
z/OS_(OS/390) |
| PC: |
Windows, Windows_for_IPF_(64_bit) |
| UNIX: |
HPUX, Solaris_(64-bit), AIX, Linux, HPUX_for_Itanium, Linux_for_Itanium, Solaris_for_x64 |
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. |
| E9BD32 for BASE SAS |
| 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 occur when you use a WHERE= option with indexed tables in the SQL procedure |
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 |
| SN-037611* |
Incorrect results are possible when you use the INDEX function without a comparison in the z/OS environment |
E9BD13 |
| SN-038458 |
SQLPLAN internal errors might occur when you reference a view in a query that has variables that are defined with the the LENGTH= column modifier |
E9BD20 |
| SN-037846* |
A segmentation violation occurs in the SAS® 9.1.3 SQL procedure after you apply hot fixes E9BD08, E9BD09, and E9BD10 in the AIX operating environment |
E9BD20 |
| SN-038519 |
Specifying both the DBSLICPARM= and the MULTI_DATASRC_OPT= options might generate incorrect results |
E9BD26 |
| SN-039304 |
SQL views of DBMS tables may not return aliased column names |
E9BD26 |
| SN-039129 |
Formatting a newly created, missing numeric variable might result in a "Format not found" error |
E9BD32 |
| SN-039125 |
An SQLPLAN error might occur when you use a new column variable in a correlated subquery |
E9BD32 |
| SN-039271 |
ALERT - Outer join condition may not appear on WHERE clause when performing query against Oracle |
E9BD32 |
| * Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems. |
| Select an Available Operating System: |
| VMS: |
OpenVMS_Alpha |
ATTENTION: Customers running SAS Base SQL must also download and install SAS Base hot fixes E9BD25 and E9BD33.
Download E9BD25
Download E9BD25 for SAS with Asian Language Support (DBCS) Download E9BD33
Download E9BD33 for SAS with Asian Language Support (DBCS) ATTENTION: This hot fix is intended for OpenVMS Alpha customers. Customers running on all other platforms should download and install SAS BASE hot fix E9BD61.
Download E9BD61
Download E9BD61 for SAS with Asian Language Support (DBCS) |
| E9TE13 for SAS/ACCESS INTERFACE TO TERADATA |
| Issue(s) Addressed: | Introduced: |
| SN-018170 |
Teradata FASTLOAD performance problems in SAS® 9 |
E9TE01 |
| SN-018429* |
Running the Teradata MultiLoad utilty is now supported on z/OS |
E9TE02 |
| SN-034604 |
Running multiple, concurrent processes in SAS® Marketing Automation causes an error in the FastLoad utility in the SAS/ACCESS® Interface to Teradata |
E9TE03 |
| SN-019941 |
Running multiple, concurrent processes causes an error in the FastLoad utility when you use it with the SAS/ACCESS® Interface to Teradata |
E9TE03 |
| SN-019939 |
Using MULTILOAD=YES without CREATE/DROP table rights in the SAS/ACCESS® Interface to Teradata can generate an error |
E9TE03 |
| SN-020199 |
The same query produces different results when submitted using the Pass-Through Facility in SAS/ACCESS® Interface to Teradata and using Teradata BTEQ |
E9TE04 |
| SN-020515 |
An error occurs when you attempt to access a Teradata TTU 8.2 library via SAS/ACCESS® Interface to Teradata 9.1.3 Service Pack 4 |
E9TE04 |
| SN-031370 |
LDAP authentication is not supported in SAS/ACCESS® Interface to Teradata |
E9TE05 |
| SN-032796 |
An incorrect error message is sometimes generated when using MODE=Teradata |
E9TE06 |
| SN-033955 |
Using the X versions of Teradata views to retrieve metadata causes performance degradation |
E9TE07 |
| SN-035002 |
An error occurs when you use the MultiLoad facility with SAS/ACCESS® 9.1.3 Interface to Teradata |
E9TE08 |
| SN-034729 |
Teradata's BIGINT data type is not supported in SAS/ACCESS® Interface to Teradata |
E9TE08 |
| SN-036348 |
An error might occur when you invoke the FastExport utility multiple times with the SAS/ACCESS® Interface to Teradata |
E9TE09 |
| SN-036369 |
An error might occur when you invoke the MultiLoad utility multiple times with the SAS/ACCESS® Interface to Teradata |
E9TE09 |
| SN-035616 |
The FastExport module fails when it is run under an object spawner |
E9TE09 |
| SN-036176 |
A Read-access violation occurs when you submit an explicit SQL pass-through query to Teradata |
E9TE10 |
| SN-037244 |
Performance decreases when you use an ORDER BY clause in the SQL procedure with the Teradata FastExport utility |
E9TE11 |
| SN-037894 |
A segmentation violation occurs when you use the MULTILOAD=YES option in the SAS/ACCESS® Interface to Teradata on an HP Itanium operating system |
E9TE11 |
| SN-031972 |
Teradata Tools and Utilities (TTU) 12 is not supported in the AIX environment |
E9TE12 |
| SN-038521 |
An error occurs when you use a LIBNAME statement with LDAP authentication to connect to Teradata in UNIX operating environments |
E9TE12 |
| SN-038647 |
An FNCLOADERROR(519) error occurs when you try to connect to the Teradata database in UNIX operating environments |
E9TE12 |
| SN-038840 |
Teradata Tools and Utilities (TTU) 13 is not suppported in the AIX operating environment |
E9TE13 |
| SN-038873 |
A UTY4015 access-module error occurs when you use the Teradata MultiLoad utility with SAS/ACCESS® Interface to Teradata |
E9TE13 |
| * Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems. |
| Select an Available Operating System: |
| UNIX: |
HPUX, Solaris_(64-bit), AIX, Linux, HPUX_for_Itanium |
Released May 18, 2010 on HPUX, Solaris (64-bit), Linux, HPUX for Itanium
Released March 24, 2010 on AIX
|
| E9OD08 for SAS/ACCESS INTERFACE TO ODBC |
| Issue(s) Addressed: | Introduced: |
| SN-037514 |
Support is now available for reading the MySQL LONGTEXT data type in SAS/ACCESS® Interface to ODBC |
E9OD01 |
| 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 |
| SN-037477 |
An incorrect value might be inserted into an Oracle SMALLINT data type when you use SAS/ACCESS® Interface to ODBC on a Linux platform |
E9OD08 |
| Select an Available Operating System: |
| PC: |
Windows, Windows_for_IPF_(64_bit) |
| UNIX: |
HPUX, Solaris_(64-bit), AIX, Linux, HPUX_for_Itanium |
| E9OC15 for SAS/ACCESS INTERFACE TO ORACLE |
| Issue(s) Addressed: | Introduced: |
| SN-018149* |
Bulkloading Oracle data on OpenVMS may load incorrect data |
E9OC02 |
| SN-014205* |
SAS/ACCESS Interface to Oracle 9.2.0.5 on OpenVMS Alpha using SAS 9.1.3 |
E9OC02 |
| SN-018148* |
Access Violation with SAS/Access® to Oracle on OpenVMS Alpha |
E9OC02 |
| SN-018748* |
ORACLE FNA support |
E9OC04 |
| SN-019772 |
The Oracle Database 10g client is supported on the Linux Itanium operating system through the SAS/ACCESS® Interface to Oracle |
E9OC05 |
| SN-019771 |
The Oracle Database 10g client is supported on the HP Itanium operating system through the SAS/ACCESS® Interface to Oracle |
E9OC06 |
| SN-020088 |
The SAS/ACCESS® Interface to Oracle returns incorrect byte lengths for the CHAR and VARCHAR2 columns |
E9OC07 |
| SN-020190 |
The Oracle bulk loader is disabled when you use the -NOXCMD command to invoke the SAS® System |
E9OC07 |
| SN-020317 |
The Oracle 10g client is supported on the Linux operating system through SAS/ACCESS® Interface to Oracle |
E9OC08 |
| SN-020739* |
An error occurs when you allocate the SQLDAT file externally during Oracle bulk loading under z/OS |
E9OC09 |
| SN-020733 |
Control files and data files might still exist after you bulk load an Oracle table |
E9OC09 |
| SN-020736* |
Using the Oracle Bulk Loader under z/OS to create multiple Oracle tables might cause an error |
E9OC09 |
| SN-020794 |
An error occurs when there is a space in the directory paths of an SQL*Loader file |
E9OC09 |
| SN-020728* |
An S0C4 abnormal ending might occur during an Oracle bulk loading task on z/OS |
E9OC09 |
| SN-020726* |
Externally defined .DAT files are not handled correctly by Oracle Bulk Loader under z/OS |
E9OC09 |
| SN-020712 |
Decreased performance might occur when you use bulk loading in SAS/ACCESS® Interface to Oracle |
E9OC09 |
| SN-020710 |
The BL_DEFAULT_DIR data set option enables you to overide the default path for SQL*LOADER intermediate files when bulk loading to Oracle |
E9OC09 |
| SN-020714 |
TIMESTAMP format does not work for all foreign languages |
E9OC09 |
| SN-020734 |
An error occurs when data that has any date format is loaded to Oracle in a non-English environment |
E9OC09 |
| SN-020687 |
Support for Oracle TIMESTAMP data types added in SAS 9.1.3 |
E9OC10 |
| SN-031179 |
Hot Fix E9OC10 for Oracle timestamp support might cause performance degradation |
E9OC11 |
| SN-032148 |
The Table Loader step in a SAS® Data Integration Studio job might not stop processing properly after a constraint violation error |
E9OC12 |
| SN-019910 |
INSERTBUFF= should be set to 1 when Using MODIFY to update an Oracle table |
E9OC12 |
| SN-032461 |
An error occurs because temporary tables are not deleted when you execute SCD2 code |
E9OC12 |
| SN-036595 |
The BL_DELETE_FILES option deletes all file types(.ctl, .log, and .dat) that are created with the bulk loader |
E9OC13 |
| SN-035837 |
Trace messages do not appear for the SQL statements INSERT, UPDATE, and DELETE |
E9OC13 |
| SN-033135 |
"Error: Physical file does not exist" occurs when using SAS® Merchandise Data Integration with Oracle SQL*Loader |
E9OC13 |
| SN-037483* |
An error occurs when you connect to Oracle from SAS® 9.1.3 with an Oracle 11g client on an Itanium machine in an HP-UX environment |
E9OC14 |
| SN-038842 |
An SQL query that is run against an Oracle table might return incorrect results if a WHERE clause contains the BETWEEN operator and a date operand |
E9OC15 |
| * Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems. |
| Select an Available Operating System: |
| MAINFRAME: |
z/OS_(OS/390) |
| PC: |
Windows, Windows_for_IPF_(64_bit) |
| VMS: |
OpenVMS_Alpha |
| UNIX: |
HPUX, Solaris_(64-bit), AIX, Linux, HPUX_for_Itanium, Linux_for_Itanium |
ATTENTION: To complete the install of this hot fix on the UNIX platforms, you must manually relink the sasora executable. See step 8 of the install instructions for more details.
ATTENTION: Customers running on the Solaris for X64 platform should download and install E9OC11. DBCS customers should install the DBCS version of E9OC11.
ATTENTION: To complete the installation of this hot fix, OpenVMS_Alpha customers must also download and install hot fix E9BD33. DBCS customers should install the DBCS version of E9BD33. Customers running on all other platforms should download and install hot fix E9BD48. DBCS customers should install the DBCS version of E9BD48. This hot fix will NOT be fully functional without having both E9OC15 and E9BD33 or E9BD48 applied.
ATTENTION: This hot fix is intended for customers running the Oracle 9i client or above. Customers running the Oracle 8i client should either upgrade their Oracle client to 9i or above before installing this hot fix, or install E9OC09 instead. |
| E9TE11 for SAS/ACCESS INTERFACE TO TERADATA |
| Issue(s) Addressed: | Introduced: |
| SN-018170 |
Teradata FASTLOAD performance problems in SAS® 9 |
E9TE01 |
| SN-018429* |
Running the Teradata MultiLoad utilty is now supported on z/OS |
E9TE02 |
| SN-034604 |
Running multiple, concurrent processes in SAS® Marketing Automation causes an error in the FastLoad utility in the SAS/ACCESS® Interface to Teradata |
E9TE03 |
| SN-019941 |
Running multiple, concurrent processes causes an error in the FastLoad utility when you use it with the SAS/ACCESS® Interface to Teradata |
E9TE03 |
| SN-019939 |
Using MULTILOAD=YES without CREATE/DROP table rights in the SAS/ACCESS® Interface to Teradata can generate an error |
E9TE03 |
| SN-020199 |
The same query produces different results when submitted using the Pass-Through Facility in SAS/ACCESS® Interface to Teradata and using Teradata BTEQ |
E9TE04 |
| SN-020515 |
An error occurs when you attempt to access a Teradata TTU 8.2 library via SAS/ACCESS® Interface to Teradata 9.1.3 Service Pack 4 |
E9TE04 |
| SN-031370 |
LDAP authentication is not supported in SAS/ACCESS® Interface to Teradata |
E9TE05 |
| SN-032796 |
An incorrect error message is sometimes generated when using MODE=Teradata |
E9TE06 |
| SN-033955 |
Using the X versions of Teradata views to retrieve metadata causes performance degradation |
E9TE07 |
| SN-035002 |
An error occurs when you use the MultiLoad facility with SAS/ACCESS® 9.1.3 Interface to Teradata |
E9TE08 |
| SN-034729 |
Teradata's BIGINT data type is not supported in SAS/ACCESS® Interface to Teradata |
E9TE08 |
| SN-036348 |
An error might occur when you invoke the FastExport utility multiple times with the SAS/ACCESS® Interface to Teradata |
E9TE09 |
| SN-036369 |
An error might occur when you invoke the MultiLoad utility multiple times with the SAS/ACCESS® Interface to Teradata |
E9TE09 |
| SN-035616 |
The FastExport module fails when it is run under an object spawner |
E9TE09 |
| SN-036176 |
A Read-access violation occurs when you submit an explicit SQL pass-through query to Teradata |
E9TE10 |
| SN-037244 |
Performance decreases when you use an ORDER BY clause in the SQL procedure with the Teradata FastExport utility |
E9TE11 |
| SN-037894 |
A segmentation violation occurs when you use the MULTILOAD=YES option in the SAS/ACCESS® Interface to Teradata on an HP Itanium operating system |
E9TE11 |
| * Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems. |
| Select an Available Operating System: |
| MAINFRAME: |
z/OS_(OS/390) |
| PC: |
Windows |
| ATTENTION: This hot fix is currently unavailable on Unix systems. See E9TE10 for the current fixes available on Unix. |
| E9CT05 for SAS/CONNECT |
| Issue(s) Addressed: | Introduced: |
| SN-019386 |
SAS/CONNECT may issue "Segmentation Violation In Task [ Program ]" |
E9CT01 |
| SN-020817 |
Using the JOBNAME= option to specify a job name in the GRDSVC_ENABLE call routine |
E9CT01 |
| SN-031089 |
A floating-point exception error might occur if you use the UPLOAD procedure to move a file that is larger than 2 GB |
E9CT02 |
| SN-013122 |
WZX: Invalid Conversion Map Specified |
E9CT03 |
| SN-032983 |
Invalid results occur when you use the DOWNLOAD procedure with the V6TRANSPORT option in SAS® 9.1.3 in the z/OS environment |
E9CT03 |
| SN-031820 |
An error can occur when you have applied Hot Fix #E9BB97 and you remotely submit PROC UPLOAD with a WHERE clause that points to a remote DBCS machine |
E9CT03 |
| SN-034153 |
Option DBIDIRECTEXEC prevents SAS® Enterprise Guide from opening tables created by PROC SQL |
E9CT04 |
| SN-033576 |
SAS® Enterprise Guide® does not detect when SAS data sets are created, updated, or deleted through a grid |
E9CT04 |
| 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 |
E9CT05 |
| Select an Available Operating System: |
| MAINFRAME: |
z/OS_(OS/390) |
| PC: |
Windows, Windows_for_IPF_(64_bit) |
| VMS: |
OpenVMS_Alpha |
| UNIX: |
HPUX, Solaris_(64-bit), AIX, Tru_64, Linux, HPUX_for_Itanium, Linux_for_Itanium |
Released July 17, 2009 on HPUX, Solaris (64-bit), Tru 64, HPUX for Itanium, Linux for Itanium, Windows for IPF (64 bit), OpenVMS Alpha, z/OS (OS/390)
Released June 29, 2009 on AIX, Linux, Windows
|
ATTENTION: To make this hot fix fully functional you must also download and install hot fixes E9BD56 for z/OS and Unix, E9BD59 for Windows, E9BC97 and E9BC98.
If you are running SAS with Asian Language Support, please download :
E9BD56 (Asian Language Support) for z/OS and Unix, E9BD59 (Asian Language Support) for Windows, E9BC97 (Asian Language Support) and E9BC98 (Asian Language Support) |
| E9PF08 for SAS/ACCESS INTERFACE TO PC FILES |
| Issue(s) Addressed: | Introduced: |
| SN-031105 |
Variable names truncate to 8 characters when you use the EXPORT procedure and DBMS=DTA to create a Stata file |
E9PF01 |
| SN-018769 |
PROC EXPORT fails for DBMS=JMP with floating point error on the Windows platform |
E9PF01 |
| SN-018768 |
PROC EXPORT to Stata file on Windows platform creates incorrect datatype |
E9PF01 |
| SN-018913 |
PROC EXPORT to JMP® creates numeric fields with 2 decimal places |
E9PF01 |
| SN-018993 |
Certain date formats generate error with PROC EXPORT when exporting to SPSS, STATA, and JMP files |
E9PF01 |
| SN-019383 |
Proc Import of SPSS v12 File Errors and Truncates Long Variable Names |
E9PF02 |
| SN-019465 |
Segmentation violation when importing an Excel 5.0/95 spreadsheet into SAS |
E9PF02 |
| SN-020326 |
The IMPORT Procedure in SAS® Enterprise Guide® does not read Excel data properly |
E9PF03 |
| SN-020325 |
Using the EXPORT procedure with DBMS=XLS in 9.1.3 SAS/ACCESS® Interface to PC Files under UNIX to create a Microsoft Excel file might cause problems with the Excel file |
E9PF03 |
| SN-013954* |
PROC DBLOAD to create an Excel 5.0 file does not apply numeric formatting correctly |
E9PF05 |
| SN-020997 |
The SAS/ACCESS® Interface to PC files on UNIX cannot read Excel column names that contain Asian phonetic text strings |
E9PF05 |
| SN-030657 |
Missing values can occur in SAS if you use SAS/ACCESS® Interface to PC Files 9.1.3 to pull data from an Excel workbook that resides under UNIX |
E9PF06 |
| SN-030646 |
The SHEET= and RANGE= options are now available in the EXPORT procedure when you use SAS/ACCESS® Interface to PC Files 9.1.3 in the UNIX environment |
E9PF06 |
| SN-030961 |
When using SAS/ACCESS® Interface to PC Files on UNIX platforms to write to Excel, some types of data result in a corrupted XLS file |
E9PF06 |
| SN-031711 |
Formatting errors might occur when exporting SAS® data sets to Stata |
E9PF07 |
| SN-031715 |
Memory request errors occur when using PROC IMPORT DBMS=XLS to import complex Excel spreadsheets |
E9PF07 |
| SN-032702* |
ALERT - Missing values can be incorrectly filled when you import a Microsoft Access file with the DBSASTYPE= option in a LIBNAME statement |
E9PF07 |
| SN-036679 |
An incorrect Microsoft Excel sheet might be read when you use the XLS engine to read Excel ranges |
E9PF08 |
| SN-036681 |
Invalid header-file errors occur when use the IMPORT procedure with the JMP engine to read JMP® 8 files |
E9PF08 |
| SN-034258 |
An error occurs when you use PROC IMPORT to read an SPSS file with a user-defined format that has the same name as a SAS format |
E9PF08 |
| SN-036667* |
Time values that exceed 24 hours do not properly export when you use the EXCEL engine |
E9PF08 |
| * Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems. |
| Select an Available Operating System: |
| PC: |
Windows, Windows_for_IPF_(64_bit) |
| UNIX: |
HPUX, Solaris_(64-bit), AIX, Tru_64, Linux, HPUX_for_Itanium, Linux_for_Itanium, Solaris_for_x64 |
| E9BC59 for BASE SAS |
| 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 |
| * Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems. |
| Select an Available Operating System: |
| MAINFRAME: |
z/OS_(OS/390) |
| PC: |
Windows, Windows_for_IPF_(64_bit) |
| UNIX: |
HPUX, Solaris_(64-bit), AIX, Linux, HPUX_for_Itanium, Linux_for_Itanium, Solaris_for_x64 |
| ATTENTION: This hot fix should be applied to all locations where the SAS Metadata Server is running. |
| E9OC11 for SAS/ACCESS INTERFACE TO ORACLE |
| Issue(s) Addressed: | Introduced: |
| SN-018149* |
Bulkloading Oracle data on OpenVMS may load incorrect data |
E9OC02 |
| SN-014205* |
SAS/ACCESS Interface to Oracle 9.2.0.5 on OpenVMS Alpha using SAS 9.1.3 |
E9OC02 |
| SN-018148* |
Access Violation with SAS/Access® to Oracle on OpenVMS Alpha |
E9OC02 |
| SN-018748* |
ORACLE FNA support |
E9OC04 |
| SN-019772 |
The Oracle Database 10g client is supported on the Linux Itanium operating system through the SAS/ACCESS® Interface to Oracle |
E9OC05 |
| SN-019771 |
The Oracle Database 10g client is supported on the HP Itanium operating system through the SAS/ACCESS® Interface to Oracle |
E9OC06 |
| SN-020088 |
The SAS/ACCESS® Interface to Oracle returns incorrect byte lengths for the CHAR and VARCHAR2 columns |
E9OC07 |
| SN-020190 |
The Oracle bulk loader is disabled when you use the -NOXCMD command to invoke the SAS® System |
E9OC07 |
| SN-020317 |
The Oracle 10g client is supported on the Linux operating system through SAS/ACCESS® Interface to Oracle |
E9OC08 |
| SN-020739* |
An error occurs when you allocate the SQLDAT file externally during Oracle bulk loading under z/OS |
E9OC09 |
| SN-020733 |
Control files and data files might still exist after you bulk load an Oracle table |
E9OC09 |
| SN-020736* |
Using the Oracle Bulk Loader under z/OS to create multiple Oracle tables might cause an error |
E9OC09 |
| SN-020794 |
An error occurs when there is a space in the directory paths of an SQL*Loader file |
E9OC09 |
| SN-020728* |
An S0C4 abnormal ending might occur during an Oracle bulk loading task on z/OS |
E9OC09 |
| SN-020726* |
Externally defined .DAT files are not handled correctly by Oracle Bulk Loader under z/OS |
E9OC09 |
| SN-020712 |
Decreased performance might occur when you use bulk loading in SAS/ACCESS® Interface to Oracle |
E9OC09 |
| SN-020710 |
The BL_DEFAULT_DIR data set option enables you to overide the default path for SQL*LOADER intermediate files when bulk loading to Oracle |
E9OC09 |
| SN-020714 |
TIMESTAMP format does not work for all foreign languages |
E9OC09 |
| SN-020734 |
An error occurs when data that has any date format is loaded to Oracle in a non-English environment |
E9OC09 |
| SN-020687 |
Support for Oracle TIMESTAMP data types added in SAS 9.1.3 |
E9OC10 |
| SN-031179 |
Hot Fix E9OC10 for Oracle timestamp support might cause performance degradation |
E9OC11 |
| * Indicates that the fix for the issue described in this SAS Note does not apply to all Operating Systems. |
| Select an Available Operating System: |
| UNIX: |
Solaris_for_x64 |
ATTENTION: Customers running on platforms other than Solaris for X64 should download and install hot fix E9OC13. DBCS customers should install the DBCS version of E9OC13.
ATTENTION: To complete the installation of this hot fix on Solaris for x64, you must also download and install hot fix E9BB64. DBCS customers should install the DBCS version of E9BB64. This hot fix will NOT be fully functional without having both E9OC11 and E9BB64 applied.
ATTENTION: This hot fix is intended for customers running the Oracle 9i client or above. Customers running the Oracle 8i client should either upgrade their Oracle client to 9i or above before installing this hot fix, or install E9OC09 instead. |
Return to 9.1.3 Hot Fix Home