120 READ_MODE_WAIT= LIBNAME Option Chapter 9
valid in the DB2 OS/390, DB2 UNIX/PC, ODBC, Oracle, Microsoft SQL Server, and
Teradata interfaces.)
NOLOCK
does not lock the DBMS table, pages, or rows during a read transaction. (This value
is valid in the Oracle and SYBASE interfaces, in the ODBC and Microsoft SQL
Server interfaces when using the Microsoft SQLServer driver, and in the OLE DB
interface when using the Microsoft SQL Server provider.)
VIEW
locks the entire DBMS view. (This value is valid in the Teradata interface.)
Details
If you omit READ_LOCK_TYPE=, the default is the DBMS’ default action. You can set
a lock for one DBMS table by using the data set option or for a group of DBMS tables
by using the LIBNAME option.
See the documentation for your SAS/ACCESS interface for additional details.
Example
In the following example, the libref MYDBLIB uses the SAS/ACCESS interface to
Oracle to connect to an Oracle database. USER=, PASSWORD=, and PATH= are
SAS/ACCESS connection options. The LIBNAME options specify that row-level locking
is used when data is read or updated:
libname mydblib oracle user=testuser password=testpass
path=myorapth read_lock_type=row update_lock_type=row;
See Also
To apply this option to an individual data set, see the data set option
“READ_LOCK_TYPE= Data Set Option” on page 206.
READ_MODE_WAIT= LIBNAME Option
Specifies during SAS/ACCESS read operations whether Teradata should wait to acquire a lock or
should fail the request when the DBMS resource is already locked by a different user
Valid in: the SAS/ACCESS LIBNAME statement
DBMS support: Teradata
Default value:
none
Syntax
READ_MODE_WAIT= YES|NO
Syntax Description
