10-28-2014 08:13 PM
We are not able see the pre assigned libraries in EG. we recently migrated to SAS 94. it seems workspace start up scripts are not loading pre assigned libraries during session initialization. validated all the Configuration files , but not getting any clue on issues. Can you some one please help me on it
10-28-2014 08:25 PM
There are a variety of reasons that could cause this.
How do you pre-assign your libraries? Was it in SMC (Management Console) Data Manager? If so, please confirm that you migrated your SAS metadata from your previous SAS version including your data libraries.
10-28-2014 08:36 PM
i am using SMC Data manger - Library- properties - options - pre-assigned - Type ( By Native library Engine ) . Yes we migrated SAS metadata and all other Components to new version
10-28-2014 08:49 PM
OK. What I would try next then is construct a LIBNAME statement that is exactly the same as one of your pre-assigned libraries and submit that in EG. Does it work OK?
10-28-2014 09:10 PM
Yes I am able to run LIBNAME statements which are Generated from SMC . I would like to call out one more issues here is when i trying to see libname statement for pre-assigned Lib in SMC , it is giving error stating that " The "XXXXX" library was pre assigned so no LIBNAME Statement is generated "
10-28-2014 11:04 PM
That is a "normal" response - it is a SAS limitation. You can turn off the pre-assigment temporarily so you can see the LIBNAME, which you can then copy to EG for testing.
Another reason why pre-assigned libraries might not work is to do with metadata permissions. Check to see whether the metadata folder(s) where your data libraries are stored are accessible by your users.
10-29-2014 12:18 AM
yes I validated metadata permissions for both Physical locations of Libraries and Libraries. users have required level of access on those.
10-29-2014 03:04 AM
Do an Object Spawner refresh.
Also check that libraries are assigned to the right application server (Assign tab in MC)
10-29-2014 08:52 PM
yes I did Object Spawner refresh but that didn't work. and yes I assigned libraries to right application server SASApp.
10-29-2014 08:53 PM
Yes. we are seeing the same issue for new data Libraries which are created in new environment.
10-29-2014 05:47 PM
Check the servers are allowed to support to do metadata pre defined
SAS(R) 9.4 Intelligence Platform: Data Administration Guide, Third Edition Understanding Pre-Assigned Libraries
SAS(R) 9.4 Intelligence Platform: Data Administration Guide, Third Edition Pre-assigning a Library.
SAS(R) 9.4 Intelligence Platform: Application Server Administration Guide There are parameter that prevent metadata pre assigned libraries. Are these set correct?
In the last one there is a disadvantage mentioned as multiple locations.
This disadvantage can be also an advantage when the physical (external) and logical definitions are needed to be segregated (a real possible requirement).
An other advantage is that is more easy to debug in case of issues.
Choosing the best method:
10-29-2014 09:21 PM
Thanks for detailed information ,those Notes are replied helped me to understand more on Pre -assigned libraries.
I am using "By native library engine" option while updating libraries as pre -assigned one. To load these I updated metaautoresources option to my sasv9.cfg file. And i am calling it from Autoexec.sas file.
10-30-2014 02:28 AM
jagadeesh, The mentioned steps are clear as is the figure of G.Nelson.
However I cannot get clear where your assignments are done.
- If the libname is in the autoexec you can very all that by using X11 and X-server starting the WS-script manullay.
When the libname are not visible in Eguide after that than there is an option active that disables libraries not being registered in metadata
- When the autoexec is left untouched those libnames are generated at start of the process by interacting to the metadataserver.
In this case validation of all settings in the metadata is possible but never the whole process a total. Using Eguide is the only option and all could be influence by metadatasecurity settings. They can be surprising as the user iniitating the sas process and the user running the sas (shared account SP Pooled ws) could both need those. Shared accounts are to be avoided as much as possible oe being very well reviewed on their aspects.
10-30-2014 03:02 AM
we are able resolve the issues. Due to enormous features of SAS 94 we were not able figured out default parameter of SASApp- Logical Workspace server called Object server parameter was set to "nopreassigned". After we remove this to make the Changes effective we did restart of both Metadata and Object Spawner servers and that resolves the issues .
Thank you all for your timely response and Help
Thank you !
Need further help from the community? Please ask a new question.