Pre-Assigned ODBC DB library, shows up with the expected icon (yellow folder), however registered tables underneath (visible in SMC), do not.
I found this link of a previously answered note: https://communities.sas.com/t5/General-SAS-Programming/pre-assigned-libraries-in-SAS-94-are-not-load... however, I do not see any such option in the .bat file for WSS nor in SMC.
I am lacking what else to look at. Note two weeks ago when the pre-assigned was established same user was able to see all those registered tables show up in EG and was able to drag n drop a table (able to use). To re-word, they still show only in SMC library pre-assigned icon shows up in EG but no registered tables underneath.
Any insights are appreciated an thank you in advance,
Shoin
Hi @Greg the security is very simple (few users) and all are members of SASUSERS and it has the default permissions RM, WMM, read.
TY for your suggestion
Do you have a special need to register the database tables? If you instead assign an extended attribute on the pre-assigned library like so:
then all tables will show without registering.
Hi and TY.
The registration is not the issue. The tables in EG do not how up, same registered tabled show in SMC. In the EG sesison, pre-assigned shows up proper yellow icon. However, no registered tables, yet end user could do a data step using any one of the reg. tables.
So did you try my solution to see if the tables showed in EG with no registration required?
No tables showing? Is the library is pre-assigned? It won't work otherwise. Also check the database and schema definition.
Hi, yes library is pre-assigned.
I am stumped.
@shoin - I'm running out of ideas too. We use metadata-defined pre-assigned libraries with AssignMode = 2 exclusively and there are no problems with tables showing.
What happens if you assign the same external database in a LIBNAME statement? Do the tables show in EG (need to refresh the Server List after running the LIBNAME)?
If your EG LIBNAME works fine then it is your metadata data library settings that are causing the problem. I would try these tests:
Hello
Please check if the tables were registered as unrestricted user account.
If yes, that could be an issue.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.
Find more tutorials on the SAS Users YouTube channel.