LIBNAME BASE | Tables does not appears

[MariaD]

Hi folks,

We have a really bizarre situation. We create a libname using SAS code, a simple BASE libname. When open the LIBANME o SAS EG (7.15) (SAS9.4M6 on Solaris) only a few tables appears. All the tables have the same OS permission. 

If we execute a proc contents or execute a data step with the table on set statement, works. But we can't see it on SAS EG interface. Any idea?

Regards

[Reeza]

Are the table names over 32 characters? Are you on unix, if so are all the table names are lower case?

[MariaD]

Yes, our server is Unix (Solaris). All table names have less than 32 characters and are in lowercase.

[Tom]

Not sure why it would impact the Entriprise Guide's ability to show a list of table, but check the setting of the FMTERR option.  If it is set to FMTERR trying changing it to NOFMTERR.  Other options to check VALIDVARNAME, VALIDMEMNAME.    If you have VALIDVARNAME set to V6 then names longer than 8 characters will be ignored.  Make sure none of the filenames start with a digit.

Also check results of running PROC CONTENTS on the libref.   Check that the libref is not pointing to the folder you think it is pointing to.  Also perhaps some of the datasets have zero variables?

[SASKiwi]

What happens if you read one of the tables that doesn't show and overwrite it like so:

data MyLib.MyTable;
  set MyLib.MyTable;
run;

Then refresh your EG server list, does the overwritten table now show?

[MariaD]

Hi @SASKiwi , 

I tried it but still no show...

Thanks

[SASKiwi]

@MariaD  - OK, try a copy to the WORK library, then refresh the WORK library in the server list - does it show?

data WORK.MyTable;
  set MyLib.MyTable;
run;

[Reeza]

Given that it works via code but not the GUI I think you should raise a ticket with Tech Support.

[JuanS_OCS]

Hi @MariaD ,

if you enable SAS EG Project Logging, the resulting log after you expand this library should give more information about the issue. When you run proc contents data=lib._all_; can you see any noticeable difference amongst the properties/attributes of the tables that appear, and the ones that cannot?

Reasons can be many. As an example, the last time I saw this kind of behavior was cause due to the fact that the workspace server is in a specific locale/encoding, and then some tables were created with a compatible encoding/locale, but some others were generated using a different encoding/locale.

[MariaD]

Thanks all for your answers. We compare the results of proc contents and all the results are the same.

If we copy or create a new table to work area, for example, the new table opens fine and we can visualize it ok. 

All the tables, and folders, have 777 permission... Any idea?

[JuanS_OCS]

Hello @MariaD ,

thank you for the checks. Did you have the chance to look at the SAS EG logging, right after you expand "Libraries"?

Otherwise, I would suggest to open a ticket with SAS Tech Support, as suggested earlier.