Getting error like "rename of temporary member for ...... failed file can be found in "

[Sai_001]

Hi All,

Can any one help to fix the issue which is happening due to .lck file extention. We are  using linux as OS. issue is users  other than the  owner (who created the dataset)  are not able to update the dataset. user is getting the error like "rename of temporary member for ...... failed file can be found in ". Only the the person who created the dataset is able to  update it eventhough the permission set as rw-rw-rw or rwxrwxrwx.

We are not  executing the huge file or no space issue.

[Astounding]

The permissions are fine. You need to know what .lck is telling you.

What should happen if one user is sorting the data set and another user tries to update the data set at the same time? The answer is that no one can access the data until PROC SORT completes. It doesn't matter whether the person who is sorting the data is the creator or any other authorized user. All other users are locked out (hence ".lck") until sorting completes.

SAS doesn't allow two people to update a data set at the same time.

[Sai_001]

Hi Astounding,

Thank you for the  details. the problem is there is no second person is  trying to run when  some one is trying.Each day we are taking turns to run it program and also make sure there is no held process for these datasets. Except the creator  others couldn't able to run it , its ended up with error like "rename of temXXXX" , ans this report was working fine for all of us until last month. Suddenly it is starts behaving  like this , no profile change happened recently for these users in SAs Management console. Is any folder permission, file permission needs to be checked ? file permission is rw-rw-rw and folder permission is rwxrwxrwxT.

[Tom]

---

@Sai_001 wrote:

Hi All,

Can any one help to fix the issue which is happening due to .lck file extention. We are  using linux as OS. issue is users  other than the  owner (who created the dataset)  are not able to update the dataset. user is getting the error like "rename of temporary member for ...... failed file can be found in ". Only the the person who created the dataset is able to  update it eventhough the permission set as rw-rw-rw or rwxrwxrwx.

We are not  executing the huge file or no space issue.

---

The normal SAS steps to create a new version of a dataset is to first make a NEW file and when that succeeds then to remove the original file and rename the NEW file to the target name.  So in general it is the permissions on the directory, not the file, that controls whether you can modify a dataset.

To prevent concurrent changes to a file SAS will also normally create semaphore files with .lck suffix.  The presence of this fill will let other SAS sessions know that the file is LOCKED and so cannot be changed. Once the update is done the lck file is removed. 

That said it is possible for SAS to crash in a way that leaves the .lck file that is created to prevent concurrent changes on the disk and the existance of that file will stop SAS from letting you update the file.  If you are sure that file is ok and no SAS processes are currently trying to update it then you can use operating system commands to remove the .lck file and you should be able to update the file again.

[Sai_001]

Hi Tom,

Thanks for  your valuable inputs. so you said the permisssion of the folder can play the role. In that case , this folder permission is rwxrwxrwxT and all the persons who are used to run this program were able to run till this month and this issue started since  fist of this month.

And also , even after removing the .lck filesfrom system, if the user tries again, same .lck files are gettting created and  program excution is ended up with the said error. the only user , who is the creator/ updated it lastly (before the .lck issue arrise ) nly can able to update it .

[SASKiwi]

Have there been any system changes made around the time the problem started? Some system event must have happened to cause the change.

[Sai_001]

OS is linux system and the server team confirms taht there is no configuration change happened in that month time. Is it possible to emntion few check points that  needs to be checked in server end regarding this so that , I can ask the team to take a look on those.

[Tom]

Check for some other software that might be locking the files.  Like a backup system or some type of crawler.

[Astounding]

Difficult to diagnose from a distance. If possible, try to narrow your focus by testing:

Can a non-creator run the program if all other users are logged off?

[Sai_001]

No, the non creator is getting the same error , even no one is logging or running it.

[Patrick]

@Sai_001 

It used to work and now doesn't anymore. This is a very clear indication that something in the environment changed.

Problem Note 62333 might give you some guidance. 

In my personal experience it's almost always antivirus software that interferes. Talk to your system admin if there has been a change lately. May be they haven't excluded .lck and .sas7bdat from scanning.

[Sai_001]

Hi Patrick,

In my personal experience it's almost always antivirus software that interferes. Talk to your system admin if there has been a change lately. May be they haven't excluded .lck and .sas7bdat from scanning.Is it applicable for linux environement ? application is running on linux server.

[Patrick]

---

@Sai_001 wrote:

Hi Patrick,

In my personal experience it's almost always antivirus software that interferes. Talk to your system admin if there has been a change lately. May be they haven't excluded .lck and .sas7bdat from scanning.Is it applicable for linux environement ? application is running on linux server.

---

Yes, that also applies to a Linux OS. Last time I've been in a project where some antivirus software locked tables the OS was RHEL.

[Tom]

---

@Patrick wrote:

---

@Sai_001 wrote:

Hi Patrick,

In my personal experience it's almost always antivirus software that interferes. Talk to your system admin if there has been a change lately. May be they haven't excluded .lck and .sas7bdat from scanning.Is it applicable for linux environement ? application is running on linux server.

---

Yes, that also applies to a Linux OS. Last time I've been in a project where some antivirus software locked tables the OS was RHEL.

---

Note also that these days the disks are not normally physically on the same machine the one you are running your code from. So the ant-virus software could be running on some other server and just scanning the disk that you are trying to use to write your SAS datasets.

[Sai_001]

Thanks Patric.

Will check in that aspect .