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:
-objectserverparms "cel=... hostknownby='mymetadataserver_ip.com' lbconfig='./LBConfigNoCluster.xml'"
To circumvent the problem, change the parameter to dnsMatch=, as shown in this example:
-objectserverparms "cel=... dnsMatch='mymetadataserver_ip.com' lbconfig='./LBConfigNoCluster.xml'"
Operating System and Release Information
SAS System | SAS Metadata Server | Microsoft Windows 8 Enterprise 32-bit | 9.4 | 9.4_M2 | 9.4 TS1M0 | 9.4 TS1M2 |
Microsoft Windows 8 Enterprise x64 | 9.4 | 9.4_M2 | 9.4 TS1M0 | 9.4 TS1M2 |
Microsoft Windows 8 Pro 32-bit | 9.4 | 9.4_M2 | 9.4 TS1M0 | 9.4 TS1M2 |
Microsoft Windows 8 Pro x64 | 9.4 | 9.4_M2 | 9.4 TS1M0 | 9.4 TS1M2 |
Microsoft Windows 8.1 Enterprise 32-bit | 9.4 | 9.4_M2 | 9.4 TS1M0 | 9.4 TS1M2 |
Microsoft Windows 8.1 Enterprise x64 | 9.4 | 9.4_M2 | 9.4 TS1M0 | 9.4 TS1M2 |
Microsoft Windows 8.1 Pro | 9.4 | 9.4_M2 | 9.4 TS1M0 | 9.4 TS1M2 |
Microsoft Windows 8.1 Pro 32-bit | 9.4 | 9.4_M2 | 9.4 TS1M0 | 9.4 TS1M2 |
Microsoft Windows Server 2012 Datacenter | 9.4 | 9.4_M2 | 9.4 TS1M0 | 9.4 TS1M2 |
Microsoft Windows Server 2012 R2 Datacenter | 9.4 | 9.4_M2 | 9.4 TS1M0 | 9.4 TS1M2 |
Microsoft Windows Server 2012 R2 Std | 9.4 | 9.4_M2 | 9.4 TS1M0 | 9.4 TS1M2 |
Microsoft Windows Server 2012 Std | 9.4 | 9.4_M2 | 9.4 TS1M0 | 9.4 TS1M2 |
Windows 7 Enterprise x64 | 9.4 | 9.4_M2 | 9.4 TS1M0 | 9.4 TS1M2 |
Windows 7 Professional x64 | 9.4 | 9.4_M2 | 9.4 TS1M0 | 9.4 TS1M2 |
64-bit Enabled AIX | 9.4 | 9.4_M2 | 9.4 TS1M0 | 9.4 TS1M2 |
64-bit Enabled Solaris | 9.4 | 9.4_M2 | 9.4 TS1M0 | 9.4 TS1M2 |
HP-UX IPF | 9.4 | 9.4_M2 | 9.4 TS1M0 | 9.4 TS1M2 |
Linux for x64 | 9.4 | 9.4_M2 | 9.4 TS1M0 | 9.4 TS1M2 |
Solaris for x64 | 9.4 | 9.4_M2 | 9.4 TS1M0 | 9.4 TS1M2 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.