SAS/ACCESS 9.2 for Relational Databases: Reference, Fourth Edition

180 REREAD_EXPOSURE= LIBNAME Option 4 Chapter 10REREAD_EXPOSURE= LIBNAME OptionSpecifies whether the SAS/ACCESS engine functions like a random access engine for the scope ofthe LIBNAME statement.Default value: NOValid in: SAS/ACCESS LIBNAME statementDBMS support: 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, TeradataSyntaxREREAD_EXPOSURE=YES | NOSyntax DescriptionNOspecifies that the SAS/ACCESS engine functions as an RMOD engine, which meansthat your data is protected by the normal data protection that SAS provides.YESspecifies that the SAS/ACCESS engine functions like a random access engine whenrereading a row so that you cannot guarantee that the same row is returned. Forexample, if you read row 5 and someone else deletes it, then the next time you readrow 5, you read a different row. You have the potential for data integrity exposureswithin the scope of your SAS session.DetailsCAUTION:Using REREAD_EXPOSURE= could cause data integrity exposures. 4HP Neoview, Netezza, ODBC, and OLE DB: To avoid data integrity problems, it isadvisable to set UPDATE_ISOLATION_LEVEL=S (serializable) if you setREREAD_EXPOSURE=YES.Oracle: To avoid data integrity problems, it is advisable to setUPDATE_LOCK_TYPE=TABLE if you set REREAD_EXPOSURE=YES.See Also“UPDATE_ISOLATION_LEVEL= LIBNAME Option” on page 195“UPDATE_LOCK_TYPE= LIBNAME Option” on page 196