I am wondering if there is any correlation between running requests to the meta-data-server to retrieve the meta-data itself (meta-data programming) ending in exceptions and the unresponsiveness of the meta-data-server ? We experienced an unresponsiveness of the meta-data-server (reported by the users) but I am not able to see anything in the logs which could indicate such problem. As I am new to the SAS world any suggestion / hint which could lead me in the right way is appreciated. For information, we do use SAS 9.4.
Thank you very much,
It could be, but it's hard to tell given the information at hand.
If not already done so, run the Analyze & repair metadata task.
When users report problem document when, what objects they were working with, and using which client.
Depending on the client, there might be local logs that can give you additional information.
I recommend you open a TS track for this question.
Please include the following:
- SAS Version you are running (the following code will report SAS version information)
%put &sysvlong ;
%put &sysscpl ;
%put &syssite ;
- Registry Report (*.txt files) for each server, please clearly name the report files to reflect the server it was executed on
- Detailed description of the issue
- Any logs that contain helpful information
after some more analysis it seems that at the time of the problem we had a high load on the system itself caused by people checking in changes and performing exports via the ExportPackage script at the same time.
It seems that calling the ExportPackage script a couple of times (30 to 40 times) in a row does put quite some load onto the system as it reads each time the whole meta-data (can this be ?). Is there a way to call the ExportPackage script in such a way that it does export multiple objects at once but each object in a different defined .spk file and not into one ?
There is no way to read once and export to different spks.
An Analyze/Repair and Backup/REORG would be helpful.
See if you can tell if there is a particular export that is slow.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.
Find more tutorials on the SAS Users YouTube channel.