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

Popular posts from this blog

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...

The authentication server is not SETUID ROOT error in SAS

Question: When validating the SAS Server from SAS Management Console, I received the following error: The authentication server is not SETUID ROOT.  So, I ran the setuid.sh utility and restarted the services many times. I just checked the elssrv sasauth sasperm setuid bit. There were no error in sasauth-debug.log, sasauth-access.log, sasauth-error.log.  Any suggestions? Answer: Please do the following:    1) Run /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh stop  2) Edit /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh and add the code shown below right after SCRIPT=`basename $0`:  if [ -n ""$TKPATH"" ]; then  unset TKPATH  fi   if [ -n ""$TK_PATHLIST"" ]; then  unset TK_PATHLIST  fi    3) Run /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh start  The above code change in ObjectSpawner.sh should fix the issue.

SAS - CLI error trying to establish connection

Issue: User asked me to make a database connectivity to SQL Server. They provided following details SQL server hostname and ip address Database/DSN name Username Password I made entry in ODBC.ini file. You know, SQL Server entries were made in ODBC.ini and Oracle entries were made in TNS.ora file. Everything went fine, took back up of odbc.ini, made entry and saved the file. So to test this connection I ran the libname statement in SAS Enterprise Guide 6.1. It throwed following error. Error Message: My DB team showed that they are able to login   14 GOPTIONS ACCESSIBLE; 15 LIBNAME test ODBC DATASRC=SGE_DS SCHEMA=VST USER=sales PASSWORD=XXXXXXXXX; ERROR: CLI error trying to establish connection: [SAS/ACCESS to SQL Server][ODBC SQL Server Legacy Driver][SQL Server]Login failed for user 'sales'. Solution: First I suspected that Login failed for user 'sales' meant the password provided by DB team was wrong. They responded that they were able to login wi...