SAS Hot Fixes for Release 8.2 (TS2M0) SBCS

SAS Release 8.2 (TS2M0)

SAS/ACCESS INTERFACE TO ADABAS

82AD01

Issue(s) Addressed: Introduced:

SN-008569 ADABAS view descriptor subset WHERE clause GT 72 characters in length isnot passed to the data base 82AD01
SN-006013 SUBSET WHERE used in ADABAS access descriptor returns zero rows 82AD01
SN-008697 NAT3061 error when creating ADABAS descriptor using 4 digit SYSFILE parm 82AD01

Select an Available Operating System:

MAINFRAME: OS/390

Top ^

82AD02

Issue(s) Addressed: Introduced:

SN-009206 Error: Periodic group / multiple value status has changed for field 82AD02

Select an Available Operating System:

MAINFRAME: OS/390

Top ^

SAS/ACCESS INTERFACE TO CA-DATACOM/DB

82DD01

Issue(s) Addressed: Introduced:

SN-005983 'Unsupported DATADICTIONARY Version' message issued for Release 10 ofCA-DATACOM/DB 82DD01

Select an Available Operating System:

MAINFRAME: OS/390

Top ^

SAS/ACCESS INTERFACE TO DB2

82D201 was replaced by 82D223

82D202 was replaced by 82D223

82D203 was replaced by 82D226

82D204 was replaced by 82D226

82D205 was replaced by 82D213

82D206 was replaced by 82D223

82D207 was replaced by 82D223

82D208 was replaced by 82D226

82D209 was replaced by 82D224

82D210 was replaced by 82D226

82D211 was replaced by 82D224

82D212 was replaced by 82D223

82D213

Issue(s) Addressed: Introduced:

SN-006469 Using NULLS statement in PROC DBLOAD to define a DB2 column as NOT NULLWITH DEFAULT does not work 82D205
SN-005504 ALERT - Including an SQL statement in PROC DB2UTIL or PROC DBLOAD may causewrong table to be updated 82D213
SN-006484 PROC DB2UTIL can insert garbage into DB2 columns that are defined asVARCHAR 82D213

Select an Available Operating System:

MAINFRAME: OS/390

Top ^

82D214 was replaced by 82D224

82D215 was replaced by 82D223

82D216 was replaced by 82D226

82D217 was replaced by 82D224

82D218 was replaced by 82D224

82D219 was replaced by 82D223

82D220 was replaced by 82D226

82D221 was replaced by 82D223

82D222 was replaced by 82D226

82D223

Issue(s) Addressed: Introduced:

SN-004819 SAS/ACCESS view referencing DB2 table with character column wider than200 bytes may produce errors 82D201
SN-004982 CPU time significantly higher with SQL pass-through to DB2 82D201
SN-005647 ALERT - Using LOCATION= in PROC ACCESS can cause error or incorrecttable to be used 82D202
SN-006736 Specifying DBKEY= to reference a composite index can produce one ofseveral error messages 82D206
SN-007182 YEAR, MONTH and DAY functions may be passed to DB2 82D207
SN-007857 Performance problem when using a libref pointing to a remote locationthat includes the option preserve_names=yes 82D212
SN-007858 Incorrect list of tables is displayed when a libref is pointing to aremote location 82D212
SN-008508 Specifying a composite index with DBKEY= may cause a S0C4 abend 82D215
SN-007859 Setting a special register via DBCONINIT does not always work 82D219
SN-009720 Extra and unexpected commits may occur after applying DB2 hotfix 82D219
SN-002892 DB2 SQLCODE +535 received updating DB2 table 82D221
SN-013020 Performance issues with regard to padding of decimals 82D223

Select an Available Operating System:

MAINFRAME: OS/390

ATTENTION: To complete the installation of this hot fix, you must also download and install hot fix 82BC07 for OS/390. This hot fix will NOT be fully functional without both 82D223 and 82BC07 applied.

Top ^

82D224

Issue(s) Addressed: Introduced:

SN-006505 ALERT - PROC DB2UTIL passes incorrect datetime to DB2 when updating a DB2timestamp column 82D209
SN-007854 Running PROC DB2UTIL may cause a S0C4 abend 82D211
SN-006839 SAS DATETIME format is used in PROC DB2UTIL delete operations ratherthan the correct DB2 format 82D214
SN-008806 Non-zero return codes when executing PROC DB2UTIL do not set the jobreturn code to 4 82D217
SN-009054 ALERT - PROC DB2UTIL's SSID= option does not work correctly starting in Version8 82D218
SN-013018 ALERT - DB2UTIL passes incorrect value when updating a decimal variable 82D224

Select an Available Operating System:

MAINFRAME: OS/390

Top ^

82D225 was replaced by 82D226

82D226

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-007694^* NonStop Tandem LARGEINT columns causes problems with Access to ODBC V8.2on Windows 82D210
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-011355^* WARNING: SQL3107W There is at least one warning message in the messagefile received when using the bulkload feature of SAS/ACCESS 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
* 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

UNIX: HPUX_32bit_SAS, Solaris_32bit_SAS, AIX_32bit_SAS, Linux

ATTENTION (1): To complete the installation of this hot fix on Windows platforms, you must also download and install hot fix 82BC07 for Windows. This hot fix will NOT be fully functional without 82BC07 applied.
ATTENTION (2): The HP-UX version of this hot fix should only be applied to systems running HP-UX 11.x.

Top ^

SAS/ACCESS INTERFACE TO DB2 SERVER FOR VM

82SQ01

Issue(s) Addressed: Introduced:

SN-007855 FSEDIT on an access view for DB2 Server for VM will receive a -205 fromDB2 82SQ01

Select an Available Operating System:

MAINFRAME: CMS

Top ^

SAS/ACCESS INTERFACE TO CA-IDMS

82ID01

Issue(s) Addressed: Introduced:

SN-005057 IDMS DATA step interface INPUT statement cannot access record data pastoffset 1000 82ID01

Select an Available Operating System:

MAINFRAME: OS/390

Top ^

SAS/ACCESS INTERFACE TO INFORMIX

82IF01 was replaced by 82IF04

82IF02 was replaced by 82IF04

82IF03 was replaced by 82IF04

82IF04

Issue(s) Addressed: Introduced:

SN-005027 Unable to query an INFORMIX table containing a DATETIME precisiondatatype 82IF01
SN-005894 "ERROR: Informix EXECUTE Error: Already in transaction" is issued inSAS 8.2 82IF01
SN-007957 TEXT fields are truncated when using SAS/ACCESS Interface to Informixwith PROC SQL Passthrough 82IF02
SN-002782 Using the dbkey= option results in 0 rows being selected from a Informixtable 82IF03
SN-007212 INFORMIX table names cannot be longer than 18 characters when usingthe LIBNAME Access method 82IF04

Select an Available Operating System:

UNIX: HPUX_32bit_SAS, Solaris_32bit_SAS, AIX_32bit_SAS, Tru_64

Top ^

SAS/ACCESS INTERFACE TO MICROSOFT SQL SERVER

82MQ01

Issue(s) Addressed: Introduced:

SN-009609 SAS/ACCESS Interfaceto Microsoft SQL Server fails when running on HPUX11using the sabhhpt binary 82MQ01

Select an Available Operating System:

UNIX: HPUX_32bit_SAS

Top ^

SAS/ACCESS INTERFACE TO CA-OPENINGRES

82IG01 was replaced by 82IG02

82IG02

Issue(s) Addressed: Introduced:

SN-008460 SAS/ACCESS Interface to CA-OpenIngres does not support MULTINATIONAL4dates 82IG01
SN-010494 Deleting from an empty Ingres table generates an error instead of awarning 82IG02

Select an Available Operating System:

UNIX: Solaris_32bit_SAS

Top ^

SAS/ACCESS INTERFACE TO ODBC SERVER

82OD01 was replaced by 82OD09

82OD02 was replaced by 82OD09

82OD03 was replaced by 82OD09

82OD04 was replaced by 82OD09

82OD05 was replaced by 82OD09

82OD06 was replaced by 82OD09

82OD07 was replaced by 82OD09

82OD08 was replaced by 82OD09

82OD09

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-007694^* NonStop Tandem LARGEINT columns causes problems with Access to ODBC V8.2on Windows 82OD04
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-011355^* WARNING: SQL3107W There is at least one warning message in the messagefile received when using the bulkload feature of SAS/ACCESS 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
* 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

UNIX: HPUX_32bit_SAS, Solaris_32bit_SAS, AIX_32bit_SAS, Linux

ATTENTION (1): To complete the installation of this hot fix on Windows platforms, you must also download and install hot fix 82BC07 for Windows. This hot fix will NOT be fully functional without 82BC07 applied.
ATTENTION (2): The HP-UX version of this hot fix should only be applied to systems running HP-UX 11.x.

Top ^

SAS/ACCESS INTERFACE TO OLE DB

82OL01 was replaced by 82OL05

82OL02 was replaced by 82OL05

82OL03 was replaced by 82OL05

82OL04 was replaced by 82OL05

82OL05

Issue(s) Addressed: Introduced:

SN-004249 PROC EXPORT of a numeric variable causes missing data in MSAccess2000/XP file 82OL01
SN-005811 Syntax error when using WGDB option with PROC IMPORT procedure 82OL01
SN-005812 PROC IMPORT fails when importing Microsoft files when MDAC 2.70 isinstalled on the machine 82OL01
SN-004195 PROC IMPORT is not setting the SYSLAST and SYSDSN Macros Correctly 82OL01
SN-005506 Importing from Excel 97 or 2000 where the sheet name contains an &fails. 82OL01
SN-006001 Access Interface to OLEDB will fail when attempting to call a storedprocedure with 'command was not prepared' 82OL01
SN-000494 Can SAS access Microsoft SQL Server OLAP cubes? 82OL01
SN-007399 ALERT - Version 8 import procedure might hang after SAS 9 Early AdopterRelease installed 82OL01
SN-007477 Error using Access to OLEDB w/MS V5 DB2OLEDB Provider to access data onOS390 82OL03
SN-007806 Accessing OLAP cube that contains a currency type will return $0 82OL04
SN-005809 ERROR: Problem removing original table, when using PROC EXPORT to createan MSACCESS table 82OL05
SN-010553 Unable to list tables or retrieve data using the Ihistorian OLE DBprovider 82OL05

Select an Available Operating System:

PC: Windows

Top ^

SAS/ACCESS INTERFACE TO ORACLE

82OC01 was replaced by 82OC08

82OC02

Issue(s) Addressed: Introduced:

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

Select an Available Operating System:

VMS: OpenVMS_Alpha

Top ^

82OC03 was replaced by 82OC08

82OC04 was replaced by 82OC08

82OC05 was replaced by 82OC08

82OC06 was replaced by 82OC08

82OC07

Issue(s) Addressed: Introduced:

SN-005272 V8 formats are not compatible with V6 formats with SQL Pass-throughfacility for Char and Number 82OC01
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

Select an Available Operating System:

VMS: OpenVMS_Alpha

Top ^

82OC08

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

Select an Available Operating System:

PC: Windows

UNIX: HPUX_32bit_SAS, Solaris_32bit_SAS, AIX_32bit_SAS, Tru_64, Solaris_64bit_SAS, Linux

Top ^

SAS/ACCESS INTERFACE TO ORACLE RDB

82RB01 was replaced by 82RB02

82RB02

Issue(s) Addressed: Introduced:

SN-009955 WHERE clause may not be passed to Rdb database for processing, causingpoor performance 82RB01
SN-012091 "Unterminated string" and "Access violation" errors when runningSAS/ACCESS Interface to Oracle/Rdb 82RB02

Select an Available Operating System:

VMS: OpenVMS_Alpha, OpenVMS_VAX

Top ^

SAS/ACCESS INTERFACE TO PC FILE FORMATS

82PF01 was replaced by 82PF05

82PF02 was replaced by 82PF05

82PF03 was replaced by 82PF05

82PF04 was replaced by 82PF05

82PF05

Issue(s) Addressed: Introduced:

SN-004249 PROC EXPORT of a numeric variable causes missing data in MSAccess2000/XP file 82PF01
SN-005811 Syntax error when using WGDB option with PROC IMPORT procedure 82PF01
SN-005812 PROC IMPORT fails when importing Microsoft files when MDAC 2.70 isinstalled on the machine 82PF01
SN-004195 PROC IMPORT is not setting the SYSLAST and SYSDSN Macros Correctly 82PF01
SN-005506 Importing from Excel 97 or 2000 where the sheet name contains an &fails. 82PF01
SN-006001 Access Interface to OLEDB will fail when attempting to call a storedprocedure with 'command was not prepared' 82PF01
SN-000494 Can SAS access Microsoft SQL Server OLAP cubes? 82PF01
SN-007399 ALERT - Version 8 import procedure might hang after SAS 9 Early AdopterRelease installed 82PF01
SN-007477 Error using Access to OLEDB w/MS V5 DB2OLEDB Provider to access data onOS390 82PF03
SN-007806 Accessing OLAP cube that contains a currency type will return $0 82PF04
SN-005809 ERROR: Problem removing original table, when using PROC EXPORT to createan MSACCESS table 82PF05
SN-010553 Unable to list tables or retrieve data using the Ihistorian OLE DBprovider 82PF05

Select an Available Operating System:

PC: Windows

Top ^

SAS/ACCESS INTERFACE TO PEOPLESOFT

82PE01

Issue(s) Addressed: Introduced:

SN-005945 SAS/ACCESS Interface to PeopleSoft abends during Create PSFIELDS inmetadata extraction 82PE01

Select an Available Operating System:

PC: Windows

UNIX: HPUX_32bit_SAS, Solaris_32bit_SAS, AIX_32bit_SAS, Tru_64

Top ^

SAS/ACCESS INTERFACE TO R/3

82R301

Issue(s) Addressed: Introduced:

SN-006980 Error using transport files to install SAP objects for SAS/ACCESSInterface to R/3 82R301
SN-007683 Transport files to load SAP ABAP objects are available for SAS/ACCESSInterface to SAP BW 82R301
SN-010245 Function module Z_SAS_IOBJ_GETDETAIL_LIST for SAS/ACCESS Interface toSAP BW increases performance for extraction of metadata aboutInfoObjects 82R301

Select an Available Operating System:

PC: Windows

UNIX: HPUX_32bit_SAS, Solaris_32bit_SAS, AIX_32bit_SAS, Tru_64

Top ^

82R302

Issue(s) Addressed: Introduced:

SN-007103 Extract job continues to run when error encountered without abending inACCESS to R/3 82R302

Select an Available Operating System:

PC: Windows

UNIX: HPUX_32bit_SAS, Solaris_32bit_SAS, AIX_32bit_SAS, Tru_64

Top ^

82R303

Issue(s) Addressed: Introduced:

SN-007638 CALLRFC function used within SAS/ACCESS to R/3 and SAS/ACCESS to SAP BWfails for SAP Version 6.x 82R303

Select an Available Operating System:

PC: Windows

UNIX: HPUX_32bit_SAS, Solaris_32bit_SAS, AIX_32bit_SAS, Tru_64

Top ^

SAS/ACCESS INTERFACE TO SAP BW

82BW01 was replaced by 82BW03

82BW02 was replaced by 82BW03

82BW03

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

Select an Available Operating System:

PC: Windows

UNIX: HPUX_32bit_SAS, Solaris_32bit_SAS, AIX_32bit_SAS, Tru_64

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.

Top ^

SAS/ACCESS INTERFACE TO SYBASE

82SB01 was replaced by 82SB12

82SB02 was replaced by 82SB12

82SB03 was replaced by 82SB12

82SB04 was replaced by 82SB12

82SB05 was replaced by 82SB12

82SB06 was replaced by 82SB12

82SB07 was replaced by 82SB12

82SB08 was replaced by 82SB12

82SB09 was replaced by 82SB12

82SB10 was replaced by 82SB12

82SB11

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-008034^* Segmentation Violation in SAS/ACCESS Interface to Sybase when loadinga table with BULKCOPY on Solaris 82SB03
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-009951^* New image for Sybase 12.5 on HPUX 82SB07
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
* 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: AIX_32bit_SAS

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.

Top ^

82SB12

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-008034^* Segmentation Violation in SAS/ACCESS Interface to Sybase when loadinga table with BULKCOPY on Solaris 82SB03
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-009951^* New image for Sybase 12.5 on HPUX 82SB07
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
* 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

UNIX: HPUX_32bit_SAS, Solaris_32bit_SAS, AIX_32bit_SAS, Tru_64, Linux

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.

Top ^

SAS/ACCESS INTERFACE TO SYSTEM 2000

82S201

Issue(s) Addressed: Introduced:

SN-005982 System 0C4 abends can occur in applications that apply WHERE clausecriteria to System 2000 view descriptor references 82S201
SN-005981 Cannot create valid SAS/ACCESS descriptors for Release 11.6 of System2000 82S201

Select an Available Operating System:

MAINFRAME: OS/390

Top ^

SAS/ACCESS INTERFACE TO TERADATA

82TE01 was replaced by 82TE09

82TE02 was replaced by 82TE09

82TE03 was replaced by 82TE09

82TE04 was replaced by 82TE09

82TE05

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

Select an Available Operating System:

UNIX: AIX_32bit_SAS

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.

Top ^

82TE06 was replaced by 82TE09

82TE07 was replaced by 82TE09

82TE08

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
* 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: OS/390

PC: Windows

UNIX: HPUX_32bit_SAS, Solaris_32bit_SAS, AIX_32bit_SAS

ATTENTION: This hot fix should only be applied to systems running AIX 5.1 or greater.
ATTENTION: This hot fix should only be downloaded by customers running HP-UX, Solaris, AIX, Windows, and OS/390. Customers running ABI+ for Intel Architecture should download 82te09 instead.

Top ^

82TE09

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


Hot Fix Download Quick Links:
SAS/ACCESS INTERFACE TO ADABAS	SAS/ACCESS INTERFACE TO CA-DATACOM/DB	SAS/ACCESS INTERFACE TO DB2	SAS/ACCESS INTERFACE TO DB2 SERVER FOR VM
SAS/ACCESS INTERFACE TO CA-IDMS	SAS/ACCESS INTERFACE TO INFORMIX	SAS/ACCESS INTERFACE TO MICROSOFT SQL SERVER	SAS/ACCESS INTERFACE TO CA-OPENINGRES
SAS/ACCESS INTERFACE TO ODBC SERVER	SAS/ACCESS INTERFACE TO OLE DB	SAS/ACCESS INTERFACE TO ORACLE	SAS/ACCESS INTERFACE TO ORACLE RDB
SAS/ACCESS INTERFACE TO PC FILE FORMATS	SAS/ACCESS INTERFACE TO PEOPLESOFT	SAS/ACCESS INTERFACE TO R/3	SAS/ACCESS INTERFACE TO SAP BW
SAS/ACCESS INTERFACE TO SYBASE	SAS/ACCESS INTERFACE TO SYSTEM 2000	SAS/ACCESS INTERFACE TO TERADATA	SAS/ASSIST
BASE SAS	SAS/CONNECT	SAS/EIS	SAS ENTERPRISE MINER
SAS/ETS	SAS/FSP	SAS/GENETICS	SAS/GRAPH
SAS/IML	SAS INTEGRATION TECHNOLOGIES	SAS/INTRNET	SAS/MDDB SERVER
SAS/QC	RISK DIMENSIONS	SAS/SHARE	SAS/STAT
SAS TEXT MINER	SAS WAREHOUSE ADMINISTRATOR	WEBHOUND
Other Hot Fix Links:
Hot Fixes for Additional SAS Products and Solutions
National Language Support Hot Fixes

82AD01
Issue(s) Addressed:		Introduced:
SN-008569	ADABAS view descriptor subset WHERE clause GT 72 characters in length isnot passed to the data base	82AD01
SN-006013	SUBSET WHERE used in ADABAS access descriptor returns zero rows	82AD01
SN-008697	NAT3061 error when creating ADABAS descriptor using 4 digit SYSFILE parm	82AD01
Select an Available Operating System:
MAINFRAME:	OS/390

82AD02
Issue(s) Addressed:		Introduced:
SN-009206	Error: Periodic group / multiple value status has changed for field	82AD02
Select an Available Operating System:
MAINFRAME:	OS/390

82DD01
Issue(s) Addressed:		Introduced:
SN-005983	'Unsupported DATADICTIONARY Version' message issued for Release 10 ofCA-DATACOM/DB	82DD01
Select an Available Operating System:
MAINFRAME:	OS/390

82D213
Issue(s) Addressed:		Introduced:
SN-006469	Using NULLS statement in PROC DBLOAD to define a DB2 column as NOT NULLWITH DEFAULT does not work	82D205
SN-005504	ALERT - Including an SQL statement in PROC DB2UTIL or PROC DBLOAD may causewrong table to be updated	82D213
SN-006484	PROC DB2UTIL can insert garbage into DB2 columns that are defined asVARCHAR	82D213
Select an Available Operating System:
MAINFRAME:	OS/390

82D223
Issue(s) Addressed:		Introduced:
SN-004819	SAS/ACCESS view referencing DB2 table with character column wider than200 bytes may produce errors	82D201
SN-004982	CPU time significantly higher with SQL pass-through to DB2	82D201
SN-005647	ALERT - Using LOCATION= in PROC ACCESS can cause error or incorrecttable to be used	82D202
SN-006736	Specifying DBKEY= to reference a composite index can produce one ofseveral error messages	82D206
SN-007182	YEAR, MONTH and DAY functions may be passed to DB2	82D207
SN-007857	Performance problem when using a libref pointing to a remote locationthat includes the option preserve_names=yes	82D212
SN-007858	Incorrect list of tables is displayed when a libref is pointing to aremote location	82D212
SN-008508	Specifying a composite index with DBKEY= may cause a S0C4 abend	82D215
SN-007859	Setting a special register via DBCONINIT does not always work	82D219
SN-009720	Extra and unexpected commits may occur after applying DB2 hotfix	82D219
SN-002892	DB2 SQLCODE +535 received updating DB2 table	82D221
SN-013020	Performance issues with regard to padding of decimals	82D223
Select an Available Operating System:
MAINFRAME:	OS/390
ATTENTION: To complete the installation of this hot fix, you must also download and install hot fix 82BC07 for OS/390. This hot fix will NOT be fully functional without both 82D223 and 82BC07 applied.

82D224
Issue(s) Addressed:		Introduced:
SN-006505	ALERT - PROC DB2UTIL passes incorrect datetime to DB2 when updating a DB2timestamp column	82D209
SN-007854	Running PROC DB2UTIL may cause a S0C4 abend	82D211
SN-006839	SAS DATETIME format is used in PROC DB2UTIL delete operations ratherthan the correct DB2 format	82D214
SN-008806	Non-zero return codes when executing PROC DB2UTIL do not set the jobreturn code to 4	82D217
SN-009054	ALERT - PROC DB2UTIL's SSID= option does not work correctly starting in Version8	82D218
SN-013018	ALERT - DB2UTIL passes incorrect value when updating a decimal variable	82D224
Select an Available Operating System:
MAINFRAME:	OS/390

82D226
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-007694^*	NonStop Tandem LARGEINT columns causes problems with Access to ODBC V8.2on Windows	82D210
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-011355^*	WARNING: SQL3107W There is at least one warning message in the messagefile received when using the bulkload feature of SAS/ACCESS	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
* 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
UNIX:	HPUX_32bit_SAS, Solaris_32bit_SAS, AIX_32bit_SAS, Linux
ATTENTION (1): To complete the installation of this hot fix on Windows platforms, you must also download and install hot fix 82BC07 for Windows. This hot fix will NOT be fully functional without 82BC07 applied. ATTENTION (2): The HP-UX version of this hot fix should only be applied to systems running HP-UX 11.x.

82SQ01
Issue(s) Addressed:		Introduced:
SN-007855	FSEDIT on an access view for DB2 Server for VM will receive a -205 fromDB2	82SQ01
Select an Available Operating System:
MAINFRAME:	CMS

82ID01
Issue(s) Addressed:		Introduced:
SN-005057	IDMS DATA step interface INPUT statement cannot access record data pastoffset 1000	82ID01
Select an Available Operating System:
MAINFRAME:	OS/390

82IF04
Issue(s) Addressed:		Introduced:
SN-005027	Unable to query an INFORMIX table containing a DATETIME precisiondatatype	82IF01
SN-005894	"ERROR: Informix EXECUTE Error: Already in transaction" is issued inSAS 8.2	82IF01
SN-007957	TEXT fields are truncated when using SAS/ACCESS Interface to Informixwith PROC SQL Passthrough	82IF02
SN-002782	Using the dbkey= option results in 0 rows being selected from a Informixtable	82IF03
SN-007212	INFORMIX table names cannot be longer than 18 characters when usingthe LIBNAME Access method	82IF04
Select an Available Operating System:
UNIX:	HPUX_32bit_SAS, Solaris_32bit_SAS, AIX_32bit_SAS, Tru_64

82MQ01
Issue(s) Addressed:		Introduced:
SN-009609	SAS/ACCESS Interfaceto Microsoft SQL Server fails when running on HPUX11using the sabhhpt binary	82MQ01
Select an Available Operating System:
UNIX:	HPUX_32bit_SAS

82IG02
Issue(s) Addressed:		Introduced:
SN-008460	SAS/ACCESS Interface to CA-OpenIngres does not support MULTINATIONAL4dates	82IG01
SN-010494	Deleting from an empty Ingres table generates an error instead of awarning	82IG02
Select an Available Operating System:
UNIX:	Solaris_32bit_SAS

82OD09
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-007694^*	NonStop Tandem LARGEINT columns causes problems with Access to ODBC V8.2on Windows	82OD04
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-011355^*	WARNING: SQL3107W There is at least one warning message in the messagefile received when using the bulkload feature of SAS/ACCESS	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
* 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
UNIX:	HPUX_32bit_SAS, Solaris_32bit_SAS, AIX_32bit_SAS, Linux
ATTENTION (1): To complete the installation of this hot fix on Windows platforms, you must also download and install hot fix 82BC07 for Windows. This hot fix will NOT be fully functional without 82BC07 applied. ATTENTION (2): The HP-UX version of this hot fix should only be applied to systems running HP-UX 11.x.

82OL05
Issue(s) Addressed:		Introduced:
SN-004249	PROC EXPORT of a numeric variable causes missing data in MSAccess2000/XP file	82OL01
SN-005811	Syntax error when using WGDB option with PROC IMPORT procedure	82OL01
SN-005812	PROC IMPORT fails when importing Microsoft files when MDAC 2.70 isinstalled on the machine	82OL01
SN-004195	PROC IMPORT is not setting the SYSLAST and SYSDSN Macros Correctly	82OL01
SN-005506	Importing from Excel 97 or 2000 where the sheet name contains an &fails.	82OL01
SN-006001	Access Interface to OLEDB will fail when attempting to call a storedprocedure with 'command was not prepared'	82OL01
SN-000494	Can SAS access Microsoft SQL Server OLAP cubes?	82OL01
SN-007399	ALERT - Version 8 import procedure might hang after SAS 9 Early AdopterRelease installed	82OL01
SN-007477	Error using Access to OLEDB w/MS V5 DB2OLEDB Provider to access data onOS390	82OL03
SN-007806	Accessing OLAP cube that contains a currency type will return $0	82OL04
SN-005809	ERROR: Problem removing original table, when using PROC EXPORT to createan MSACCESS table	82OL05
SN-010553	Unable to list tables or retrieve data using the Ihistorian OLE DBprovider	82OL05
Select an Available Operating System:
PC:	Windows

82OC02
Issue(s) Addressed:		Introduced:
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
Select an Available Operating System:
VMS:	OpenVMS_Alpha

82OC07
Issue(s) Addressed:		Introduced:
SN-005272	V8 formats are not compatible with V6 formats with SQL Pass-throughfacility for Char and Number	82OC01
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
Select an Available Operating System:
VMS:	OpenVMS_Alpha

82OC08
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
Select an Available Operating System:
PC:	Windows
UNIX:	HPUX_32bit_SAS, Solaris_32bit_SAS, AIX_32bit_SAS, Tru_64, Solaris_64bit_SAS, Linux

82RB02
Issue(s) Addressed:		Introduced:
SN-009955	WHERE clause may not be passed to Rdb database for processing, causingpoor performance	82RB01
SN-012091	"Unterminated string" and "Access violation" errors when runningSAS/ACCESS Interface to Oracle/Rdb	82RB02
Select an Available Operating System:
VMS:	OpenVMS_Alpha, OpenVMS_VAX

82PF05
Issue(s) Addressed:		Introduced:
SN-004249	PROC EXPORT of a numeric variable causes missing data in MSAccess2000/XP file	82PF01
SN-005811	Syntax error when using WGDB option with PROC IMPORT procedure	82PF01
SN-005812	PROC IMPORT fails when importing Microsoft files when MDAC 2.70 isinstalled on the machine	82PF01
SN-004195	PROC IMPORT is not setting the SYSLAST and SYSDSN Macros Correctly	82PF01
SN-005506	Importing from Excel 97 or 2000 where the sheet name contains an &fails.	82PF01
SN-006001	Access Interface to OLEDB will fail when attempting to call a storedprocedure with 'command was not prepared'	82PF01
SN-000494	Can SAS access Microsoft SQL Server OLAP cubes?	82PF01
SN-007399	ALERT - Version 8 import procedure might hang after SAS 9 Early AdopterRelease installed	82PF01
SN-007477	Error using Access to OLEDB w/MS V5 DB2OLEDB Provider to access data onOS390	82PF03
SN-007806	Accessing OLAP cube that contains a currency type will return $0	82PF04
SN-005809	ERROR: Problem removing original table, when using PROC EXPORT to createan MSACCESS table	82PF05
SN-010553	Unable to list tables or retrieve data using the Ihistorian OLE DBprovider	82PF05
Select an Available Operating System:
PC:	Windows

82PE01
Issue(s) Addressed:		Introduced:
SN-005945	SAS/ACCESS Interface to PeopleSoft abends during Create PSFIELDS inmetadata extraction	82PE01
Select an Available Operating System:
PC:	Windows
UNIX:	HPUX_32bit_SAS, Solaris_32bit_SAS, AIX_32bit_SAS, Tru_64

82R301
Issue(s) Addressed:		Introduced:
SN-006980	Error using transport files to install SAP objects for SAS/ACCESSInterface to R/3	82R301
SN-007683	Transport files to load SAP ABAP objects are available for SAS/ACCESSInterface to SAP BW	82R301
SN-010245	Function module Z_SAS_IOBJ_GETDETAIL_LIST for SAS/ACCESS Interface toSAP BW increases performance for extraction of metadata aboutInfoObjects	82R301
Select an Available Operating System:
PC:	Windows
UNIX:	HPUX_32bit_SAS, Solaris_32bit_SAS, AIX_32bit_SAS, Tru_64

82R302
Issue(s) Addressed:		Introduced:
SN-007103	Extract job continues to run when error encountered without abending inACCESS to R/3	82R302
Select an Available Operating System:
PC:	Windows
UNIX:	HPUX_32bit_SAS, Solaris_32bit_SAS, AIX_32bit_SAS, Tru_64

82R303
Issue(s) Addressed:		Introduced:
SN-007638	CALLRFC function used within SAS/ACCESS to R/3 and SAS/ACCESS to SAP BWfails for SAP Version 6.x	82R303
Select an Available Operating System:
PC:	Windows
UNIX:	HPUX_32bit_SAS, Solaris_32bit_SAS, AIX_32bit_SAS, Tru_64

82BW03
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
Select an Available Operating System:
PC:	Windows
UNIX:	HPUX_32bit_SAS, Solaris_32bit_SAS, AIX_32bit_SAS, Tru_64
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
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-008034^*	Segmentation Violation in SAS/ACCESS Interface to Sybase when loadinga table with BULKCOPY on Solaris	82SB03
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-009951^*	New image for Sybase 12.5 on HPUX	82SB07
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
* 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:	AIX_32bit_SAS
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
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-008034^*	Segmentation Violation in SAS/ACCESS Interface to Sybase when loadinga table with BULKCOPY on Solaris	82SB03
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-009951^*	New image for Sybase 12.5 on HPUX	82SB07
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
* 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
UNIX:	HPUX_32bit_SAS, Solaris_32bit_SAS, AIX_32bit_SAS, Tru_64, Linux
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.

82S201
Issue(s) Addressed:		Introduced:
SN-005982	System 0C4 abends can occur in applications that apply WHERE clausecriteria to System 2000 view descriptor references	82S201
SN-005981	Cannot create valid SAS/ACCESS descriptors for Release 11.6 of System2000	82S201
Select an Available Operating System:
MAINFRAME:	OS/390

82TE05
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
Select an Available Operating System:
UNIX:	AIX_32bit_SAS
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
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
* 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:	OS/390
PC:	Windows
UNIX:	HPUX_32bit_SAS, Solaris_32bit_SAS, AIX_32bit_SAS
ATTENTION: This hot fix should only be applied to systems running AIX 5.1 or greater. ATTENTION: This hot fix should only be downloaded by customers running HP-UX, Solaris, AIX, Windows, and OS/390. Customers running ABI+ for Intel Architecture should download 82te09 instead.