ERROR: MEMBER lock is not available for STAGE.ERAS0001_R.DATA, lock held by SYSTEM(ADMUSER1)

Lakshmi_G90 — Mon, 13 May 2019 06:20:30 GMT

Hi All,

Hope you're Doing Well !!

In our environment SAS is installed on Windows 2012 R2. Now a days we are frequently experiencing the scheduled jobs failure due to the MEMBER lock is not available on the particular tables in our Production environment.

This time we got the below error.

ERROR: MEMBER lock is not available for STAGE.ERAS0001_R.DATA, lock held by SYSTEM(ADMUSER1) connection ID 66648736.

Anyone can please suggest us how to find out the user who locked the table and how to kill the sessions.

My user id account is holding the all admin privileges to do the above tasks.

Please help us out.

Re: ERROR: MEMBER lock is not available for STAGE.ERAS0001_R.DATA, lock held by SYSTEM(ADMUSER1)

Patrick — Mon, 13 May 2019 06:49:58 GMT

@Lakshmi_G90

That's more a Windows than a SAS question. May be the following discussion will give you the necessary pointers.

https://communities.sas.com/t5/SAS-Procedures/How-to-find-which-user-has-a-lock-on-a-table/td-p/136654

IF these locks are only temporarily (i.e. concurrent sessions updating some control table) then also consider using libname option FILEOCKWAIT.

topic ERROR: MEMBER lock is not available for STAGE.ERAS0001_R.DATA, lock held by SYSTEM(ADMUSER1) in New SAS User

ERROR: MEMBER lock is not available for STAGE.ERAS0001_R.DATA, lock held by SYSTEM(ADMUSER1)

Re: ERROR: MEMBER lock is not available for STAGE.ERAS0001_R.DATA, lock held by SYSTEM(ADMUSER1)