Skip Headers
Oracle® Enterprise Manager Cloud Control Administrator's Guide
12c Release 4 (12.1.0.4)

E24473-31
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

20 Starting and Stopping Enterprise Manager Components

This chapter explains how to use the Enterprise Manager command line utility (emctl) to start and stop the Management Services, the Management Agent, and Cloud Control.

This chapter also explains the various emctl commands for Management Service and Management Agent and how to use log information to troubleshoot emctl.

Following are the sections in this chapter:

20.1 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:

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

When you start the agent on UNIX systems, it starts the parent watchdog process and the child Java process for the agent. The watchdog monitors the agent Java process and attempts to start it if it fails abnormally.

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

  1. Change directory to the AGENT_INSTANCE_HOME/bin directory.

  2. Use the appropriate command described in Table 20-1.

    For example, to stop the Management Agent, enter the following commands:

    $PROMPT> cd AGENT_INSTANCE_HOME/bin
    $PROMPT> emctl stop agent
    

Table 20-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 20-1 Checking the Status of the Management Agent

$ ./emctl status agent
Oracle Enterprise Manager Cloud Control 12c Release 4  
Copyright (c) 1996, 2014 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
Agent Version          : 12.1.0.4.0
OMS Version            : 12.1.0.4.0
Protocol Version       : 12.1.0.1.0
Agent Home             : /scratch/agtRC2/agent_inst
Agent Log Directory    : /scratch/agtRC2/agent_inst/sysman/log
Agent Binaries         : /scratch/agtRC2/core/12.1.0.4.0
Agent Process ID       : 3104
Parent Process ID      : 3040
Agent URL              : https://slc03ljl.us.oracle.com:3872/emd/main/
Local Agent URL in NAT : https://slc03ljl.us.oracle.com:3872/emd/main/
Repository URL         : https://slc03ljl.us.oracle.com:4902/empbs/upload
Started at             : 2014-03-17 13:57:24
Started by user        : aime
Operating System       : Linux version 2.6.18-308.0.0.0.1.el5xen (amd64)
LLast Reload           : (none)
Last successful upload                       : 2014-04-08 21:48:35
Last attempted upload                        : 2014-04-08 21:48:35
Total Megabytes of XML files uploaded so far : 28.79
Number of XML files pending upload           : 0
Size of XML files pending upload(MB)         : 0
Available disk space on upload filesystem    : 19.01%
Collection Status                            : Collections enabled
Heartbeat Status                             : Ok
Last attempted heartbeat to OMS              : 2014-04-08 21:50:28
Last successful heartbeat to OMS             : 2014-04-08 21:50:28
Next scheduled heartbeat to OMS              : 2014-04-08 21:51:28
---------------------------------------------------------------
Agent is Running and Ready

Example 20-2

$. /emctl status agent
Oracle Enterprise Manager Cloud Control 12c Release 4  
Copyright (c) 1996, 2014 Oracle Corporation.  All rights reserved.
---------------------------------------------------------------
Agent Version          : 12.1.0.4.0
OMS Version            : 12.1.0.4.0
Protocol Version       : 12.1.0.1.0
Agent Home             : /scratch/agtR05/agent_inst
Agent Log Directory    : /scratch/agtR05/agent_inst/sysman/log
Agent Binaries         : /scratch/agtR05/core/12.1.0.4.0
Agent Process ID       : 11802
Parent Process ID      : 11740
Agent URL              : https://example.com:3872/emd/main/
Local Agent URL in NAT : https://example.com:3872/emd/main/
Repository URL         : https://example.com:4901/empbs/upload
Started at             : 2014-03-06 11:10:57
Started by user        : user1
Operating System       : Linux version 2.6.18-308.0.0.0.1.el5xen (amd64)
Last Reload            : (none)
Last successful upload                       : 2014-03-10 21:56:02
Last attempted upload                        : 2014-03-10 21:56:02
Total Megabytes of XML files uploaded so far : 6.8
Number of XML files pending upload           : 0
Size of XML files pending upload(MB)         : 0
Available disk space on upload filesystem    : 25.40%
Collection Status                            : Collections enabled
Heartbeat Status                             : Ok
Last attempted heartbeat to OMS              : 2014-03-10 22:00:15
Last successful heartbeat to OMS             : 2014-03-10 22:00:15
Next scheduled heartbeat to OMS              : 2014-03-10 22:01:15
 
---------------------------------------------------------------
Agent is Running and Ready

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, add the following parameters to the common environment file:

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.

20.1.2 Starting and Stopping the Management Agent on Windows

When you install the Oracle Management Agent on a Windows system, the installation procedure creates one new service 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 Section 20.2.1 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 20-2 describes the Windows service that you use to control the Management Agent.

Table 20-2 Service Installed and Configured When You Install the Management Agent on Windows

Component Service Name Format Description

Oracle Management Agent

Oracle<agent_home>Agent

For example:

OracleOraHome1Agent

Use this to start and stop the Management Agent.


20.1.3 Checking the Status of the Management Agent on Windows

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

  1. Change directory to the following location in the AGENT_INSTANCE_HOME directory:

    <install directory of agent>\core\12.1.0.x.0\bin
    

    For example, d:\12cagent\core\12.1.0.3.0\bin.

  2. 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 ().

20.1.4 Troubleshooting Management Agent Startup Errors

If the agent fails to start, see the emctl.log and emagent.nohup log files for details. The log files are saved in the $AGENT_INSTANCE_HOME/sysman/logs directory. Following are common issues and troubleshooting suggestions:

20.1.4.1 Management Agent starts up but is not ready

The Management Agent goes through the following process when it starts up:

  1. Starting up (the Management Agent has just received the request to start up and is going to start the initialization sequence)

  2. Initializing (the Management Agent is iterating over each of its components and is initializing them)

  3. Ready (All components have been initialized and the Management Agent is ready to accept requests)

The command to start the Management Agent (emctl start agent) has a default timeout of 120 seconds. At the end of that timeout, it will return control to the caller and will indicate what the last state of the Management Agent was when it returns control. Depending on the number of targets being monitored by the Management Agent, step 2 listed above could take a long time and it is possible that when the command exits, the state of the agent is "Initializing" and the command reports that the "agent is running but is not ready".

You can increase the timeout by setting an environment variable "EMAGENT_TIME_FOR_START_STOP". The value should indicate the number of seconds to wait before returning control to the caller.

20.1.4.2 Management Agent fails to start due to time zone mismatch between agent and OMS

The Management Agent uses the time zone set in emd.properties file. During the install process of the Management Agent, the agent and the host target are registered with the OMS along with the time zone. If the Management Agent's time zone is modified at any point after the installation, the OMS will signal the Management Agent to shut down as soon as it detects this mismatch.

To reset the Management Agent's time zone, run the following command:

emctl resettz agent

For more information about setting the time zone for the agent, see Section 20.7.4.

20.1.4.3 Management Agent fails to start due to possible port conflict

If the Management Agent cannot start and emctl reports that there is a possible port conflict, check the Management Agent's port (based on emd.properties:EMD_URL) and see if there is another application, such as another agent, running on the machine that is already bound to the port.

To resolve this issue, stop the application currently bound to the Management Agent's port.

20.1.4.4 Management Agent fails to start due to failure of securing or unsecuring

Securing or unsecuring of the Management Agent can fail if the password to secure the agent against the OMS is incorrect or if the OMS is locked or down. You can find the reason for the failure in the <agent state directory>/sysman/log/secure.log file.

20.2 Controlling the Oracle Management Service

Note:

The user who can start or stop the OMS is the Oracle Software Owner.

When you start the Management Service, the following services are started:

  1. OPMN process. This is the watchdog for the Apache process. The OPMN process starts the Apache process if it crashes.

  2. Apache processes to start the HTTP server.

  3. Node Manager Java process. This is the watchdog for the Managed Server and Admin Server processes. It restarts the Managed Server and Admin Server processes if they crash.

  4. Admin Server Java process (if the command to start OMS is executed on the first OMS machine). This is the WebLogic Server instance that maintains configuration data for configured Enterprise Manager domain.

  5. Managed Server Java process. This is the Managed WebLogic Server on which Enterprise Manager application is deployed.

  6. (On Windows only) Node Manager service process. This is the Windows service for starting and stopping the Node Manager (equivalent to the Node Manager process on Linux).

  7. (On Windows only) OMS service process. This is the Windows service for starting and stopping the OMS.

  8. BI Publisher Server Java process, if it has been configured on the system. This is the Managed WebLogic Server on which the Oracle BI Publisher application is deployed.

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

20.2.1 Controlling the Management Service on UNIX

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

  1. Change directory to the ORACLE_HOME/bin directory in the Management Service home.

  2. Use the appropriate command described in Table 20-3.

    For example, to stop the Management Service, enter the following commands:

    $PROMPT> cd bin
    $PROMPT> ./emctl stop oms
    

Table 20-3 Starting, Stopping, and Checking the Status of the Management Service

Command Purpose

emctl start oms

Starts the Fusion Middleware components required to run the Management Service. Specifically, this command starts HTTP Server, the Node Manager, OPMN process, and the managed server on which the Management Service is deployed. In addition, if this command is run on the host that has the Administration Server, then the Administration Server is also started. Similarly, if this command is run on a host that has Oracle BI Publisher configured, then Oracle BI Publisher is also started.

emctl stop oms

Stops the OMS managed server and HTTP server but leaves Node Manager and Administration Server running.

Note: The emctl stop oms command does not stop Fusion Middleware.

Use emctl stop oms -all to stop all processes including Administration Server, HTTP Server, Node Manager, management server, and Oracle BI Publisher (if it is configured on the host).

emctl status oms

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

Run emctl status oms -details to view information about the configuration of the management service such as ports being used and the URLs for console and upload.

emctl config oms -set_startup_mode [pbs_only | console_only | normal]

Configures the startup mode of the OMS. This command cannot be executed on the primary OMS.

The three startup modes are as below:

  • pbs_only: If the startup mode is configured to pbs_only, then the command emctl start oms starts only the PBS application.

  • console_only: If the startup mode is configured to console_only, then the command emctl start oms starts only the console application.

  • normal: If the startup mode is configured to normal, then the command emctl start oms starts both the PBS application and the console application.


20.2.2 Controlling the Management Service on Windows

When you install the Oracle Management Service on a Windows system, the installation procedure creates a new service 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, then Administrative Tools from the Start menu.

Note:

The emctl utility described in Section 20.2.1 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 20-4 describes the Windows service that you use to control the Oracle Management Service.

Table 20-4 Service Installed and Configured When Installing the Oracle Management Service on Windows

Component Service Name Format Description

Oracle Management Server

OracleManagementServer_EMGC_OMS1_1

Use this service to start and stop all components that were installed and configured as part of the Management Service J2EE application.


20.2.3 Troubleshooting Oracle Management Service Startup Errors

Following are the log files you can check if the OMS fails to start:

Management Service Fails to Start

Check the logs located as indicated in Table 20-5. The INSTANCE_HOME mentioned in the table is the OMS instance home and n is the index of the OMS server.

Table 20-5 OMS Log Files Location

OMS Log File Log File Location

emctl log file

$INSTANCE_HOME/sysman/log/emctl.log file

Managed Server log files

$INSTANCE_HOME/user_projects/domains/<DOMAIN_NAME>/servers/EMGC_OMS<n>/logs/EMGC_OMS<n>.log

$INSTANCE_HOME/user_projects/domains/<DOMAIN_NAME>/servers/EMGC_OMS<n>/logs/EMGC_OMS<n>.out

OMS log files

$INSTANCE_HOME/sysman/log/emoms_pbs.log

$INSTANCE_HOME/sysman/log/emoms_pbs.trc

$INSTANCE_HOME/sysman/log/emoms.trc

$INSTANCE_HOME/sysman/log/emoms.log

Node Manager log files

$INSTANCE_HOME/NodeManager/emnodemanager/nodemanager.log


WebTier Service Fails to Start

Check logs under <WebTier Instance Home>/diagnostics folder in case WebTier start fails.

20.3 Setting Java Memory Arguments for Oracle Management Service

If you have changed the default, out-of-box memory settings for an OMS, then before upgrading the OMS, perform the following steps to preserve the changes. Otherwise, the changes will be lost during upgrade.

  1. Run the following command on all the OMS instances:

    $<OMS_HOME>/bin/emctl set property -name 'JAVA_EM_MEM_ARGS' -value '<java_memory_arguments>'

    For example,

    $<OMS_HOME>/bin/emctl set property -name 'JAVA_EM_MEM_ARGS' -value '-Xms256m -Xmx1740m'

  2. Stop all the OMS instances and all the Oracle WebLogic-related services, and then start them again.

    $<OMS_HOME>/bin/emctl stop oms -all

    $<OMS_HOME>/bin/emctl start oms

20.4 Controlling JVMD and ADP Engines

This section contains the following:

20.4.1 Controlling JVMD Engines

Table 20-6 lists the commands used to control JVMD Engines.

Table 20-6 Commands Used to Control JVMD Engines

Command Purpose

emctl extended oms jvmd list

Lists all the JVMD Engines.

emctl extended oms jvmd start -server=<server_name1>,<server_name2>...

Starts specified JVMD Engines. Accepts the engine names as a comma separated list.

emctl extended oms jvmd start -all

Starts all JVMD Engines.

emctl extended oms jvmd stop -server=<server_name1>,<server_name2>...

Stops specified JVMD Engines. Accepts the engine names as a comma separated list.

emctl extended oms jvmd stop -all

Stops all JVMD Engines.

emctl extended oms jvmd status -server=<server_name1>,<server_name2>...

Displays the status of specified JVMD Engines. Accepts the engine names as a comma separated list.

emctl extended oms jvmd status -all

Displays the status of all JVMD Engines.

emctl extended oms jvmd -help

Displays the list of available commands for the JVMD verb.


20.4.2 Controlling ADP Engines

Table 20-7 lists the commands used to control ADP Engines.

Table 20-7 Commands Used to Control ADP Engines

Command Purpose

emctl extended oms adp list

Lists all ADP Engines.

emctl extended oms adp start -server=<server_name1>,<server_name2>...

Starts specified ADP Engines. Accepts the engine names as a comma separated list.

emctl extended oms adp start -all

Starts all ADP Engines.

emctl extended oms adp stop -server=<server_name1>,<server_name2>...

Stops specified ADP Engines. Accepts the engine names as a comma separated list.

emctl extended oms adp stop -all

Stops all ADP Engines.

emctl extended oms adp status -server=<server_name1>,<server_name2>...

Displays the status of specified ADP Engines. Accepts the engine names as a comma separated list.

emctl extended oms adp status -all

Displays the status of all ADP Engines.

emctl extended oms adp -help

Displays the list of available commands for the ADP verb.


20.5 Guidelines for Starting Multiple Enterprise Manager Components on a Single Host

Oracle Enterprise Manager components are used to manage a variety of Oracle software products. In most cases, in a production environment, you will want to distribute your database and WebLogic Server instances among multiple hosts to improve performance and availability of your software resources. However, in cases where you must install multiple WebLogic Servers or databases on the same host, consider the following guidelines.

When you start Fusion Middleware Control, the Management Agent, or Database Control, Enterprise Manager immediately begins gathering important monitoring data about the host and its managed targets. Keep this in mind when you develop a process for starting the components on the host.

Specifically, consider staggering the startup process so that each Enterprise Manager process has a chance to start before the next process begins its startup procedure. Using a staggered startup procedure ensures that the processes are not in contention for resources during the CPU-intensive startup phase for each component. However, in the case of a system restart, /etc/init.d/gcstartup script which is registered during the EM deployment ensures that the OMS and the Management Agent are started automatically in a staggered manner.

20.6 Starting and Stopping Oracle Enterprise Manager 12c Cloud Control

As described in the previous sections, you use separate commands to control the Oracle Management Service and Management Agents.

The following sections describe how to stop and start all the Cloud Control components that are installed by the Oracle Enterprise Manager 12c Cloud Control Console installation procedure.

You can use this procedure to start all the framework components after a system reboot or to shutdown all the components before bringing the system down for system maintenance.

20.6.1 Starting Cloud Control and All Its Components

The following procedure summarizes the steps required to start all the components of the Cloud Control. For example, use this procedure if you have restarted the host computer and all the components of the Cloud Control have been installed on that host.

To start all the Cloud Control components on a host, use the following procedure:

  1. If your Oracle Management Repository resides on the host, change directory to the Oracle Home for the database where you installed the Management Repository and start the database and the Net Listener for the database:

    1. Set the ORACLE_HOME environment variable to the Management Repository database home directory.

    2. Set the ORACLE_SID environment variable to the Management Repository database SID (default is asdb).

    3. Start the Net Listener:

      $PROMPT> $ORACLE_HOME/bin/lsnrctl start
      
    4. Start the Management Repository database instance:

      ORACLE_HOME/bin/sqlplus /nolog
      SQL> connect SYS as SYSDBA
      SQL> startup
      SQL> quit
      

      See Also:

      Oracle Database Administrator's Guide for information about starting and stopping an Oracle Database.
  2. Start the Oracle Management Service:

    $PROMPT> OMS_HOME/bin/emctl start oms
    
  3. Change directory to the home directory for the Oracle Management Agent and start the Management Agent:

    $PROMPT> AGENT_HOME/bin/emctl start agent
    

    Note:

    Be sure to run the emctl start agent command in the Oracle Management Agent home directory and not in the Management Service home directory.

20.6.2 Stopping Cloud Control and All Its Components

The following procedure summarizes the steps required to stop all the components of the Cloud Control. For example, use this procedure if you have installed all the components of the Cloud Control on the same host you want to shut down or restart the host computer.

To stop all the Cloud Control components on a host, use the following procedure:

  1. Stop the Oracle Management Service:

    $PROMPT> $ORACLE_HOME/bin/emctl stop oms -all
    
  2. Change directory to the home directory for the Oracle Management Agent and stop the Management Agent:

    $PROMPT> AGENT_HOME/bin/emctl stop agent
    

    Note:

    Be sure to run the emctl stop agent command in the Oracle Management Agent home directory and not in the Oracle Management Service home directory.
  3. If your Oracle Management Repository resides on the same host, follow these steps:

    1. Set the ORACLE_HOME environment variable to the Management Repository database home directory.

    2. Set the ORACLE_SID environment variable to the Management Repository database SID (default is asdb).

    3. Stop the database instance:

      $PROMPT> ORACLE_HOME/bin/sqlplus /nolog
      SQL> connect SYS as SYSDBA
      SQL> shutdown
      SQL> quit
      

      See Also:

      Oracle Database Administrator's Guide for information about starting and stopping an Oracle Database.
    4. Stop the Net Listener:

      $PROMPT> $ORACLE_HOME/bin/lsnrctl stop
      

20.7 Additional Management Agent Commands

The following sections describe additional emctl commands you can use to control the Management Agent:

20.7.1 Uploading and Reloading Data to the Management Repository

Under normal circumstances, the Management Agent uploads information about your managed targets to the Management Service at regular intervals.

To use these commands, change directory to the AGENT_HOME/bin directory (UNIX) or the AGENT_HOME\bin directory (Windows) and enter the appropriate command as described in Table 20-8.

Table 20-8 Manually Reloading and Uploading Management Data

Command Description

emctl upload (agent)

Use this command to force an immediate upload of the current management data from the managed host to the Management Service. Use this command instead of waiting until the next scheduled upload of the data.

emctl reload (agent)

This command can be used to apply the changes after you have manually modified the emd.properties file. For example, to change the upload interval, emd.properties can be modified, and emctl reload can then be run.

Note: Oracle does not support manual editing of the targets.xml files unless the procedure is explicitly documented or you are instructed to do so by Oracle Support.


20.7.2 Specifying New Target Monitoring Credentials

To monitor the performance of your database targets, Enterprise Manager connects to your database using a database user name and password. This user name and password combination is referred to as the database monitoring credentials.

Note:

The instructions in this section are specific to the monitoring credentials for a database target, but you can use this procedure for any other target type that requires monitoring credentials. For example, you can use this procedure to specify new monitoring credentials for your Oracle Management Service and Management Repository.

When you first add an Oracle9i Database target, or when it is added for you during the installation of the Management Agent, Enterprise Manager uses the DBSNMP database user account and the default password for the DBSNMP account as the monitoring credentials.

When you install Oracle Database 11g, you specify the DBSNMP monitoring password during the database installation procedure.

As a result, if the password for the DBSNMP database user account is changed, you must modify the properties of the database target so that Enterprise Manager can continue to connect to the database and gather configuration and performance data.

Similarly, immediately after you add a new Oracle Database 11g target to the Cloud Control, you may need to configure the target so it recognizes the DBSNMP password that you defined during the database installation. Otherwise, the Database Home page may display no monitoring data and the status of the database may indicate that there is a metric collection error.

Note:

You can modify the Enterprise Manager monitoring credentials by using the Oracle Enterprise Manager 12c Cloud Control Console.

20.7.3 Listing the Targets on a Managed Host

There are times when you need to provide the name and type of a particular target you are managing. For example, you must know the target name and type when you are setting the monitoring credentials for a target.

To list the name and type of each target currently being monitored by a particular Management Agent:

  1. Change directory to the AGENT_HOME/bin directory (UNIX) or the AGENT_HOME\bin directory (Windows).

  2. Enter the following command to list new monitoring credentials:

    $PROMPT>./emctl config agent listtargets
    
    
    

    shows the typical output of the command.

Example 20-3 Listing the Targets on a Managed Host

$. /emctl config agent listtargets
Oracle Enterprise Manager Cloud Control 12c Release 4
Copyright (c) 1996, 2014 Oracle Corporation.  All rights reserved.
[slc03ljl.us.oracle.com, host]
[slc03ljl.us.oracle.com:3872, oracle_emd]
[Management Services and Repository, oracle_emrep]
[slc03ljl.us.oracle.com:4891_Management_Service, oracle_oms]
[slc03ljl.us.oracle.com:4891_Management_Service_CONSOLE, oracle_oms_console]
[slc03ljl.us.oracle.com:4891_Management_Service_PBS, oracle_oms_pbs]
[agent12c10_151_slc03ljl.us.oracle.com, oracle_home]
[EM Management Beacon, oracle_beacon]
[/EMGC_GCDomain/GCDomain/EMGC_ADMINSERVER/FMW Welcome Page Application(11.1.0.0.0), j2ee_application]
[/EMGC_GCDomain/GCDomain/EMGC_OMS1/OCMRepeater, j2ee_application]
[/EMGC_GCDomain/GCDomain/EMGC_OMS1/emgc, j2ee_application]
[/EMGC_GCDomain/GCDomain/EMGC_OMS1/empbs, j2ee_application]
[/EMGC_GCDomain/GCDomain/EMGC_ADMINSERVER/mds-owsm, metadata_repository]
[/EMGC_GCDomain/GCDomain/EMGC_ADMINSERVER/mds-sysman_mds, metadata_repository]
[/EMGC_GCDomain/instance1/ohs1, oracle_apache]
[EMGC_GCDomain, oracle_ias_farm]
[/EMGC_GCDomain/GCDomain/EMGC_ADMINSERVER, weblogic_j2eeserver]
[/EMGC_GCDomain/GCDomain/EMGC_OMS1, weblogic_j2eeserver]
[/EMGC_GCDomain/GCDomain, weblogic_domain]
[oms12c10_145_slc03ljl.us.oracle.com, oracle_home]
[common12c10_163_slc03ljl.us.oracle.com, oracle_home]
[WebLogicServer10_3_6_0_slc03ljl.us.oracle.com_4348, oracle_home]
[webtier12c10_164_slc03ljl.us.oracle.com, oracle_home]

20.7.4 Changing the Management Agent Time Zone

The Management Agent may fail to start after the upgrade if it realizes that it is no longer in the same time zone that it was originally configured with.

You can reset the time zone used by the Management Agent using the following command:

emctl resetTZ agent

This command will correct the Management Agent side time zone and specify an additional command to be run against the Management Repository to correct the value there.

IMPORTANT:

Before you change the Management Agent time zone, first check to see if there are any blackouts that are currently running or scheduled to run on any targets managed by that Management Agent. Refer to Section 5.1.3.1 to know how to check for blackouts.

If any blackouts exist, then from the Cloud Control Console, stop all the scheduled and all the currently running blackouts on all targets monitored by that Management Agent. You can then change the Management Agent's time zone and later create new blackouts on the targets as needed.

20.7.5 Reevaluating Metric Collections

Use the following command to perform an immediate reevaluation of a metric collection:

emctl control agent runCollection <targetName>:<targetType> <colletionItemName>

where <collectionItemName> is the name of the Collection Item that collects the metric.

Performing this command causes the reevaluated value of the metric to be uploaded into the Management Repository, and possibly trigger alerts if the metric crosses its threshold.

Related metrics are typically collected together; collectively a set of metrics collected together is called a Metric Collection. Each Metric Collection has its own name. If you want to reevaluate a metric, you first need to determine the name of the Metric Collection to which it belongs, then the CollectionItem for that Metric Collection.

When you run the previous command to reevaluate the metric, all other metrics that are part of the same Metric Collection and Collection Item will also be reevaluated.

Perform the following steps to determine the Metric Collection name and Collection Item name for a metric:

  1. Go to $INSTALL_BASE/ngagent/plugins directory, where $INSTALL_BASE is the root of the installation. The Oracle Home of the Management Agent exists in this directory.

  2. Locate the XML file for the target type. For example, if you are interested in the host metric 'Filesystem Space Available(%)' metric, look for the host.xml file.

  3. In the xml file, look for the metric in which you are interested. The metric that you are familiar with is actually the display name of the metric. The metric name would be preceded by a tag that started with:

    <Label NLSID=

    For example, in the host.xml file, the metric 'Filesystem Space Available(%)" would have an entry that looks like this:

    <Label NLSID="host_filesys_pctAvailable">Filesystem Space Available (%) </Label>
    
  4. Once you have located the metric in the xml file, you will notice that its entry is part of a bigger entry that starts with:

    <Metric NAME=

    Take note of the value defined for "Metric NAME". This is the Metric Collection name. For example, for the 'Filesystem Space Available(%)' metric, the entry would look like this:

    <Metric NAME="Filesystems"

    So for the 'Filesystem Space Available(%)' metric, the Metric Collection name is 'Filesystems'.

  5. The Collection Item name for this Metric Collection needs to be determined next. Go to the $INSTALL_BASE/plugins/<plugin id directory, where $INSTALL_BASE is the Oracle Home of the Management Agent.

  6. In this directory, look for the collection file for the target type. In our example, this would be host.xml.

  7. In cases where a Metric Collection is collected by itself, there would be a single Collection Item of the same name in the collection file. To determine if this is the case for your Metric Collection, look for an entry in the collection file that starts with:

    <CollectionItem NAME=

    where the value assigned to the CollectionItem NAME matches the Metric NAME in step (4).

    For the 'Filesystem Space Available(%)' metric, the entry in the collection file would look like:

    <CollectionItem NAME = "Filesystems"

  8. If you find such an entry, then the value assigned to "CollectionItem NAME" is the collection item name that you can use in the emctl command.

  9. Otherwise, this means the Metric Collection is collected with other Metric Collections under a single Collection Item. To find the Collection Item for your Metric Collection, first search for your Metric Collection. It should be preceded by the tag:

    <MetricColl NAME=

    Once you have located it, look in the file above it for: <CollectionItem NAME=

    The value associated with the CollectionItem NAME is the name of the collection item that you should use in the emctl command.

    For example if the you want to reevaluate the host metric "Open Ports", using the previous steps, you would do the following:

    1. Go to the $INSTALL_BASE/plugins/<plugin id directory where $INSTALL_BASE is the Oracle Home of the Management Agent. Look for the host.xml file and in that file locate: <Metric NAME="openPorts".

    2. Then go to the $INSTALL_BASE/ngagent/plugins/default_collection directory. Look for the host.xml file and in that file look for <CollectionItem NAME="openPorts".

      Failing this, look for <MetricColl NAME="openPorts".

    3. Look above this entry in the file to find the <CollectionItem NAME= string and find <CollectionItem NAME="oracle_security".

    The CollectionItem NAME oracle_security is what you would use in the emctl command to reevaluate the Open Ports metric.