Thank you both.
Please find my answers next to your questions.
Good morning,
there has been a lot of great info, and you seem to have done quite some tests. If you don't mind, let me take a shot and summarize what we have so far, maybe narrowing it down will help us all to get a new perspective, idea.
Problem:
In Library Manager, looking at a library's properties, in the data base server info tab, the field that is supposed to have database info stored, is empty, and SASMC hangs.
Is this a correct understanding? Correct.
You do encounter this problem in one environment (Prod?Dev?Test?), but not in the other? Yes.
What is the difference between both:
Are they both running on the same SAS version and SAS maintenance release? Yes.Same Version for all stages.
Are all environments using one and the same Oracle Server?Yes. (Each DEv PROD has their own schema)
As - in mulitple environments - the Metadata Server is different, and therefore, libraries etc are different, could you do a right click
on the library, Display libname statement, in both environments to see if there are any significant differences? I checked. No diiference found.
Next, right click on that lib again - Edit Assignment. Are both definitions assigned to the same DB? Yes,
Does this happen with Oracle dbms libraries only, or do you have any other DBs you could test this with? We have only oracle. It happends with oracle.
If we'd keep data base server def out of the picture, generally speaking, can you generally look at the properties in all tabs, for all libraries (including BASE)? I am interested if there might be a general problem with SASMC properties on libraries in general, and am wondering if SASMC hanging on the db serv def is just a random thing.
I can able to check all tabs for other DBs..like base sas. This is issue appearing only when i check oracle DB.
As a test, you ran lib statements against Ora from within EG and DI, with no problems, correct? Yes. No isues.
In case you have not increased the logging trace for SASMC, would you mind doing so and send the log file that's being created
after testing the behavior again? Yes I can..Send you below details.
Exist SASMC.
Close SAS Management Console on the local host.
Open the file sasmc.ini and add the following Java argument:
JavaArgs_xx=-Dcom.sas.workspace.logging.debug=true
(xx is the next available Java argument number)
(By default JavaArgs_16 is empty and can be used)
Example:
JavaArgs_16=-Dcom.sas.workspace.logging.debug=true
Modify the last line to look like:
MainClass=com.sas.console.visuals.MainConsole -debug -serverLog -consoleLog
Then from a command prompt:
For a Windows console:
<sashome>\SASManagementConsole\9.4\sasmc_console.exe -debug -serverLog -consoleLog > smcout.txt
(creates the file ) smcout.txt.
For unix:
<sashome>/SASManagementConsole/9.4/sasmc_console -debug -serverLog -consoleLog > smcout.txt
This will create a Standard out file to smcout.txt or wherever you point. In addition there will be files in the
%appdata%\SAS\SASMangementConsole\9.4 subdirectory: SASMCErrorLog.txt and SASMCServerLog.txt
On UNIX the file will be in ~/.SASAppdata/SASManagementConsole/9.4
So once the logging level has been changed, logon to SASMC and recreate the steps until SASMC hangs.
Could you please send smcout.txt, SASMCErrorLog.txt and SASMCServerLog.txt files?
It is a good practice to make a back up copy of the sasmc ini file to be sure you'll have a good file to fall back on just in
case.
Also, and that's really just a shot in the dark, could you provide the metadata server log and object spawner log after reproducing? OK.
What 9.4 maintenenace release are you running? SAS9.4 M2
Hopefully this will help to narrow it down a bit more.
... View more
