Specifies whether the SAS/ACCESS engine functions
like a random access engine for the scope of the LIBNAME statement.
Valid in:
SAS/ACCESS LIBNAME statement
Default:
NO
Data source:
Aster nCluster,
DB2 under UNIX and PC Hosts, DB2 under z/OS, Greenplum, HP Neoview,
Informix, Microsoft SQL Server, MySQL, Netezza, ODBC, OLE DB, Oracle,
Sybase, Sybase IQ, Teradata
specifies that the
SAS/ACCESS engine functions as an RMOD engine, which means that your
data is protected by the normal data protection that SAS provides.
YES
specifies that the
SAS/ACCESS engine functions like a random access engine when rereading
a row so that you cannot guarantee that the same row is returned.
For example, if you read row 5 and someone else deletes it, you read a different row the
next time you read row 5. You have the
potential for data integrity exposures within the scope of your SAS
session.
Details
CAUTION:
Using REREAD_EXPOSURE=
could cause data integrity exposures.
HP
Neoview, Netezza, ODBC, OLE DB: If you set this
option to YES, it is advisable to set UPDATE_ISOLATION_LEVEL=S (serializable)
to avoid data integrity problems.
Oracle: If
you set this option to YES, it is advisable to set UPDATE_LOCK_TYPE=TABLE
to avoid data integrity problems.