3
Controlling the Management Server

The Management Server provides distributed control between clients and managed nodes. A central engine for notification, it processes all system management tasks and administers the distribution of these tasks across the enterprise.

Specific topics discussed in this chapter are listed below:

• Starting the Management Server

• Checking the status of the Management Server

• Stopping the Management Server

Starting the Management Server

Note: The repository database must be started and open before starting the Management Server.

To start the Management Server, perform the following steps.

Note: Oracle Enterprise Manager does not support starting a Management Server that is not local to your machine (i.e., a remote Management Server).

See "Edit Configuration Parameters" on page B-8 if you need to add or change the repository connection information for a Management Server.

For information on troubleshooting the Management Server if it does not start, refer to "Checking the Management Server Log Files" on page 3-7.

On Windows NT:

1. From the Start menu->Settings->Control Panel, double-click the Services icon.

2. Select the Oracle<Oracle_Home_Name>ManagementServer service.

3. Click the Startup push-button to access the Service Startup dialog box.
   1. In the Startup Type section, specify how the Management Server service is started up by choosing Automatic or Manual. Manual allows the Management Server to be started by a user. Automatic allows the Management Server to start automatically whenever the user starts the system. Disabled does not allow the Management Server to start at all.

   2. In the Log On As section, check for the following settings:
      • Ensure that the System Account option, which is the supported way to run the Management Server, is selected; otherwise, it may no longer appear when you log out.

      • Ensure that the "Allow Service to Interact with Desktop" box is deselected. Do not check "Allow Service to Interact with Desktop" unless you are requested by support for troubleshooting purposes. If this box is checked, the Management Server will try to create a DOS console on the default desktop. If no one is logged in, the Management Server will hang.

   3. If you have chosen not to store your repository credentials during repository creation, you must enter the repository's user name that was used to create the database user and the password for that user in the Service Startup dialog box when you start the Management Server.

      If you do not supply your repository credentials in the Service dialog, the Management Server will not start. If you enter the wrong credentials, the Management Server also will not start.

      For a complete definition of a repository owner, refer to "Step 3 "Repository Login Information"" on page 2-8.

      For information on troubleshooting the Management Server if it does not start from the Windows NT Start menu, refer to "Management Server Does Not Start from the Windows NT Start Menu" on page C-12.

4. Click the Start push-button to start the Management Server.

Note: Your Management Server service is started automatically on Windows NT during repository creation if you had launched the Enterprise Manager Configuration Assistant from an installation session and if you have chosen to save your repository credentials. If you have chosen not to save your repository credentials, you must enter them in the Service Startup dialog box.

On UNIX:

At the command line, enter

% oemctrl start oms

If you want to start the Management Server as a background process, at the command prompt, enter

% oemctrl start oms&

The command string is case-sensitive and must be entered with lowercase characters.

When you are prompted, enter the repository's user name that was used to create the database user and the password for that user if you have chosen not to save your repository credentials during repository configuration. For a complete definition of a repository owner, refer to "Step 3 "Repository Login Information"" on page 2-8.

Note: If the ORACLE_HOME environment variable is not set to the Oracle home in which the Management Server is running, the Management Server will not start correctly because it will try to find its class files in the default Oracle home instead of the correct Oracle home. For information on setting the Oracle environment, refer to "Management Server May Not Run Correctly from a Non-Default Oracle Home" on page C-11.

Checking the Status of the Management Server

To check the status of the Management Server, at any operating system prompt, enter:

% oemctrl status oms

The command string is case-sensitive on UNIX and must be entered with lowercase characters.

You will be prompted to enter the username and password of an Oracle Enterprise super administrator. For a complete definition of an Oracle Enterprise Manager super administrator, refer to "What is an administrative user?" on page 1-6.

You will also need to provide the hostname for the machine running the Management Server if you are checking the status of a remote Management Server.

The following information is provided when you check the status of the Management Server:

• overall status of the Management Server

• length of time the Management Server has been running

• statistics regarding the performance of the Management Server

An example of the output is shown below:

OEMCTRL for Windows NT: Version 2.1.0.0.0
Copyright (c) 1998, 1999 Oracle Corporation.  All rights reserved.

The Oracle Management Server on host [pjlee-pc.us.oracle.com] is functioning 
properly.

  The server has been up for 0 00:03:55.437

  Target database session count: 1 (session sharing is off)
  Operations queued for processing: 0
  Number of OMS systems in domain: 1 (pjlee-pc)
  Number of administrators logged in: 1
  Repository session pool depth: 15
  Repository session count: 6 in-use and 1 available, pool efficiency: 70%

Stopping the Management Server

Note: Stopping a Management Server that is not local to your machine (i.e., a remote Management Server) is not supported.

To stop the Management Server, perform the following steps:

On Windows NT:

1. From the Start menu->Settings->Control Panel, double-click the Services icon.

2. Select the Oracle<Oracle_Home_Name>ManagementServer service.

3. Click the Stop push-button to stop the Management Server.

You will be prompted to enter the username and password of an Oracle Enterprise super administrator. For a complete definition of an Oracle Enterprise Manager super administrator, refer to "What is an administrative user?" on page 1-6.

On UNIX:

At the command line, enter

% oemctrl stop oms

The command string is case-sensitive and must be entered with lowercase characters.

You will be prompted to enter the username and password of an Oracle Enterprise super administrator. For a complete definition of an Oracle Enterprise Manager super administrator, refer to "What is an administrative user?" on page 1-6.

Checking the Management Server Log Files

For information to troubleshooting the Management Server if it does not start, refer to the following resources:

• the oms.log file

• the oms.nohup file (for Solaris)

• the Windows NT Event Log (for Windows NT)

The $ORACLE_HOME\sysman\log directory contains the output of traces that are redirected to disk. This directory contains the oms.log and oms.nohup files.

The Management Server places all its trace messages in oms.log file. The oms.log file contains messages generated when the Management Server is starting and running.

The oms.nohup file contains Management Server error messages which appear before the Management Server starts up.

To access the Windows NT Event Log to view the events logged by the Management Server.

1. From the Start menu->Programs->Administrative Tools (Common), select the Event Viewer item.

2. Select Application from the Log menu.

3. When the log screen appears, double-click any event logged by the Oracle<Oracle_Home_Name>ManagementServer service which have red octagonal stop signs next to them. These will be the errors reported by the Management Server, if any.