You
can use SAS Management Console to stop, pause, or resume the SAS Metadata
Server. You can also use SAS Management Console to reset the metadata
server in order to recover memory on the host machine.
-
Log on to SAS Management
Console as a user with the appropriate credentials.
-
On the
Plug-ins tab,
expand the
Metadata Manager node, and right-click
the
Active Server node.
-
Select one of the following
actions:
Stop
completely stops the
metadata server.
Note:
-
Stopping the metadata server stops
other components, including object spawners, OLAP servers,
SAS/CONNECT
spawners, and
SAS/SHARE servers.
-
To start the metadata server after
stopping it, you must use a script or Windows services. If you want
to be able to resume processing from SAS Management Console, use
PauseOffline instead.
PauseOffline
pauses the metadata
server to the Offline state. In the Pause Comment dialog
box, you can enter a comment that provides information about the pause
action. When a client attempts to read or write metadata, the comment
is appended to the appropriate message and displayed as follows:
Error
accessing metadata: The GetMetadataObjects request failed because
the server is paused for OFFLINE use. The reason for the server pause
is
comment.
PauseAdministration
pauses the metadata
server to the Administration state. In the Pause Comment dialog
box, you can enter a comment that provides information about the pause
action. When a user who is not in the Metadata Server:
Unrestricted role attempts to read or write metadata,
the comment is appended to the appropriate message and displayed as
follows: Error accessing metadata: The GetMetadataObjects
request failed because the server is paused for ADMINISTRATION use.
The reason for the server pause is
comment.
Resume
returns the metadata
server to the Online state (if the current state is Offline or Administration).
The metadata server resumes accepting client requests to read and
write metadata and re-opens repository containers as clients request
metadata from them.
Reset
unloads from memory
and closes the containers of all registered repositories in order
to recover memory on the metadata server host. The metadata server
then re-opens repository containers as clients request metadata from
them. This option is useful if the host computer experiences an out-of-memory
condition.