Skip to main content

Managing repository in SAS

Here you will get information about several option available in SAS that is used to manage repository.

Metadata Manager Plug-in - Create, Register, Unregister, Delete Repository

In SAS Management Console, you will be using Metadata Manager Plug-in to create and manage repositories.

With Metadata Manager Plug-in you can create, register, delete and unregister a repository. Let's see what this four operations do and how it differs from each other.

Create

With this option you can create a new repository. It will create initial repository content and all the metadata content that defines the repository.

Register

It creates the metadata that defines the repository and points to existing repository content.

Delete

It deletes the all the metadata that defines the repository and repository content.

Unregister

It removes the the metadata that defines the repository but not repository content.

Here you need focus on two things

  • Metadata content
  • repository content


If you are removing or adding repository content then you are either register or unregister. If you remove metadata content along with repository content then you are performing delete operation.

What permission is needed to do this task:

To do these task the user must be a member of Metadata Server: Unrestricted role or SAS Administrator group. However, if the users need to perform these operation on foundation repository, he/should be member of SAS Admin group and should be specified as unrestricted user in adminUsers.txt. User should be very careful while deleting or unregistering foundation repository. Any changes made in foundation repository will make metadata server unstable. These operation were done to foundation repository only in special situations.

SAS Administrators is a default group in SAS deployment with following permissions:
It is member of Management Console: Advanced role, Metadata Server: Operation role, and Metadata Server: User Administration role. In addition to this SAS Administrator group have WriteMetadata permission on the Root folder of the SAS Folders tree, Administer permission on server metadata, and ReadMetadata on server metadata in the SASMeta context.

SAS Support says:
It is better to add internal users to the SAS Administrators group rather than external users.

Comments

Post a Comment

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...
2 comments
Read more

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.
1 comment
Read more

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...
3 comments
Read more