|   Login    |   January 16, 2018    |   Knowledge Base  >  Knowledge Base Systems  >  Oracle  >  Controlling the Oracle Management Agent
search:   
Phone: (480) 722-1227
Toll Free: (888) 722-1227
Controlling the Oracle Management Agent
Last Post 20 Sep 2011 07:19 PM by SuperUser Account. 0 Replies.
Printer Friendly
Sort:
NextNext
You are not authorized to post a reply.
Author Messages
SuperUser AccountUser is Offline
Basic Member
Basic Member
Posts:138

--
20 Sep 2011 07:19 PM  

Controlling the Oracle Management Agent

The following sections describe how to use the Enterprise Manager command line utility (emctl) to control the Oracle Management Agent:

** Starting, Stopping, and Checking the Status of the Management Agent on UNIX **
** Starting and Stopping the Management Agent on Windows **
** Checking the Status of the Management Agent on Windows **

Starting, Stopping, and Checking the Status of the Management Agent on UNIX

To start, stop, or check the status of the Management Agent on UNIX systems:

** Change directory to the AGENT_HOME/bin directory. **
** Use the appropriate command described in Table 8-1. **
** For example, to stop the Management Agent, enter the following commands: **
** $PROMPT> cd AGENT_HOME/bin **
** $PROMPT> ./emctl stop agent **

Table 8-1 Starting, Stopping, and Checking the Status of the Management Agent Command Purpose

emctl start agent

Starts the Management Agent

emctl stop agent

Stops the Management Agent

emctl status agent

If the Management Agent is running, this command displays status information about the Management Agent, including the Agent Home, the process ID, and the time and date of the last successful upload to the Management Repository ().

Example 8-1 Checking the Status of the Management Agent

$PROMPT> ./emctl status agent

Oracle Enterprise Manager 10g Release 10.2.0.5.0

Copyright © 1996, 2009 Oracle Corporation. All rights reserved.


Agent Version : 10.2.0.5.0

OMS Version : 10.2.0.5.0

Protocol Version : 10.2.0.5.0

Agent Home : /scratch/OracleHomesX/agent10g

Agent binaries : /scratch/OracleHomesX/agent10g

Agent Process ID : 17604

Parent Process ID : 17587

Agent https://stadj32.us.oracle.com:3872/emd/main/

Repository https://stadj32.us.oracle.com:1159/em/upload

Started at : 2009-09-13 01:31:11

Started by user : test

Last Reload : 2009-09-13 01:31:11

Last successful upload : 2009-09-13 01:39:01

Total Megabytes of XML files uploaded so far : 0.28

Number of XML files pending upload : 0

Size of XML files pending upload(MB ) : 0.00

Available disk space on upload filesystem : 8.36%

Last successful heartbeat to OMS : 2009-09-13 01:38:51


Agent is Running and Ready

$PROMPT>

On IBM AIX environment with a large memory configuration where the Management Agent is monitoring a large number of targets, the Agent may not start. To prevent this issue, prior to starting the Management Agent, set the following variables in the shell:

LDR_CNTRL=“MAXDATA=0x80000000”@NOKRTL

AIX_THREADSCOPE=S

The LDR_CNTRL variable sets the data segment size and disables loading of run time libraries in kernel space. The AIX_THREADSCOPE parameter changes AIX Threadscope context from the default Processwide 'P' to Systemwide 'S'. This causes less mutex contention. Starting and Stopping the Management Agent on Windows

When you install the Oracle Management Agent on a Windows system, the installation procedure creates three new services in the Services control panel.

The procedure for accessing the Services control panel varies, depending upon the version of Microsoft Windows you are using. For example, on Windows 2000, locate the Services Control panel by selecting Settings and then Administrative Tools from the Start menu.

Note: The emctl utility described in Controlling the Management Service on UNIX is available in the bin subdirectory of the Oracle home where you installed the Management Agent; however, Oracle recommends that you use the Services control panel to start and stop the Management Agent on Windows systems.

Table 8-2 describes the Windows services that you use to control the Management Agent.

Table 8-2 Summary of Services Installed and Configured When You Install the Management Agent on Windows Component Service Name Format Description

Oracle Management Agent

OracleAgent

For example:

OracleOraHome1Agent

Use this to start and stop the Management Agent.

Oracle SNMP Peer Encapsulator

OracleSNMPPeerEncapsulator

For example:

OracleOraHome1PeerEncapsulator

Use this service only if you are using the advanced features of the Simple Network Management Protocol (SNMP).

For more information, see the Oracle SNMP Support Reference Guide.

Oracle Peer SNMP Master Agent

OracleSNMPPeerMasterAgent

For example:

OracleOraHome1PeerMasterAgent

Use this service only if you are using the advanced features of the Simple Network Management Protocol (SNMP).

For more information, see the Oracle SNMP Support Reference Guide.

Note: If you are having trouble starting or stopping the Management Agent on a Windows NT system, try stopping the Management Agent using the following emctl command:

$PROMPT> /bin/emctl istop agent

After stopping the Management Agent using the emctl istop agent command, start the Management Agent using the Services control panel.

This problem and solution applies only to the Windows NT platform, not to other Windows platforms, such as Windows 2000 or Windows XP systems. Checking the Status of the Management Agent on Windows

To check the status of the Management Agent on Windows systems:

** Change directory to the following location in the AGENT_HOME directory: **
** AGENT_HOME/bin **
** Enter the following emctl command to check status of the Management Agent: **
** $PROMPT> ./emctl status agent **
** If the Management Agent is running, this command displays status information about the Management Agent, including the Agent Home, the process ID, and the time and date of the last successful upload to the Management Repository (). **

Controlling the Oracle Management Service

The following sections describe how to control the Oracle Management Service:

** Controlling the Management Service on UNIX **
** Controlling the Management Service on Windows **

Controlling the Management Service on UNIX

There are two methods for starting and stopping the Oracle Management Service on UNIX systems. You can use the Oracle Process Management and Notification (OPMN) utility, or you can use a set of emctl commands.

The following sections describe these two approaches to controlling the Management Service, as well as information about starting and stopping OracleAS Web Cache, which is also required by the Grid Control console:

** Using OPMN to Start and Stop the Management Service **
** Using emctl to Start, Stop, and Check the Status of the Oracle Management Service **
** Starting and Stopping Oracle Application Server Web Cache **

Using OPMN to Start and Stop the Management Service

One method of starting and stopping the Management Service by using the Oracle Process Management and Notification (OPMN) utility. The OPMN utility (opmnctl) is a standard command used to start and stop components of the Oracle Application Server instance.

The Management Service is a J2EE application running in an Oracle Application Server Containers for J2EE (OC4J) instance within the Application Server. As a result, the following command will start all the components of the Oracle Application Server instance, including the OC4J_EM instance and the Management Service application:

$PROMPT> cd opmn/bin

$PROMPT> ./opmnctl startall

Similarly, the following command will stop all the components of the Oracle Application Server instance:

$PROMPT> ./opmnctl stopall

If you want to start only the components necessary to run the Management Service, you can use the Enterprise Manager command-line utility. Using emctl to Start, Stop, and Check the Status of the Oracle Management Service

To start, stop, or check the status of the Management Service with the Enterprise Manager command-line utility:

** Change directory to the ORACLE_HOME/bin directory in the Management Service home. **
** Use the appropriate command described in Table 8-3. **
** For example, to stop the Management Service, enter the following commands: **
** $PROMPT> cd bin **
** $PROMPT> ./emctl stop oms **

Table 8-3 Starting, Stopping, and Checking the Status of the Management Service Command Purpose

emctl start oms

Starts the Oracle Application Server components required to run the Management Service J2EE application. Specifically, this command starts OPMN, the Oracle HTTP Server, and the OC4J_EM instance where the Management Service is deployed.

Note: The emctl start oms command does not start Oracle Application Server Web Cache. For more information, see “Starting and Stopping Oracle Application Server Web Cache”.

emctl stop oms

Stops the Management Service.

Note that this command does not stop the other processes that are managed by the Oracle Process Manager and Notification Server (OPMN) utility.To stop the other Oracle Application Server components, such as the Oracle HTTP Server and Oracle Application Server Web Cache, see “Starting and Stopping Oracle Enterprise Manager 10g Grid Control”.

emctl status oms

Displays a message indicating whether or not the Management Service is running.

Starting and Stopping Oracle Application Server Web Cache

By default, when you install Oracle Enterprise Manager 10g, the Grid Control console is configured to use Oracle Application Server Web Cache.

See Also: Oracle Application Server Web Cache Administrator's Guide for more information about Oracle Application Server Web Cache

Oracle Application Server Web Cache not only improves the performance of the Grid Control console, but also makes it possible to measure the end-user performance of the Enterprise Manager Web application.

To view the Grid Control console using Oracle Application Server Web Cache, you access the Grid Control console using the standard port number assigned during the Oracle Enterprise Manager 10g installation procedure. You can find this default port number (usually 7777) in the setupinfo.txt file, which is copied to the following directory during the Enterprise Manager installation procedure:

AS_HOME/Apache/Apache

If Oracle Application Server Web Cache is not running, you will receive an error message, such as the following, if you try to access the Grid Control console using the default port number:

HTTP 500 - Internal server error

To start Oracle Application Server Web Cache:

** Change directory to the ORACLE_HOME/opmn/bin directory in the Management Service home. **
** Use the appropriate command described in Table 8-4. **
** For example, to stop Oracle Application Server Web Cache, enter the following commands: **
** $PROMPT> cd opmn/bin **
** $PROMPT> ./opmnctl stopproc ias-component=WebCache **

Table 8-4 Starting, Stopping, and Checking the Status of Oracle Application Server Web Cache Command Purpose

opmnctl startproc ias-component=WebCache

Starts Oracle Application Server Web Cache.

opmnctl stopproc ias-component=WebCache

Stops Oracle Application Server Web Cache.

opmnctl status

Displays a message showing the status of all the application server components managed by OPMN, including Oracle Application Server Web Cache.

Controlling the Management Service on Windows

When you install the Oracle Management Service on a Windows system, the installation procedure creates three new services in the Services control panel.

The procedure for accessing the Services control panel varies, depending upon the version of Microsoft Windows you are using. For example, on Windows 2000, locate the Services control panel by selecting Settings and then Administrative Tools from the Start menu.

Note: The emctl utility described in Controlling the Management Service on UNIX is available in the bin subdirectory of the Oracle home where you installed the Management Service; however, Oracle recommends that you use the Services control panel to start and stop the Management Service on Windows systems.

Table 8-5 describes the Windows services that you use to control the Oracle Management Service.

Table 8-5 Summary of Services Installed and Configured When You Install the Oracle Management Service on WIndows Component Service Name Format Description

Application Server Control

OracleASControl

For example:

OracleOraHome1ASControl

Use this Service to start and stop the Application Server Control for the Oracle Application Server instance that was installed and configured to deploy the Management Service J2EE application.

Oracle Process Management and Notification (OPMN)

OracleProcessManager

For example:

OracleOraHome1ProcessManager

Use this service to start and stop all the components of the Oracle Application Server instance that were installed and configured to deploy the Management Service J2EE application.

Use this service to start and stop the Management Service and all its related components, including OC4J, Oracle HTTP Server, and OracleAS Web Cache, which by default must be running in order for you to access the Grid Control console.

Controlling the Application Server Control

The Application Server Control is a component of Oracle Enterprise Manager 10g that is installed as part of any Oracle Application Server installation. The following sections describe how to start and stop the Application Server Control:

** Starting and Stopping the Application Server Control on UNIX **
** Starting and Stopping the Application Server Control on Windows **

See Also: Oracle Application Server 10g Administrator's Guide for more information about:

** Using emctl to control the Application Server Control Console **
** Starting and stopping the Application Server Control Console on Windows **
** Displaying disabled components of the Application Server **

Starting and Stopping the Application Server Control on UNIX

To control the Application Server Control Console on UNIX systems, you use the emctl command line utility that is available in the IAS_HOME/bin directory after you install Oracle Application Server.

To start the Application Server Control Console, change directory to the IAS_HOME/bin directory and then enter the following command:

$PROMPT> ./emctl start iasconsole

To stop the Application Server Control Console, enter the following command:

$PROMPT> ./emctl stop iasconsole

Starting and Stopping the Application Server Control on Windows

To start or stop the Application Server Control on Windows systems:

** Open the Services control panel. **
** For example, on Windows NT, select Start, point to Settings, select Control Panel, and then double-click the Services icon. **
** On Windows 2000, select Start, point to Administrative Tools, and select Services. **
** Locate the Application Server Control in the list of services. **
** The name of the service is usually consists of "Oracle", followed by the name of the home directory you specified during the installation, followed by the word "ASControl." For example, if you specified AS10g as the Oracle Home, the Service name would be: **
** OracleAS10gASControl **
** After you locate the service, you can use the Services control panel to start or stop the Application Server Control service. **
** By default, the Application Server Control service is configured to start automatically when the system starts. **

You can also start the Oracle Application Server Control console (iasconsole) on Windows using NET START Oracleoms10gASControl.

To stop the Oracle Application Server Control console (iasconsole) on Windows. use NET STOP Oracleoms10gASControl. Controlling the Database Control on UNIX

The Oracle Enterprise Manager 10g Database Control Console is a component of Oracle Enterprise Manager 10g that is installed as part of any Oracle Database 10g installation.

To control the Database Control, you use the emctl command-line utility that is available in the ORACLE_HOME/bin directory after you install Oracle Database 10g. Starting the Database Control on UNIX

To start the Database Control, as well the Management Agent and the Management Service associated with the Database Control:

** Set the following environment variables to identify the Oracle home and the system identifier (SID) for the database instance you want to manage: **
** ORACLE_HOME **
** ORACLE_SID **
** Change directory to the ORACLE_HOME/bin directory. **
** Enter the following command: **
** $PROMPT> ./emctl start dbconsole **

Stopping the Database Control on UNIX

To stop the Database Control, as well the Management Agent and the Management Service associated with the Database Control:

** Set the following environment variables to identify the Oracle home and the system identifier (SID) for the database instance you want to manage: **
** ORACLE_HOME **
** ORACLE_SID **
** Change directory to the ORACLE_HOME/bin directory. **
** Enter the following command: **
** $PROMPT> ./emctl stop dbconsole **

Starting and Stopping the Database Control on Windows

To start or stop the Database Control on Windows systems:

** Open the Services control panel. **
** For example, on Windows NT, select Start, point to Settings, select Control Panel, and then double-click the Services icon. **
** On Windows 2000, select Start, point to Administrative Tools, and select Services. **
** Locate the Database Control in the list of services. **
** The name of the service is usually consists of "Oracle", followed by the name of the home directory you specified during the installation and the database system identifier (SID), followed by the word "DBControl." For example, if you specified DBd10g as the Oracle Home, the Service name would be: **
** OracleDB10gDBControl **
** After you locate the service, you can use the Services control panel to start or stop the Database Control service. **
** By default, the Database Control service is configured to start automatically when the system starts. **

You can also start the Database Control on Windows using emctl start iasconsole as described in Stopping the Database Control on UNIX.


You are not authorized to post a reply.

Active Forums 4.2
Vigilant Technologies
Vigilant Technologies is a certified 8(a), Veteran Owned company headquartered in Chandler, Arizona. We provide products, services and enterprise-wide integration of innovative IT solutions to commercial, Federal, State and Local government clients. Our Leading edge services include Private/Hybrid Cloud, Server Consolidation, Visualization implementation, and Infrastructure Management.
Engage with us
Copyright 2006 - 2013 Vigilant Support   |  Privacy Statement  |  Terms Of Use