Usage Note 6293: Read Isolation Level defaults to CR when using SAS/Access Interface to
DB2
When using SAS/Access Interface to DB2 with SAS 8.x, we hardcode the
value of the read isolation level to CR, since a bind is not performed
at SAS 8.x.
With SAS/Access Interface to DB2 on Unix at SAS 6.12, the
customer does a bind of SAS to each database, and we use the read
isolation level that DB2 defaults to or the value that it is set to in
the db2cli.ini file when the bind occurs.
With SAS V8.x, you must recode your SAS V6 programs and use the LIBNAME
engine in order to change the value of the read isolation level.
Hot fixes are available.
V8.2 SAS/ACCESS to DB2:
A Technical Support hot fix for this problem is available at:
http://www.sas.com/techsup/download/hotfix/82_sbcs_prod_list.html#82d204
V8.2 SAS/ACCESS to ODBC :
A Technical Support hot fix for this problem is available at:
http://www.sas.com/techsup/download/hotfix/82_sbcs_prod_list.html#82od02
Operating System and Release Information
| Product Family | Product | System | Reported Release | Fixed Release* |
| SAS System | SAS/ACCESS Interface to Oracle | 64-bit Enabled Solaris | 8.1 TS1M0 | |
| Solaris | 8.1 TS1M0 | |
| 64-bit Enabled AIX | 8.1 TS1M0 | |
| 64-bit Enabled HP-UX | 8.1 TS1M0 | |
| HP-UX | 8.1 TS1M0 | |
| Tru64 UNIX | 8.1 TS1M0 | 9 TS M0 |
| AIX | 8.1 TS1M0 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Type: | Usage Note |
| Priority: | high |
| Topic: | Data Management ==> Data Sources ==> External Databases ==> Oracle
SAS Reference ==> LIBNAME Engines
|
| Date Modified: | 2002-04-29 13:58:56 |
| Date Created: | 2001-11-15 13:52:50 |
