|
||||||||||||||||||||||||||||||||||||||||||
|
OMS
The status command provides more details for the OMS environment. These include: · Target database session count – The number of database connections established under the Databases folder in the navigator component of OEM. · Operations queued for processing – Indicates the number of operations that are waiting to be processed. The activities may include sending e-mail, deleting events, submitting jobs, etc. · Number of OMS systems in domain – Displays the number of OMS servers running. Multiple OMS servers can be created for scalability in large environments. · Number of administrators logged in – The number of OEM administrators logged in to the OMS. · Repository session pool depth – The number of database sessions reserved for OMS to submit jobs and register events. The default is 15 sessions and can be increased when heavy activity occurs. · Repository session count – The number of repository sessions currently in the pool. The OMS requires 7 sessions on startup. A repository session is needed to access information in the OEM repository. A specific number of sessions are retained in a pool to keep OMS from re-opening and closing sessions – a resource consumer. This parameter is not modifiable. Stopping the OMS is performed by the command below. The stop command also requires the username and password.
oemctl stop oms <EM Username>/<EM Password>
|
|
||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||