topic Tables cannot be openend by other users when library is checked out in Administration and Deployment

Tables cannot be openend by other users when library is checked out

ericm — Fri, 02 Jul 2021 12:00:59 GMT

Hi,

We've a strange problem. When a team member checks out a library other members are not able to open the tables which are connected to this library. The team member who checked it out still can.

Is there a solution for this problem? Or is it a bug?

We are running SAS 9.4 M6 with SAS DI 4.904 on a Unix install.

We haven't seen this issue on our previous Windows installation.

Thanks

Re: Tables cannot be openend by other users when library is checked out

Sajid01 — Fri, 02 Jul 2021 13:20:57 GMT

Please see this forum topic for a resolution to your issue

https://communities.sas.com/t5/SAS-Programming/SAS-DI-jobs-trying-to-update-the-same-dataset-by-multiple-SAS/td-p/561917

Re: Tables cannot be openend by other users when library is checked out

Kurt_Bremser — Fri, 02 Jul 2021 14:15:12 GMT

If other users can't read the datasets, then this user's umask setting may be too restrictive (0033 or 0077).

Re: Tables cannot be openend by other users when library is checked out

SASKiwi — Sun, 04 Jul 2021 23:19:51 GMT

What do you mean by checked out? Is this something to do with version control or just assigning a LIBNAME pointing at that SAS library?

Re: Tables cannot be openend by other users when library is checked out

Patrick — Mon, 05 Jul 2021 06:55:45 GMT

Can't remember having seen that before. Feels like a Metadata read permission issue. Did you already check the metadata server log?

If this is not a pre-assigned library: Does the libname get generated in the code or what do you get there?

Re: Tables cannot be openend by other users when library is checked out

ericm — Mon, 12 Jul 2021 09:51:15 GMT

It is a metadata issue indeed. In the development environment we're using the checkin/checkout mechanism. When a library is checked out by a user all other users in the development environment are not able to open tables which are connected to that library. When the library is checked in everybody can open the tables again.

We didn't check the metadata log. So that's a good suggestion.