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 |
|---|---|
| Category: | Data Set Control |
| Alias: | READ_EXPOSURE_OK= [Oracle] |
| Default: | NO |
| Data source: | Amazon Redshift, Aster, DB2 under UNIX and PC Hosts, DB2 under z/OS, Greenplum, HAWQ, Impala, Informix, Microsoft SQL Server, MySQL, Netezza, ODBC, OLE DB, Oracle, PostgreSQL, SAP ASE, SAP HANA, SAP IQ, Snowflake, Teradata, Vertica, Yellowbrick |
| Note: | Support for Yellowbrick was added in SAS 9.4M7. |
| See: | UPDATE_ISOLATION_LEVEL= LIBNAME option, UPDATE_LOCK_TYPE= LIBNAME option |
Table of Contents
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.
specifies that the SAS/ACCESS engine functions as a serial engine with limited random access capabilities. In this case, your data is protected by the normal data protection that SAS provides.
CAUTION
Using REREAD_EXPOSURE= could cause data integrity exposures.
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.