| 82D226 for AIX |
| Released: Feb 2005 |
| Issue(s) Addressed: | Introduced: |
| SN-006004 |
"ERROR: CLI open cursor error: [IBM][CLI Driver] CLI0125E Functionsequence error" issued when using SAS/ACCESS Interface to DB2 |
82D203 |
| SN-005708 |
ERROR: SQL0514N The cursor "SQLCURCS297" is not in prepared state |
82D203 |
| SN-006276 |
New special queries added for ODBC and DB2: SQLDataSources and SQLDBMSInfo |
82D203 |
| SN-005997 |
Access AS400 data using Access Interface to ODBC can causeERROR:[merant][ODBC driver][DB2/400] Keyword FOR not expected. |
82D203 |
| SN-005996 |
Access Interface to ODBC when accessing MSAccess data may causedata to be overwritten if using APPEND operations |
82D203 |
| SN-005330 |
PROC APPEND to SQL Server using BCP option will insert data incorrectly |
82D203 |
| SN-004053 |
CLI ODBC driver error occurs when using SAS/ACCESS Interface to ODBC toaccess LANDMARK DBMS, through LANDMARK ODBC driver |
82D203 |
| SN-006323 |
Unable to get a single connection when using CONNECTION=GLOBALREAD asdocumentation would suggest |
82D204 |
| SN-006293 |
Read Isolation Level defaults to CR when using SAS/Access Interface toDB2 |
82D203 |
| SN-006312 |
CLI prepare error using NEON ODBC Driver to access DB2 on MVS withAccess to ODBC on Windows |
82D208 |
| SN-008603 |
"No data found" error occurs when trying to update or delete from a DB2table with SQL |
82D216 |
| SN-009478 |
SAS/Access to ODBC accessing Sql Server 2000 generates errors whencreating a temporary table |
82D220 |
| SN-009773 |
Incorrect data when KEEP= contains a field with a binary data type |
82D220 |
| SN-009914 |
/UNIQUE option does not work with ODBC engine for character typedvariables |
82D220 |
| SN-012061 |
"ERROR: No matching observation was found in MASTER data set" is issuedafter applying HOTFIX 82D220 |
82D222 |
| SN-013571 |
Bus Error accessing DBMS table via SAS/ACCESS to ODBC with rowset_size>1 |
82D225 |
| SN-013504 |
SQL3061N received bulkloading to a DB2 table in a DBCS database |
82D225 |
| SN-013980 |
DB2 bulk loader does not run with ALLOW READ ACCESS enabled |
82D226 |
| SN-008941 |
Segmentation violation when specifying DBCOMMIT= on the LIBNAMEstatement for DB2 |
82D226 |
| Install Instructions: 82D226ar.txt |
| Download: 82D226 for AIX (File Size: 382K) |
| 82OD09 for AIX |
| Released: Feb 2005 |
| Issue(s) Addressed: | Introduced: |
| SN-006004 |
"ERROR: CLI open cursor error: [IBM][CLI Driver] CLI0125E Functionsequence error" issued when using SAS/ACCESS Interface to DB2 |
82OD01 |
| SN-005708 |
ERROR: SQL0514N The cursor "SQLCURCS297" is not in prepared state |
82OD01 |
| SN-006276 |
New special queries added for ODBC and DB2: SQLDataSources and SQLDBMSInfo |
82OD02 |
| SN-005997 |
Access AS400 data using Access Interface to ODBC can causeERROR:[merant][ODBC driver][DB2/400] Keyword FOR not expected. |
82OD01 |
| SN-005996 |
Access Interface to ODBC when accessing MSAccess data may causedata to be overwritten if using APPEND operations |
82OD01 |
| SN-005330 |
PROC APPEND to SQL Server using BCP option will insert data incorrectly |
82OD01 |
| SN-004053 |
CLI ODBC driver error occurs when using SAS/ACCESS Interface to ODBC toaccess LANDMARK DBMS, through LANDMARK ODBC driver |
82OD01 |
| SN-006323 |
Unable to get a single connection when using CONNECTION=GLOBALREAD asdocumentation would suggest |
82OD02 |
| SN-006293 |
Read Isolation Level defaults to CR when using SAS/Access Interface toDB2 |
82OD02 |
| SN-006312 |
CLI prepare error using NEON ODBC Driver to access DB2 on MVS withAccess to ODBC on Windows |
82OD03 |
| SN-008603 |
"No data found" error occurs when trying to update or delete from a DB2table with SQL |
82OD05 |
| SN-009478 |
SAS/Access to ODBC accessing Sql Server 2000 generates errors whencreating a temporary table |
82OD06 |
| SN-009773 |
Incorrect data when KEEP= contains a field with a binary data type |
82OD06 |
| SN-009914 |
/UNIQUE option does not work with ODBC engine for character typedvariables |
82OD06 |
| SN-012061 |
"ERROR: No matching observation was found in MASTER data set" is issuedafter applying HOTFIX 82D220 |
82OD07 |
| SN-013571 |
Bus Error accessing DBMS table via SAS/ACCESS to ODBC with rowset_size>1 |
82OD08 |
| SN-013504 |
SQL3061N received bulkloading to a DB2 table in a DBCS database |
82OD08 |
| SN-013980 |
DB2 bulk loader does not run with ALLOW READ ACCESS enabled |
82OD09 |
| SN-008941 |
Segmentation violation when specifying DBCOMMIT= on the LIBNAMEstatement for DB2 |
82OD09 |
| Install Instructions: 82OD09ar.txt |
| Download: 82OD09 for AIX (File Size: 383K) |
| 82OC08 for AIX |
| Released: Jun 2007 |
| Issue(s) Addressed: | Introduced: |
| SN-005272 |
V8 formats are not compatible with V6 formats with SQL Pass-throughfacility for Char and Number |
82OC01 |
| SN-006708 |
"ERROR: Oracle execute error: ORA-01403: no data found" issued whenattempting to update table using PROC DBLOAD with criteria if no rowsmatch the criteria |
82OC02 |
| SN-008203 |
Bulkload userid/password are passed to the Unix Shell |
82OC03 |
| SN-001162 |
No data found error may occur when trying to update oracle table |
82OC04 |
| SN-012675 |
Using DBSASTYPE=(VAR="CHAR17")) gets value padded with '00'x (binary 0)rather than blanks in Oracle 9 in SAS 8.2 |
82OC06 |
| SN-009383 |
Datetime value containing 24 as hour value fails to load into Oracle |
82OC07 |
| SN-020088 |
The SAS/ACCESS® Interface to Oracle returns incorrect byte lengths for the CHAR and VARCHAR2 columns |
82OC08 |
| Install Instructions: 82OC08ar.txt |
| Download: 82OC08 for AIX (File Size: 150K) |
| 82BW03 for AIX |
| Released: Oct 2003 |
| Issue(s) Addressed: | Introduced: |
| SN-006764 |
Runtime error when extracting or displaying InfoCube with 0DATEattribute from InfoObject |
82BW01 |
| SN-006766 |
Cannot extract InfoCubes from SAS/ACCESS to SAP BW which have compoundcharacteristics where reference character of compound in SID table doesnot match InfoObject name |
82BW01 |
| SN-006765 |
SQL star view requires excessive space for temporary files in SAS/ACCESSto SAP BW |
82BW01 |
| SN-007682 |
Error creating formats for class variables during InfoCube dataextraction within SAS/ACCESS Interface to SAP BW |
82BW02 |
| SN-007675 |
Full extraction versus change data capture for InfoCubes and ODS inSAS/ACCESS Interface to SAP BW |
82BW02 |
| SN-007719 |
SAS/ACCESS Interface to SAP BW extraction does not recognize certainerror conditions |
82BW02 |
| SN-007674 |
Metadata extractions with FIELDS and TABLES selected from SAS/ACCESSInterface to SAP BW returns metadata about non-relevant tables |
82BW02 |
| SN-010160 |
Extractions of InfoCubes or ODS tables within SAS/ACCESS Interface toSAP BW using remote host metadata fails |
82BW03 |
| SN-008892 |
Misleading error message written when extracting ODS tables that containInfoObjects with compound keys from SAS/ACCESS Interface to SAP BW |
82BW03 |
| SN-010159 |
Change Data Capture feature in SAS/ACCESS Interface to SAP BW mayproduce incorrect InfoCube data for compressed InfoCubes in SAP BW |
82BW03 |
| SN-010158 |
Format names created for infocubes in SAS/ACCESS to SAP BW are notdescriptive |
82BW03 |
| Install Instructions: 82BW03ar.txt |
| Download: 82BW03 for AIX (File Size: 773K) |
| ATTENTION: To complete the installation of this hot fix, you must also download and install hot fix 82R302 for your operating system. Customers running in a DBCS environment should download 82R302. This hot fix will NOT be fully functional without both 82BW02 and 82R302 applied. |
| 82SB11 for AIX |
| Released: Oct 2004 |
| Issue(s) Addressed: | Introduced: |
| SN-004321 |
Unable to execute multiple SELECT statements with Access to Sybase inVersion 7 and Version 8 of the SAS System |
82SB01 |
| SN-005897 |
BULKLOAD of DOLLAR 12.2 format using SAS/ACCESS Interface to SYBASEproduces an OVERFLOW error |
82SB01 |
| SN-005909 |
Unable to append to a SYBASE table with BULKCOPY if an identity columnexists on the table |
82SB01 |
| SN-006327 |
SQL Pass-Through to Sybase EXECUTE statement allows only one statement |
82SB02 |
| SN-006335 |
Using PROC DBLOAD APPEND with BULKCOPY may cause data corruption |
82SB02 |
| SN-008355 |
PROC DBLOAD password is not X'd-out in the SAS log when using SAS/ACCESSInterface to Sybase |
82SB04 |
| SN-008473 |
"Error in results set for update" when updating a Sybase view with DATAstep MODIFY |
82SB04 |
| SN-008967 |
SAS/ACCESS Interface to Sybase incorrectly reads the Sybase value'JUN 21 2001 2:03:46:793AM' and generates a warning message |
82SB05 |
| SN-009796 |
Sybase Open Client 12.5 will not connect with Sybase 11.1 image on AIX |
82SB06 |
| SN-010317 |
Access to Sybase V8.2 is not honoring the database= option for updates |
82SB08 |
| SN-010867 |
Unable to update a Sybase table with an Identity field with SAS V8.2 |
82SB09 |
| SN-012997 |
With SAS 8.2 ACCESS TO SYBASE, Notes, warning or errors are not beingissued when attempting to insertinto a Sybase table with triggers using RAISERROR with PROC APPEND |
82SB10 |
| SN-001373 |
ALERT - SAS/ACCESS Version 6 incompatibility issues with SAS Version 7 andVersion 8 |
82SB10 |
| SN-010795 |
Wrong Sybase table accessed when using the SCHEMA LIBNAME option |
82SB10 |
| SN-012913 |
ALERT - "A Sybase Context Allocation Failed. sassyb:s_ctx: init of open clientfailed" error when using SAS/ACCESS Interface to Sybase on AIX |
82SB11 |
| Install Instructions: 82SB11ar.txt |
| Download: 82SB11 for AIX (File Size: 696K) |
| ATTENTION This hot fix should only be applied to systems running AIX 5.1 or greater. AIX customers running AIX 4.3.3 or an earlier version must download 82SB12. |
| 82SB12 for AIX |
| Released: May 2005 |
| Issue(s) Addressed: | Introduced: |
| SN-004321 |
Unable to execute multiple SELECT statements with Access to Sybase inVersion 7 and Version 8 of the SAS System |
82SB01 |
| SN-005897 |
BULKLOAD of DOLLAR 12.2 format using SAS/ACCESS Interface to SYBASEproduces an OVERFLOW error |
82SB01 |
| SN-005909 |
Unable to append to a SYBASE table with BULKCOPY if an identity columnexists on the table |
82SB01 |
| SN-006327 |
SQL Pass-Through to Sybase EXECUTE statement allows only one statement |
82SB02 |
| SN-006335 |
Using PROC DBLOAD APPEND with BULKCOPY may cause data corruption |
82SB02 |
| SN-008355 |
PROC DBLOAD password is not X'd-out in the SAS log when using SAS/ACCESSInterface to Sybase |
82SB04 |
| SN-008473 |
"Error in results set for update" when updating a Sybase view with DATAstep MODIFY |
82SB04 |
| SN-008967 |
SAS/ACCESS Interface to Sybase incorrectly reads the Sybase value'JUN 21 2001 2:03:46:793AM' and generates a warning message |
82SB05 |
| SN-009796 |
Sybase Open Client 12.5 will not connect with Sybase 11.1 image on AIX |
82SB06 |
| SN-010317 |
Access to Sybase V8.2 is not honoring the database= option for updates |
82SB08 |
| SN-010867 |
Unable to update a Sybase table with an Identity field with SAS V8.2 |
82SB09 |
| SN-012997 |
With SAS 8.2 ACCESS TO SYBASE, Notes, warning or errors are not beingissued when attempting to insertinto a Sybase table with triggers using RAISERROR with PROC APPEND |
82SB10 |
| SN-001373 |
ALERT - SAS/ACCESS Version 6 incompatibility issues with SAS Version 7 andVersion 8 |
82SB10 |
| SN-010795 |
Wrong Sybase table accessed when using the SCHEMA LIBNAME option |
82SB10 |
| SN-015017 |
Segmentation Violation error issued intermittently when accessing aSybase server that is not available |
82SB12 |
| Install Instructions: 82SB12ar.txt |
| Download: 82SB12 for AIX (File Size: 1.1M) |
ATTENTION (1): Before applying this hot fix on Solaris, you must first be running Open Client 12.5.
ATTENTION (2): The AIX version of this hot fix should only be applied to systems running AIX 4.3.3 or older. |
| 82TE05 for AIX |
| Released: Mar 2004 |
| Issue(s) Addressed: | Introduced: |
| SN-005626 |
FASTLOADING using SAS/ACCESS Interface to TERADATA may cause SAS tocrash in different ways |
82TE01 |
| SN-008268 |
Setting the value for Teradata response buffer length outside of SAS |
82TE02 |
| SN-009378 |
ALERT - Implicit SQL Pass Through query returns incorrect results from TeradataDBMS |
82TE03 |
| SN-010021 |
SAS/Access to Teradata V8.2 does not work with TUF Version 7.0 andV2R5.0 |
82TE03 |
| SN-011547 |
Locking modifiers are not handled correctly when DBKEY= is used |
82TE04 |
| SN-011549 |
Out of memory error may occur if DBKEY= is used to query a Teradatatable |
82TE04 |
| SN-011713 |
SAS allows only CONNECTION=UNIQUE when READ_ISOLATION_LEVEL=ACCESS isused in a LIBNAME statement in SAS/ACCESS Interface to Teradata |
82TE05 |
| SN-011822 |
ALERT - Incorrect WHERE passed to Teradata when OR condition is used with a DATEvariable |
82TE05 |
| Install Instructions: 82TE05ar.txt |
| Download: 82TE05 for AIX (File Size: 237K) |
| ATTENTION: The AIX version of this hot fix should only be applied to systems running AIX 4.3.3 or older. AIX customers running AIX 5.1 or greater must download 82TE07. |
| 82TE08 for AIX |
| Released: May 2005 |
| Issue(s) Addressed: | Introduced: |
| SN-005626 |
FASTLOADING using SAS/ACCESS Interface to TERADATA may cause SAS tocrash in different ways |
82TE01 |
| SN-008268 |
Setting the value for Teradata response buffer length outside of SAS |
82TE02 |
| SN-009378 |
ALERT - Implicit SQL Pass Through query returns incorrect results from TeradataDBMS |
82TE03 |
| SN-010021 |
SAS/Access to Teradata V8.2 does not work with TUF Version 7.0 andV2R5.0 |
82TE03 |
| SN-011547 |
Locking modifiers are not handled correctly when DBKEY= is used |
82TE04 |
| SN-011549 |
Out of memory error may occur if DBKEY= is used to query a Teradatatable |
82TE04 |
| SN-011713 |
SAS allows only CONNECTION=UNIQUE when READ_ISOLATION_LEVEL=ACCESS isused in a LIBNAME statement in SAS/ACCESS Interface to Teradata |
82TE05 |
| SN-011822 |
ALERT - Incorrect WHERE passed to Teradata when OR condition is used with a DATEvariable |
82TE05 |
| SN-012331 |
SAS/ACCESS Interface to Teradata on AIXR requires a new sastra modulewhen using Teradata TTU 7.1 |
82TE06 |
| SN-012478 |
'Error: CLI2: BADBUFRQ(302): Invalid buffer size' returned withSAS/ACCESS Interface to Teradata |
82TE07 |
| SN-012639 |
ALERT - TERADATA large decimal values not inserted correctly with the SAS/ACCESSInterface to Teradata |
82TE08 |
| Install Instructions: 82TE08ar.txt |
| Download: 82TE08 for AIX (File Size: 221K) |
| 82BB46 for AIX |
| Released: Jul 2003 |
| This Hot Fix is included in Hot Fix Bundle 82BX09. |
| Issue(s) Addressed: | Introduced: |
| SN-005210 |
ALERT - LINE statement may display incorrect data with COMPUTE BEFORE and theFLOW option |
82BA36 |
| SN-005223 |
BREAK statement and GROUP under an ACROSS may cause an error |
82BA36 |
| SN-005211 |
ALERT - GROUP values under ACROSS may be missing if BREAK/COMPUTE AFTER variableis requested |
82BA36 |
| SN-005767 |
ALERT - Nested ACROSS variables may result in system specific errors |
82BA36 |
| SN-005770 |
ALERT - Row variable values may be printed under wrong variable column |
82BA36 |
| SN-005766 |
ALERT - Rows of data may be missing from output with multiple ACROSS variablesin PROC REPORT |
82BA36 |
| SN-007784 |
ALERT - PROC REPORT quantile values may be incorrect |
82BA98 |
| SN-007785 |
ALERT - ACROSS values may be missing in the REPORT WINDOW of PROC REPORT |
82BA98 |
| SN-007786 |
BY statement in PROC REPORT may cause memory problems |
82BA98 |
| SN-007888 |
ALERT - All but the first column under an ACROSS variable may contain missingvalues |
82BA98 |
| SN-005776 |
CALL DEFINE specified in COMPUTE block may produce an abend |
82BA98 |
| SN-009218 |
ALERT - Data missing when ANALYSIS variable is requested over multiple ACROSSvariables |
82BB33 |
| SN-009829 |
PROC REPORT _PAGE_ location LINE statements are missing when onlysummary rows are printed on a page |
82BB46 |
| SN-010063 |
PROC REPORT option NOCOMPLETECOLS may apply only to last variable listedunder a nested ACROSS |
82BB46 |
| SN-010051 |
Label for OTHER format range may display in RBREAK summary line |
82BB46 |
| Install Instructions: 82BB46ar.txt |
| Download: 82BB46 for AIX (File Size: 460K) |
| 82BB57 for AIX |
| Released: Jul 2003 |
| This Hot Fix is included in Hot Fix Bundle 82BX09. |
| Issue(s) Addressed: | Introduced: |
| SN-004660 |
Library used by DATA step view executing on SAS/SHARE Server remainslocked |
82BA38 |
| SN-005758 |
ALERT - Assignment statements using Boolean logic may produce incorrect results |
82BA38 |
| SN-004681 |
ALERT - UNEXPECTED ERROR occurs when running a selection rule that references adynamic SAS modeling score |
82BA38 |
| SN-007025 |
Memory overlay possible with $CHARw., $ASCIIw., and $EBCDICw. informatsand character variable length mismatch |
82BA73 |
| SN-004659 |
ALERT - DATA step view containing Boolean comparisons can return incorrectresults |
82BA96 |
| SN-009334 |
Error occurred in the code generation subsystem during program load |
82BB39 |
| SN-010252 |
Segmentation violation using the FILEVAR= option with the FTP engine ona FILE statement |
82BB57 |
| Install Instructions: 82BB57ar.txt |
| Download: 82BB57 for AIX (File Size: 464K) |
