BookmarkSubscribeRSS Feed
Lakshmi_G90
Calcite | Level 5

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.

1 REPLY 1
Patrick
Opal | Level 21

@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/1366... 

 

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

 

Ready to join fellow brilliant minds for the SAS Hackathon?

Build your skills. Make connections. Enjoy creative freedom. Maybe change the world. Registration is now open through August 30th. Visit the SAS Hackathon homepage.

Register today!
Mastering the WHERE Clause in PROC SQL

SAS' Charu Shankar shares her PROC SQL expertise by showing you how to master the WHERE clause using real winter weather data.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 1 reply
  • 1663 views
  • 0 likes
  • 2 in conversation