topic Converting SAS DB2 to Oracle - dealing with record locks in SAS Programming

Converting SAS DB2 to Oracle - dealing with record locks

MarkParent — Fri, 22 Sep 2017 13:03:34 GMT

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?

Re: Converting SAS DB2 to Oracle - dealing with record locks

JonLaurent — Mon, 25 Sep 2017 15:16:16 GMT

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.