METAOPERATE Procedure

Concepts: METAOPERATE Procedure

The administrator of the metadata server can perform two kinds of maintenance with PROC METAOPERATE:

control the metadata server by calling methods in the IServer class of SAS Open Metadata Architecture: PAUSE, REFRESH, RESUME, STATUS, STOP
control a repository by calling methods in the IOMI class of SAS Open Metadata Architecture: DELETE, EMPTY, UNREGISTER

How PAUSE, REFRESH, and RESUME Affect Repositories

Beginning in SAS 9.2, the PAUSE and RESUME actions affect the metadata server, not an individual repository or the repository manager. The REFRESH action is equivalent to a PAUSE action followed by a RESUME action.

The pause state is a property of each repository. However, a repository's pause state is not set directly. It is computed from both the metadata server state and the repository's registered access mode.

You can set the metadata server's state with the PAUSE and RESUME actions in PROC METAOPERATE or with SAS Management Console.
You cannot set a repository's registered access mode with PROC METAOPERATE. To do so, it is recommended that you use SAS Management Console. Alternatively, you can change the access mode by issuing an UpdateMetadata method call with PROC METADATA. You can determine a repository's registered access mode by issuing a GetRepositories method call with PROC METADATA. For more information, see METADATA Procedure.
However, notice in the grid below that when you use PROC METAOPERATE to pause the metadata server to an OFFLINE state (which is the default), the repositories are set to an OFFLINE state, regardless of the repositories' registered access mode. For more information about the tasks that require PAUSE, REFRESH, or RESUME actions, see SAS Intelligence Platform: System Administration Guide, especially the large section about backing up and restoring.

A repository's computed pause state is one of the following:

admin: allows read and write access for users with administrative status only.
admin(readonly): allows read-only access for users with administrative status only.
offline: disables all read and write access, unloads the repository from memory, and closes the physical files.
online: allows normal access to the repository.
readonly: allows read-only access for any user.

The following grid shows how a repository's pause state is computed from the repository's access mode (the rows) and the metadata server's state (the columns). For example, a repository with a registered OMS_READONLY access mode and an ADMIN server state has an admin(readonly) pause state.

	Online Server State	Admin Server State	Offline Server State
OMS_FULL Access Mode	online	admin	offline
OMS_READONLY Access Mode	readonly	admin(readonly)	offline
OMS_ADMIN Access Mode	admin	admin	offline
OMS_OFFLINE Access Mode	offline	offline	offline

Top of Page