topic Re: Solving the error: A lock is not available for <dataset> in SAS Programming

Solving the error: A lock is not available for

wlierman — Wed, 08 Jul 2020 22:53:53 GMT

The log just returned the following error:

ERROR: A lock is not available for CCO_AREA.CCO_PCPCH_PROV_INTERLEAVED.DATA.
NOTE: The SAS System stopped processing this step because of errors.
NOTE: There were 1 observations read from the data set CCO_AREA.CCO_WITH_PCPCH.
NOTE: There were 1 observations read from the data set CCO_AREA.PROV_IN_STATE_W_NPI_ADDRESS.
WARNING: The data set CCO_AREA.CCO_PCPCH_PROV_INTERLEAVED was only partially opened and will not be saved.

I have never gotten this error before.

How can it be resolved?

Thank you for your help.

wlierman

Re: Solving the error: A lock is not available for

Jagadishkatam — Wed, 08 Jul 2020 23:00:12 GMT

This happens when the dataset you are trying to generate is already there and again you are running it to generate it but this time either you or someone else has opened it and it is unable to overwrite the opened dataset. In order to avoid this, the opened dataset has to be closed and the code for the same has to be run again.

Re: Solving the error: A lock is not available for

sustagens — Thu, 09 Jul 2020 00:42:50 GMT

If you are using SAS Enterprise Guide, go to Tools > View Open Data Sets, from there you can close any of the open datasets listed.

Re: Solving the error: A lock is not available for

SASKiwi — Thu, 09 Jul 2020 03:21:13 GMT

If your SAS server runs on Unix then this article by @Kurt_Bremser might be helpful: https://communities.sas.com/t5/SAS-Communities-Library/Avoiding-the-dreaded-quot-Dataset-is-locked-quot-ERROR/ta-p/653210

Re: Solving the error: A lock is not available for

wlierman — Thu, 09 Jul 2020 05:47:54 GMT

Hello,
The SAS server is located on Windows.Thanks.
wlierman

Re: Solving the error: A lock is not available for

wlierman — Thu, 09 Jul 2020 05:49:54 GMT

Thanks. I am working in a Windows environment with base SAS.
Is there a quick fix like that for SAS in Windows?
wlierman

Re: Solving the error: A lock is not available for

Kurt_Bremser — Thu, 09 Jul 2020 06:17:16 GMT

You say you work with a Windows server. How do you access that?

Re: Solving the error: A lock is not available for

Patrick — Thu, 09 Jul 2020 06:21:26 GMT

For SAS tables a process writing to a table locks it and any read access will lock the table for any other process trying to write to the table.

A table gets already locked for write access if you have it open somewhere - like if you've got two SAS sessions open with the table open.

There is no "fix" for that other than the person/session/process locking the table releasing it (i.e. closing the data grid in the session, libname blah clear, restart the SAS session, ....)

Re: Solving the error: A lock is not available for

wlierman — Thu, 09 Jul 2020 06:38:46 GMT

Thanks Patrick.

Re: Solving the error: A lock is not available for

wlierman — Sun, 12 Jul 2020 15:33:09 GMT

Hi Jagadishkatam,

I took your advice but rebooted and the problem was resolved.

Thanks.

wlierman

Re: Solving the error: A lock is not available for

bprice — Tue, 26 Jul 2022 19:10:43 GMT

Another cause of this error is something outside of SAS locking the file. If you are storing a large permanent SAS data set on a cloud server such as DropBox and trying to read/write to it often, the cloud service may have the file locked while it is pushing it to the cloud. For example, I've run into this when running a bootstrap routine that was trying to save iterations to a permanent data set on a cloud server and also when trying to sequentially update a large permanent data set multiple times during a SAS program. The solution is to just read/write everything locally and not save to the cloud based server until the end of the program.

Re: Solving the error: A lock is not available for

gregorywpower — Mon, 09 Oct 2023 16:06:42 GMT

For folks who find the above solutions unsatisfactory or you're wondering why LOCK LIBNAME LIST or LOCK LIBNAME QUERY is returning something to the effect of "You and nobody on your system is locking this dataset." and yet you run a PROC DATASET step and your files are still locked, you have more options.

You can check to see what files are in use by your system and terminate/kill those processes by process ID's.

For Unix Systems, you can use lsof -p | grep FILENAME which will spit out the process ID(s) using the file. You can kill that process with kill -v PROCESS_ID.

On Windows Servers, you have to install the Handle.exe program onto your compute server. Then you must open up the command prompt and run the handle.exe file and feed it the name of the table/file you are attempting to access. Which will provide the process ID(s) using the file. You open up Windows Task Manager, go to Details, sort your process IDs, and then you can kill that process.

It is highly likely this will damage the file, however, we can delete the file and replace it with SAS Data Integration Studio. Looking at the LIBNAME statement you can find where on your machine the file is and delete it. Then you use SAS Data Integration studio to recreate your corresponding library.