Skip to main content

SAS Metadata repository physical location



In this article you will get to know where Metadata repository is stored physically and in Metadata level.

I have already posted article about three different types of Metadata repositories and their uses. You can locate any type of repositories using SAS Management Console.

Metadata Manager plug in shows repository location

Expand Metadata manager plug in, under Active Sever you will find all the repositories configured in you SAS environment. By expanding Active Server you can see the Foundation repository. All the Metadata contents will be stored under this. There should be exactly one foundation repository.

Physical location

In Metadata manager plug in, expand active server and click on the foundation. You will get repository id, repository type and repository path. Repository path shows the physical location. It only show you the relative path.


In above figure, I have merged snapshot of SAS Management Console and snapshot of physical location.

You can get details about the type of repository and the repository ID. You can also see the format of Metadata data sets are sas7bdat. You should use OS command line editor like vi or vim to edit the file. Editing the file directly will corrupt and may cause severe damage to metadata server.

Default location of Metadata repository is SAS-configuration-directory/Lev1/SASMeta/MetadataServer

However you can use different location for custom or project repository.

Metadata repository format

Metadata repositories are nothing but tables in sas7bdat format. The sas7bdat is SAS dataset format. You should not access those tables directly. These tables get locked while Metadata server is in running state. If you to access repository tables, you should use Metadata queries. It is safe to use Metadata queries because PROC Metadata, Metadata management batch tools and DATA step function will be processed by Metadata several.

Comments

Post a Comment

Popular posts from this blog

Starting Gemfire in SAS

Gemfire is available in both Compute and Mid. The default port is 41415. If you have many gemfire, you may have port numbers incremented by 1, for example: 41416. Gemfire is located under Web. <SASCONFIG>/Web/gemfire. To Start: <SASCONFIG>/Web/gemfire/instances/ins_41415/gemfire-locator.sh start To check Status: <SASCONFIG>/Web/gemfire/instances/ins_41415/gemfire-locator.sh status To stop: <SASCONFIG>/Web/gemfire/instances/ins_41415/gemfire-locator.sh stop If it doesn;t start check port number is occupied by any other process. lsof -i tcp:41415 If you only have one instance then 41415 will be default. If you have Lev2 then it will be 41416
Post a Comment
Read more

SAS 9.4 server startup order

In Linux / Unix OS we normally use sas.servers to start the services. The script in the background follows an order to start the services. It is important to follow the order to run the services correctly. In this post we can see what is the order to start / stop and to generate the sas.servers script. It is not really required to memorize the order because SAS provide an utility to create the sas.servers script automatically which will start / stop the service in order. Starting order SAS Metadata server Olap server SAS object spawner SAS / SHARE server SAS / connect spawner SAP table server SAP remote services SAS deployment tester server Stopping will be the same in reverse. How to create sas.server script? We can create sas.server script by using generate_boot_script.sh. if you have made any changes to your environment like adding a new server or spawner we can use the script to generate new sas.server. You can use the script even if you have removed the spanner o...
Post a Comment
Read more

Insufficient authorization to access PIPE error in SAS EG

Issue: When I tried to run SAS code in SAS Enterprise Guide it throws following errors: ERROR: Insufficient authorization to access PIPE. ERROR: Error in the FILENAME statement. Screenshot of error: Solution: This error occurs when you try to run OS commands in SAS code. To run the OS commands in SAS code you need to enable XCMD option. You check it in SAS Management Console by following below steps.   Open SMC -> Expand Servers -> Expand   In SASApp , expand Logical Workspace Server -> right click on Workspace Server. Click properties -> option tab -> advanced options -> launch properties. Check whether Allow XCMD is checked. The issue arises if the Allow XCMD is not checked. In above image, Allow XCMD option is not checked. It should be checked to run OS commands from SAS code. In Unix /Linux machines, this XCMD option can be enabled by using system option XCMD in sasv9 config file or workspaceserver.sh script f...
2 comments
Read more