I configured 2 libraries, 1 Oracle(Assuming Library LA) and 1 BASE SAS(Assuming Library FM).
In SAS Management Console, for Oracle Library(LA), I did not tick "Library Pre-assign". Database Server, Connection and Default Login are all configured. I right click this particular library in SMC and the Libname statement it produces runs perfectly fine in SAS Enterprise Guide and I can see all tables in Oracle under this library(yellow color).
Same for BASE SAS Library(LA), I did not tick "Library Pre-assign". Database Server, Connection and Default Login are all configured. I right click this particular library in SMC and the Libname statement it produces runs perfectly fine in SAS Enterprise Guide and I can see all tables in the physical directory(Linux) under this library(yellow color).
Problem is, when i open SAS EG, Oracle library(LA) is shown white color and if i double click it, only tables that I manually Register in SAS DI Studio will be listed in SAS Enterprise Guide. What I want is to see the full list of oracle tables in Oracle library using SAS Enterprise Guide regardless of what I registered in SAS DI Studio. How can I do so?
Also, in SAS DI Studio, if i try to read/write Oracle(LA) or BASE(FM) tables, it will complain "Libref LA is not assigned". I don't understand as I can register LA table in SAS DI Studio but job in DI will complain Libref error. What did i do wrong?
@WorkingMan - The secret to getting all tables listed in EG, without registering them, for libraries pointing to external databases is to add the following Extended Attribute to your SMC library definition. Also regarding the library assignment problem. I suspect you will need to select the SMC pre-assign library option to fix that.
@SASKiwi Adding Extended Attributes work! Really appreciate that.
For SAS DI Studio, despite ticking "Library pre-assign" for both Oracle LA and BASE SAS FM libraries, my DI Studio is still prompting the same error of Libref LA not assign and Libref FM not assign. Is there any other method that we can try?
@WorkingMan - Good to hear it partly works. We don't have DI Studio so I can't test your problem. All I know is the libraries need to be pre-assigned to work in SAS batch jobs. Does your DI Studio SAS log provide any clues? Does it try to assign the library and fail? Be sure to start a new DI Studio SAS session after changing your libraries in SMC.
I am thinking if i should restart any services component for it to work?
@SASKiwi the only error logs are Libref LA is not assigned & Libref FM is not assigned in DI Studio 😞
strange...i tried to hardcode the libname statement in appserver_usermod.sas, error gone. But, I do not want to hardcode it in that file...what else should I check?
Hi WorkingMan,
You may need to have a look at https://documentation.sas.com/?docsetId=bidsag&docsetTarget=p0u8xcdo2ll3kmn1oqfz2s0ybooq.htm&docsetV...
Note: Keep in mind that pre-assigning the library does not mean that you do not need to register tables in metadata. You must register the tables so that applications that read tables from metadata, such as SAS Data Integration Studio, can work with the tables.
and select the best recommended option that suit you.
Hope this help.
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.