I'm converting SAS code with PROC SQL statements where the back end is moving from DB2 to Oracle. My Base SAS is 9.4
The existing DB2 statements use FOR FETCH ONLY WITH UR, which I understand allows this code to avoid record locks with other users and potentially accepts some "out of date" data when accessing records which others may be simultaneously updating.
In the Oracle environment will the LIBNAME option READ_LOCK_TYPE=NOLOCK provide the equivalent locking control?
FOR FETCH ONLY WITH UR is IBM DB2-code for fetching uncommited changes from other sessions.
FOR FETCH ONLY - means the cursor is read only, issues different types of locks and does not allow for update.
WITH UR - means instead of retrieving only committed work, your SELECT or FETCH will also retrieve rows that have not been committed by other tasks.
This sort of "Dirty reads" is not allowed in Oracle.
FOR FETCH ONLY WITH UR is IBM DB2-code for fetching uncommited changes from other sessions.
FOR FETCH ONLY - means the cursor is read only, issues different types of locks and does not allow for update.
WITH UR - means instead of retrieving only committed work, your SELECT or FETCH will also retrieve rows that have not been committed by other tasks.
This sort of "Dirty reads" is not allowed in Oracle.
Don't miss out on SAS Innovate - Register now for the FREE Livestream!
Can't make it to Vegas? No problem! Watch our general sessions LIVE or on-demand starting April 17th. Hear from SAS execs, best-selling author Adam Grant, Hot Ones host Sean Evans, top tech journalist Kara Swisher, AI expert Cassie Kozyrkov, and the mind-blowing dance crew iLuminate! Plus, get access to over 20 breakout sessions.
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.