The -startNoCluster option starts a single node in a metadata cluster. That node, in turn, starts a single, non–clustered metadata server that is paused in the Administration state.

This action is useful when you want to perform one of the following administrative tasks:

• recover a metadata server
• back up the metadata server by using the REORG option
• run the optimizeIMDB command option of the metadata server script
• run the Metadata Analyze and Repair tools

The -startNoCluster option, which is available to a single node deployment, is primarily to be used to address a clustered metadata server.

However, when you start the SAS Metadata Server server with the shell script option -startNoCluster, the server fails to initialize.

The server will attempt to start, but ultimately it fails and the following message is generated:

Server is stopped
Log files are located at: /tmp/prod/configmeta3/Lev1/Logs
Metadata server failed to start, check the log for errors.

The log also contains the following error messages:

ERROR [00000007] :sas@SASBI - The local server definition could not be found in the load balancing configuration file (LBCONFIG).     
ERROR [00000007] :sas@SASBI - The load balancing configuration could not be processed for this server.  The server will terminate.    

The problem occurs when the objectserverparms option includes the hostknownby= parameter in the sasv9_nocluster.cfg file, as shown below:

To circumvent the problem, change the parameter to dnsMatch=, as shown in this example:

Operating System and Release Information