| Oracle® Enterprise Manager Administration 10g Release 5 (10.2.0.5) Part Number E14586-03 |
|
|
PDF · Mobi · ePub |
| Oracle® Enterprise Manager Administration 10g Release 5 (10.2.0.5) Part Number E14586-03 |
|
|
PDF · Mobi · ePub |
This chapter explains how to use the Enterprise Manager command line utility (emctl) to start and stop the Management Service, the Management Agent, the Grid Control console, the Application Server Control Console, and Database Control.
This chapter also explains the various emctl commands, exit codes, and how to use log information to troubleshoot emctl.
Following are the sections in this chapter:
Guidelines for Starting Multiple Enterprise Manager Components on a Single Host
Starting and Stopping Oracle Enterprise Manager 10g Grid Control
The following sections describe how to use the Enterprise Manager command line utility (emctl) to control the Oracle Management Agent:
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 |
|---|---|
|
Starts the Management Agent |
|
|
Stops the Management 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 (c) 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 URL : https://stadj32.us.oracle.com:3872/emd/main/ Repository URL : 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.
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:
Theemctl 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 |
Oracle<agent_home>Agent For example: OracleOraHome1Agent |
Use this to start and stop the Management Agent. |
Oracle<oracle_home>SNMPPeerEncapsulator 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<oracle_home>SNMPPeerMasterAgent 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> <AGENT_HOME>/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.
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 ().
The following sections describe how to control the Oracle Management Service:
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:
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.
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 |
|---|---|
|
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 |
|
|
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". |
|
|
Displays a message indicating whether or not the Management Service is running. |
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 CacheOracle 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 |
|---|---|
|
Starts Oracle Application Server Web Cache. |
|
|
Stops Oracle Application Server Web Cache. |
|
|
Displays a message showing the status of all the application server components managed by OPMN, including Oracle Application Server Web Cache. |
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:
Theemctl 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 |
|---|---|---|
Oracle<oracle_home>ASControl 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<oracle_home>ProcessManager 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. |
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
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
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.
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.
To start the Database Control, as well the Management Agent and the Management Service associated with the Database Control:
To stop the Database Control, as well the Management Agent and the Management Service associated with the Database Control:
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.
Oracle Enterprise Manager 10g components are used to manage a variety of Oracle software products. For example, each time you install Oracle Application Server 10g (9.0.4) instance, you also install an Application Server Control. Similarly, each time you install Oracle Database 10g, you install a Database Control. In addition, if you want to centrally manage your system with Database Control, the Management Agent is also installed on each host you monitor.
In most cases, in a production environment, you will want to distribute your database and application server instances among multiple hosts to improve performance and availability of your software resources. However, in rare cases where you must install multiple application servers or databases on the same host, consider the following guidelines.
When you start Application Server Control, the Management Agent, or the 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.
For example, suppose you have installed OracleAS Infrastructure 10g, the J2EE and Web Cache application server installation type, and the Management Agent on the same host. When you start up all the components (for example, after a restart of the system), use a process such as the following:
Use the opmnctl startall command to start all the OPMN-managed processes in the OracleAS Infrastructure 10g home directory.
Wait 15 seconds.
Use the emctl start iasconsole command to start the Application Server Control in the OracleAS Infrastructure 10g home directory.
Wait 15 seconds.
Use the opmnctl startall command to start all the OPMN-managed processes in the J2EE and Web Cache home directory.
Wait 15 seconds.
Use the emctl start iasconsole command to start the Application Server Control in the J2EE and Web Cache home directory.
Wait 15 seconds.
Use the emctl start agent command to start the Management Agent for the host.
Using a staggered startup procedure such as the preceding example will ensure that the processes are not in contention for resources during the CPU-intensive startup phase for each component.
As described in the previous sections, you use separate commands to control the Oracle Management Service, Oracle Management Agent, and the Oracle Application Server components on which the Grid Control depends.
The following sections describe how to stop and start all the Grid Control components that are installed by the Oracle Enterprise Manager 10g Grid 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.
The following procedure summarizes the steps required to start all the components of the Grid Control. For example, use this procedure if you have restarted the host computer and all the components of the Grid Control have been installed on that host.
To start all the Grid Control components on a host, use the following procedure:
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:
Set the ORACLE_HOME environment variable to the Management Repository database home directory.
Set the ORACLE_SID environment variable to the Management Repository database SID (default is asdb).
Start the Net Listener:
$PROMPT> $ORACLE_HOME/bin/lsnrctl start
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 DatabaseStart the Oracle Management Service:
$PROMPT> ORACLE_HOME/bin/emctl start oms
Start OracleAS Web Cache:
$PROPMT> $ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=WebCache
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 theemctl start agent command in the Oracle Management Agent home directory and not in the Management Service home directory.Optionally, start the Application Server Control Console, which is used to manage the Oracle Application Server instance that is used to deploy the Management Service:
$PROMPT> $ORACLE_HOME/bin/emctl start iasconsole
The following procedure summarizes the steps required to stop all the components of the Grid Control. For example, use this procedure if you have installed all the components of the Grid Control on the same host you want to shut down or restart the host computer.
To stop all the Grid Control components on a host, use the following procedure:
Stop the Oracle Management Service:
$PROMPT> $ORACLE_HOME/bin/emctl stop oms
If necessary, stop the Application Server Control Console, which is used to manage the Oracle Application Server instance used to deploy the Management Service:
$PROMPT> $ORACLE_HOME/bin/emctl stop iasconsole
Stop all the Oracle Application Server components, such as the Oracle HTTP Server the OracleAS Web Cache:
$PROMPT> $ORACLE_HOME/opmn/bin/opmnctl stopall
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 theemctl stop agent command in the Oracle Management Agent home directory and not in the Oracle Application Server home directory.If your Oracle Management Repository resides on the same host, change directory to the Oracle Home for the database where you installed the Management Repository and stop the database and the Net Listener for the database:
Set the ORACLE_HOME environment variable to the Management Repository database home directory.
Set the ORACLE_SID environment variable to the Management Repository database SID (default is asdb).
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 DatabaseStop the Net Listener:
$PROMPT> $ORACLE_HOME/bin/lsnrctl stop
The following sections describe additional emctl commands you can use to control the Management Agent:
Under normal circumstances, the Management Agent uploads information about your managed targets to the Management Service at regular intervals.
However, there are two Enterprise Manager commands that can help you force an immediate upload of data to the Management Service or a reload of the target definitions and attributes stored in the Management Agent home directory.
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 8-6.
Table 8-6 Manually Reloading and Uploading Management Data
| Command | Purpose |
|---|---|
|
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. |
|
|
This command can be used to modify the Note: Oracle does not support manual editing of the |
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 10g, 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 10g target to the Grid 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.
You can modify the Enterprise Manager monitoring credentials by using the Oracle Enterprise Manager 10g Grid Control Console or by using the Enterprise Manager command line utility (emctl).
To modify the password for the DBSNMP account in the Oracle Enterprise Manager 10g Grid Control Console:
Click the Targets tab in the Grid Control console.
Click the Database subtab to list the database targets you are monitoring.
Select the database and click Configure.
Enterprise Manager displays the Configure Database: Properties page.
Enter the new password for the DBSNMP account in the Monitor Password field.
Click Test Connection to confirm that the monitoring credentials are correct.
If the connection is successful, continue to the end of the Database Configuration wizard and click Submit.
To enter new monitoring credentials with the Enterprise Manager command-line utility:
Change directory to the AGENT_HOME/bin directory (UNIX) or the AGENT_HOME\bin directory (Windows).
Enter the following command to specify new monitoring credentials:
$PROMPT>./emctl config agent credentials [Target_name[:Target_Type]]
To determine the correct target name and target type, see "Listing the Targets on a Managed Host".
shows an example of the prompts and the output you receive from the command.
Example 8-2 Modifying the Database Monitoring Credentials
$PROMPT>./emctl config agent credentials emrep10.acme.com:oracle_database Oracle Enterprise Manager 10g Release 10.1.0.2.0 Copyright (c) 2002, 2003 Oracle Corporation. All rights reserved. Name = emrep10.us.oracle.com, Type = oracle_database Want to change for "UserName" (y/n):n Want to change for "password" (y/n):y Enter the value for "password" :******* EMD reload completed successfully
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:
Change directory to the AGENT_HOME/bin directory (UNIX) or the AGENT_HOME\bin directory (Windows).
Enter the following command to specify new monitoring credentials:
$PROMPT>./emctl config agent listtargets [AGENT_HOME]
shows the typical output of the command.
Example 8-3 Listing the Targets on a Managed Host
./emctl config agent listtargets Oracle Enterprise Manager 10g Release 10.1.0.2.0 Copyright (c) 2002, 2003 Oracle Corporation. All rights reserved. [usunnab08.us.oracle.com, host] [LISTENER_usunnab08.us.oracle.com, oracle_listener] [EnterpriseManager.usunnab08.us.oracle.com_HTTP Server, oracle_apache] [EnterpriseManager.usunnab08.us.oracle.com_home, oc4j] [EnterpriseManager.usunnab08.us.oracle.com_Web Cache, oracle_webcache] [EnterpriseManager.usunnab08.us.oracle.com, oracle_ias] [EnterpriseManager.usunnab08.us.oracle.com_OC4J_EM, oc4j] [EnterpriseManager.usunnab08.us.oracle.com_OC4J_Demos, oc4j] [EM_Repository, oracle_emrep] [usunnab08.us.oracle.com:1813, oracle_emd] [EM Website, website] [emrep10.us.oracle.com, oracle_database]
Blackouts allow Enterprise Manager users to suspend management data collection activity on one or more managed targets. For example, administrators use blackouts to prevent data collection during scheduled maintenance or emergency operations.
See Also:
The "Systems Monitoring" chapter in Oracle Enterprise Manager Concepts for more information about Enterprise Manager blackoutsYou can control blackouts from the Oracle Enterprise Manager 10g Grid Control Console or from the Enterprise Manager command line utility (emctl). However, if you are controlling target blackouts from the command line, you should not attempt to control the same blackouts from the Grid Control console. Similarly, if you are controlling target blackouts from the Grid Control console, do not attempt to control those blackouts from the command line.
See Also:
"Creating, Editing, and Viewing Blackouts" in the Enterprise Manager online help for information about controlling blackouts from the Grid Control consoleFrom the command line, you can perform the following blackout functions:
Starting Immediate Blackouts
Stopping Immediate Blackouts
Checking the Status of Immediate Blackouts
Note:
When you start a blackout from the command line, any Enterprise Manager jobs scheduled to run against the blacked out targets will still run. If you use the Grid Control console to control blackouts, you can optionally prevent jobs from running against blacked out targets.To use the Enterprise Manager command-line utility to control blackouts:
Change directory to the AGENT_HOME/bin directory (UNIX) or the AGENT_HOME\bin directory (Windows).
Enter the appropriate command as described in Table 8-7.
Note:
When you start a blackout, you must identify the target or targets affected by the blackout. To obtain the correct target name and target type for a target, see "Listing the Targets on a Managed Host".Table 8-7 Summary of Blackout Commands
Use the following examples to learn more about controlling blackouts from the Enterprise Manager command line:
To start a blackout called "bk1" for databases "db1" and "db2," and for Oracle Listener "ldb2," enter the following command:
$PROMPT> emctl start blackout bk1 db1 db2 ldb2:oracle_listener -d 5 02:30
The blackout starts immediately and will last for 5 days 2 hours and 30 minutes.
To check the status of all the blackouts on a managed host:
$PROMPT> emctl status blackout
To stop blackout "bk2" immediately:
$PROMPT> emctl stop blackout bk2
To start an immediate blackout called "bk3" for all targets on the host:
$PROMPT> emctl start blackout bk3 -nodeLevel
To start an immediate blackout called "bk3" for database "db1" for 30 minutes:
$PROMPT> emctl start blackout bk3 db1 -d 30
To start an immediate blackout called "bk3" for database "db2" for five hours:
$PROMPT> emctl start blackout bk db2 -d 5:00
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.
There were bugs in Enterprise Manager Releases 10.1.0.2 and 10.1.0.3 RAC Management Agent installs that caused the Management Agent to be configured with a UTC timezone.
You can correct 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 target managed by that Management Agent.
To check for blackouts:
In the Grid Control Console, go to the All Targets page under the Targets tab, and locate the Management Agent in the list of targets. Click on the Management Agent's name. This brings you to the Management Agent's home page.
The list of targets monitored by the Management Agent are listed in the "Monitored Targets" section.
For each of target in the list:
Click the target name. This brings you to the target's home page.
In the Related Links section of the home page, click the Blackouts link. This allows you to check any currently running blackouts or blackouts that are scheduled in the future for this target.
If such blackouts exist, then:
From the Grid Control Console, stop all currently running blackouts on all targets monitored by that Management Agent.
From the Grid Control Console, stop all scheduled blackouts on all targets monitored by that Management Agent.
Once you have stopped all currently running and scheduled blackouts, you can run the emctl resetTZ agent command to change the Management Agent's time zone.Once you have changed the Management Agent's time zone, create new blackouts on the targets as needed.
If you are running a Management Agent Release 10.2, then you can 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:
Go to $ORACLE_HOME/sysman/admin/metadata directory, where $ORACLE_HOME is the Oracle Home of the Management Agent.
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.
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>
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'.
The Collection Item name for this Metric Collection needs to be determined next. Go to the $ORACLE_HOME/sysman/admin/default_collection directory, where $ORACLE_HOME is the Oracle Home of the Management Agent.
In this directory, look for the collection file for the target type. In our example, this would be host.xml.
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"
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.
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:
Go to the $ORACLE_HOME/sysman/admin/metadata directory where $ORACLE_HOME is the Oracle Home of the Management Agent. Look for the host.xml file and in that file locate: <Metric NAME="openPorts".
Then go to the $ORACLE_HOME/sysman/admin/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".
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.
This section lists the emctl commands for the Enterprise Manager agent.
| emctl Command | Description |
|---|---|
|
emctl start | stop agent |
Starts or stops agent. |
|
emctl start | stop | status subagent |
Starts or stops subagent. |
|
emctl status agent |
Lists the status of agent. |
|
emctl status agent -secure [-omsurl <http://<oms-hostname>:<oms-unsecure-port>/em/*>] |
Lists the secure status of the agent and the port on which the agent is running in secure mode and also the OMS security status of the agent it points to. This command also gives the OMS secure port. Below is an example output: bash-3.00$ emctl status agent -secure Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0. Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved. Checking the security status of the Agent at location set in /ade/aime_cpap4_ag/oracle/sysman/config/emd.properties... Done. Agent is secure at HTTPS Port 1838. Checking the security status of the OMS at http://staxe05.us.oracle.com:7654/em/upload/... Done. OMS is secure on HTTPS Port 4473 bash-3.00$ |
|
emctl status agent scheduler |
Lists all Running, Ready, and Scheduled Collection threads. |
|
emctl status agent jobs |
Lists the status of the jobs that are running at present on the agent. The following is an example output: bash-3.00$ emctl status agent jobs Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0. Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved. ------------------------------------------------- step id typ pid stat command line ------- --- --- ---- ------------ ------------------------------------------------- Agent is Running and Ready |
|
emctl status agent target <target name>,<target type>,<metric> |
Lists the detailed status of the specified targets in the order of target name, target type. The following is an example of an oracle_database target. You can also provide a particular metric name in the emctl command to get the status of a particular metric of a target. bash-3.00$ emctl status agent target database,oracle_database Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0. Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved. ------------------------------------------------- Target Name : database Target Type : oracle_database Current severity state ---------------------- Metric Column name Key State Timestamp ------------------------------------------------- DeferredTrans errortrans_count n/a CLEAR 2009-07-09 02:38:07 DeferredTrans deftrans_count n/a CLEAR 2009-07-09 02:38:07 ha_recovery missing_media_files n/a CLEAR 2009-07-09 02:28:57 ha_recovery corrupt_data_blocks n/a CLEAR 2009-07-09 02:28:57 ha_recovery datafiles_need_recovery n/a CLEAR 2009-07-09 02:28:57 Response Status n/a CLEAR 2009-07-09 02:38:04 Response userLogon n/a CLEAR 2009-07-09 02:38:04 Response State n/a CLEAR 2009-07-09 02:38:04 OCMInstrumentation NeedToInstrument n/a CLEAR 2009-07-09 02:31:55 health_check Status n/a CLEAR 2009-07-09 02:40:00 health_check Unmounted n/a CLEAR 2009-07-09 02:40:00 health_check Mounted n/a CLEAR 2009-07-09 02:40:00 health_check Unavailable n/a CLEAR 2009-07-09 02:40:00 health_check Maintenance n/a CLEAR 2009-07-09 02:40:00 sql_response time n/a CLEAR 2009-07-09 02:38:50 sga_pool_wastage java_free_pct n/a CLEAR 2009-07-09 02:28: 58 UserAudit username DBSNMP_staxe05 CLEAR 2009-07-09 02:32:48 ------------------------------------------------------- Agent is Running and Ready |
|
emctl status agent mcache <target name>,<target type>,<metric> |
Lists the names of the metrics for which the values are present in the metric cache. See the following example for a simple host target: bash-3.00$ emctl status agent mcache staxe05.us.oracle.com,host Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0. Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved. ------------------------------------------------------- Metric cache contains value for following metrics at 2009-07-09 02:54:47 CPUUsage DiskActivity FileMonitoring LPAR Performance on AIX Load Network PagingActivity ------------------------------------------------------- Agent is Running and Ready The metrics listed above are the ones whose values are present in the metric cache. |
|
emctl status agent cpu |
Dumps the agent Thread CPU usage into a .trc file. This file contains the list of all the threads that are running at present and their CPU usage.Following is the sample output of emctl status agent cpu: bash-3.00$ emctl status agent cpu Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0. Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved. ------------------------------------------------------- Agent Thread CPU Snapshot available in file: /ade/aime_cpap4_ag/oracle/sysman/emd/cputrack/emagent_1654792_2009-07-09_02-58-54_cpudiag.trc ------------------------------------------------------- Agent is Running and Ready |
|
emctl status agent mutex |
Gives the detailed status of the agent mutex contention for each thread. It gives the acquired, release, and wait time of mutexes for each thread.Following is a sample output: bash-3.00$ emctl status agent mutex
Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.
Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.
-------------------------------------------------------
Mutex status at 2009-07-09 03:03:46 (prev : 2009-07-09 03:03:13)
Addr Name : TotAcq TotRel TotWT LSAcq LSRel LSWT MxWt OwnerTid
2346a578 CollState : 14 14 18 0 0 0 1 NULL-thread
232e7628 CollState : 0 0 0 0 0 0 0 NULL-thread
23386638 CollState : 0 0 0 0 0 0 0 NULL-thread
2329fd28 CollState : 0 0 0 0 0 0 0 NULL-thread
239521c8 CollItem : 0 0 0 0 0 0 0 NULL-thread
2328cd98 CollState : 0 0 0 0 0 0 0 NULL-thread
23a54948 CollItem : 0 0 0 0 0 0 0 NULL-thread
232d8b68 CollItem : 1 1 1 0 0 0 1 NULL-thread
2358ce38 MetricCacheItem : 2 2 2 0 0 0 1 NULL-thread
|
|
emctl status agent memory |
Used for debugging agent memory. You will need to set “enableMemoryTracing=TRUE” in emd.properties for memory profiling agent. |
|
emctl status agent memclean |
Clears the memory hash table. Note that by default, the memory tracing will not be enabled by the agent. So, if the memory tracing is not enabled, then emctl status agent memclean will not clear the hashtable. To enable memory tracing, you need to set enableMemoryTracing=true in emd.properties of the agent and then reload the agent.The following is a sample output: bash-3.00$ emctl status agent memclean Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0. Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved. ------------------------------------------------------- Memory hashtable cleared. ------------------------------------------------------ Agent is Running and Ready |
|
emctl reload [agent] |
Reloads the agent by reading the emd.properties and targets.xml files again. If you have changed any property in emd.properties file, for example, if you have changed the tracing level of collector in the emd.properties by changing tracelevel.collector=DEBUG (default will be WARN) then you need to reload the agent to make the agent takes this change into account. Note that the agent should be up and running for the reload to happen successfully. |
|
emctl reload agent dynamicproperties [<Target_name>:<Target_Type>]... |
Recomputes the dynamic properties of a target and generates the dynamic properties for the target.Sample output for oracle_database is as follows: bash-3.00$ emctl reload agent dynamicproperties database:oracle_database Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0. Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved. ------------------------------------------------------- EMD recompute dynprops completed successfully |
|
emctl upload |
Uploads xml files that are pending to upload to the OMS under the upload directory. |
|
emctl pingOMS [agent] |
Pings the OMS to check if the agent is able to connect to the OMS. Agent will wait for the reverse ping from the OMS so that agent can say the pingOMS is successful. |
|
emctl config agent <options> |
Configures agent based on the options provided. |
|
emctl config agent updateTZ |
Updates the current timezone of the agent in emd.properties file. |
|
emctl config agent getTZ |
Prints the current timezone of the agent. |
|
emctl config agent credentials [<Target_name>[:<Target_Type>]] |
Provides the option to change the credentials for a particular target. Through this, you can change the user name and password of the target. It will ask you when you run this command whether you want to change the user name or password. If you select yes, then you have to provide the new user name and password for the target which you want to configure. Then it will reload the agent.Sample output for oracle_database is as follows: bash-3.00$ emctl config agent credentials database Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0. Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved. Name = database, Type = oracle_database Want to change for "UserName" (y/n): Want to change for "password" (y/n): EMD reload completed successfully |
|
emctl config agent getSupportedTZ |
Prints the supported timezones for the agent. |
|
emctl config console <fileloc> [<EM loc>] |
Allows you to configure the console based on the configuration entries that you have mentioned in the file <fileloc>. <EM loc> is optional and can be used to operate on a different Oracle Home. |
|
emctl config [agent] addtarget [-f|-force] <fileloc> [<EM loc>] |
Allows you to configure agent. <fileloc> contains a definition of target to add and where -f or -force allows to overwrite an existing target.If -f or -force is not specified, existing targets cannot be overwritten. <EM loc> is optional and can be used to operate on a different Oracle Home. |
|
emctl config [agent] addtargets [-f|-force] <fileloc> [<EM loc>] |
Allows you to configure agent. <fileloc> contains a definition of targets to add and -f or -force allows to overwrite existing targets.If -f or -force is not specified, existing targets cannot be overwritten. <EM loc> is optional and can be used to operate on a different Oracle Home. |
|
emctl config [agent] modifytarget <fileloc> [<EM loc>] [<EM State>] [-mergeProps] |
Allows you to configure agent. <fileloc> contains a definition of target to modify and -mergeProps is used when only target properties are to be updated. <EM loc> is optional and can be used to operate on a different Oracle Home. |
|
emctl config [agent] deletetarget <type> <name> [<EM loc>] |
Allows you to delete target. <type>,<name> specify target type and name to delete. <EM loc> is optional and can be used to operate on a different Oracle Home. |
|
emctl config [agent] listtargets [<EM loc>] |
Lists all targets present in targets.xml. <EM loc> is optional and can be used to operate on a different Oracle Home. |
|
emctl config agent listtargetsfully [<EM loc1>] [<EM loc2>] ... |
Lists all targets present in targets.xml of the given Enterprise Manager location. <EM loc> is optional and can be used to operate on a different Oracle Home. |
|
emctl config [agent] listcentralagents [<EM loc>] |
Lists the central agents this home is associated with. The centralagent command does not apply in an agent-only home. <EM loc> is optional and can be used to operate on a different Oracle Home. |
|
emctl config [agent] addcentralagent <centralAgentHomePath> [<EM loc>] |
Associates this home with a new central agent. The centralagent command does not apply in an agent-only home. <EM loc> is optional and can be used to operate on a different Oracle Home. |
|
emctl config [agent] removecentralagent <centralAgentHomePath> [<EM loc>] |
Removes the association of this home with a central agent. The centralagent command does not apply in an agent-only home. <EM loc> is optional and can be used to operate on a different Oracle Home. |
|
emctl config [agent] upgradecentralagent <centralAgentHomePathOld> [<centralAgentHomePathNew>] |
Upgrades all product homes being monitored by this central agent. The centralagent command does not apply in an agent-only home. |
|
emctl config [agent] setcentralagents <centralAgent1> [<centralAgent2> ...] |
Sets the list of central agents this home is associated with. The centralagent command does not apply in an agent-only home. |
|
emctl config agent addTargetsToRepository <uploadFile> <update_on_dup (true | false)> |
Adds targets to repository. uploadFile contains definition for targetsupdate_on_dup decides whether updating duplicate targetsThis function is for central agent. |
|
emctl config agent addAssociationsToRepository <uploadFile> |
Adds associations to repository. uploadFile contains definition(s) for association(s)This function is for central agent. |
|
emctl config agent getLocalHost |
Prints the local host where the agent is running. |
|
emctl control agent runCollection <target_name>:<target_type> <metric_name> |
Allows to manually run the collections for a particular metric of a target. Sample output is as follows: bash-3.00$ emctl control agent runCollection staxe05.us.oracle.com:host CPUUsage Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0. Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved. ------------------------------------------------------- EMD runCollection completed successfully |
|
emctl getcurdir agent |
Prints the current working directory you are in (pwd). |
|
emctl resetTZ agent |
Resets the timezone of the agent. Stop the agent first and then run this command to change the current timezone to a different timezone. Then start the agent. |
|
emctl resettzhost <hostname> <override_timezone> |
Resets the timezone settings of the host where the agent is running. |
|
emctl getversion |
Prints the version of the agent. Sample output is as follows: bash-3.00$ emctll getversion
bash: emctll: command not found
bash-3.00$ emctl getversion
Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.
Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.
--- Standalone agent
Enterprise Manager 10g Agent Version 10.2.0.5.0
|
|
emctl dumpstate agent <component> . . . |
Generates the dumps for the agent. This command allow you to analyze the memory/cpu issues of the agent. Sample output is as follows: bash-3.00$ emctl dumpstate agent Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0. Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved. dump file generated: /ade/aime_cpap4_ag/oracle/sysman/dump/emagent_1654792_20090709042448.diagtrc bash-3.00$ |
|
emctl gensudoprops |
Generates the sudo properties of the agent. |
|
emctl clearsudoprops |
Clears the sudo properties. |
|
emctl clearstate |
Clears the state directory contents. The files that are located under $ORACLE_HOME/sysman/emd/state will be deleted if this command is run. The state files are the files which are ready for the agent to convert them into corresponding xml files. |
|
emctl getemhome |
Prints the agent home directory. The sample output is as follows: bash-3.00$ emctl getemhome Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0. Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved. EMHOME=/ade/aime_cpap4_ag/oracle |
|
emctl start blackout <Blackoutname> [-nodeLevel] [<Target_name>[:<Target_Type>]].... [-d <Duration>] |
Starts blackout on a target. <Target_name:Target_type> defaults to local node target if not specified.If -nodeLevel is specified after <Blackoutname>,the blackout will be applied to all targets and any target list that follows will be ignored.Duration is specified in [days] hh:mm |
|
emctl stop blackout <Blackoutname> |
Stops the blackout that was started on a particular target. Only those blackouts that are started by the emctl tool can be stopped using emctl. This command cannot stop the blackouts that are started using the Console or emcli. |
|
emctl status blackout [<Target_name>[:<Target_Type>]].... |
Provides the status of the blackout of the target. The status includes the type of blackout, whether one time, repeating, or a scheduled blackout. This command also specifies whether the blackout has started or stopped. |
|
emctl secure agent <registration password> [-passwd_file <abs file loc>] |
Secures the agent against an OMS. The registration password must be provided. |
|
emctl unsecure agent |
Unsecures the agent. This will make the agent unsecure and the agent's port will be changed to http port. |
|
emctl verifykey |
Verifies the communication between the OMS and agent by sending pingOMS. |
|
emctl deploy agent [-s <install-password>] [-o <omshostname:consoleSrvPort>] [-S] <deploy-dir> <deploy-hostname>:<port> <source-hostname> |
'agent' creates and deploys only the agent. [-s <password>]: Install password for securing agent. [-S ]: Password will be provided in STDIN. [-o <omshostname:consoleSrvPort>]: The OMS Hostname and console servlet port. Choose the unsecured port. <deploy-dir> : Directory to create the shared (state-only) installation port. <deploy-hostname:port> : Host name and port of the shared (state-only) installation. Choose unused port. <source-hostname>: The host name of the source install. Typically the machine where EM is installed. This is searched and replaced in targets.xml by the host name provided in argument <deploy-hostname:port>. <sid>: The instance of the remote database. Only specified when deploying "dbconsole". |
|
emctl deploy dbconsole [-s <install-password>] <deploy-dir> <deploy-hostname>:<port> <source-hostname> <sid> |
'dbconsole' creates and deploys both the agent and the dbconsole. [-s <password>]: Install password for securing agent. <deploy-dir> : Directory to create the shared (state-only) installation port. <deploy-hostname:port> : Host name and port of the shared(state-only) installation. Choose unused port. <source-hostname>: The host name of the source install. Typically the machine where EM is installed. This is searched and replaced in targets.xml by the host name provided in argument <deploy-hostname:port>. <sid>: The instance of the remote database. Only specified when deploying "dbconsole". |
|
emctl ilint |
Allows ilint support of agent. |
The emctl.log file is a file that captures the results of all emctl commands you run. The log file resides in the $ORACLE_HOME/sysman/log directory of the Management Agent, and is updated every time you run an emctl command. If your emctl command fails for some reason, access this log file to diagnose the issue.
For example, run the following command from the Oracle home directory of the Management Agent to check its status:
<Oracle_Home>emctl status agent
After running the command, navigate to the log directory to view the following information in the emctl.log file:
1114306 :: Wed Jun 10 02:29:36 2009::AgentLifeCycle.pm: Processing status agent 1114306 :: Wed Jun 10 02:29:36 2009::AgentStatus.pm:Processing status agent 1114306 :: Wed Jun 10 02:29:37 2009::AgentStatus.pm:emdctl status returned 3
Here, the first column, that is, 1114306, is the thread that was used to check the status. The second column shows the date and time when the command was run. The third column mentions the Perl script that was run for the command. The last column describes the result of the command, where it shows the progress made by the command and the exit code returned for the command. In this case, the exit code is 3, which means that the Management Agent is up and running.
Another example, run the following command from the Oracle home directory of the Management Agent to upload data:
<Oracle_Home>emctl upload agent
After running the command, navigate to the log directory to view the following information in the emctl.log file:
1286220 :: Tue Jun 9 07:13:09 2009::AgentStatus.pm:Processing upload 1286220 :: Tue Jun 9 07:13:10 2009::AgentStatus.pm:emdctl status agent returned 3 1286220 :: Tue Jun 9 07:13:41 2009::AgentStatus.pm: emdctl upload returned with exit code 6
Here, the entries are similar to the entries in the first example, but the exit code returned is 6, which means the upload operation is failing for some reason.
Table 8-9 describes the different exit codes of an emctl command:
Table 8-9 Description of Exit Codes
| Exit Code | Description |
|---|---|
|
0 |
Operation was successful. No action required from you. |
|
1 |
Failed to connect to the Management Agent. Maybe the Management Agent is not running. Restart the Management Agent, and then try the emctl command again. |
|
2 |
Timed out while connecting to the Management Agent. Maybe the Management Agent is hanging. Restart the Management Agent, and then try the emctl command again. |
|
3 |
Management Agent is up and running. No action required from you. |
|
4 |
Management Agent is up but not ready. Wait for some more time, and then try the emctl command again. |
|
5 |
Input/output error while sending Management Agent-related request or receiving Management Agent-related response. |
|
6 |
Unable to upload. Check the status of the Management Agent, and then try the emctl command again. |
|
7 |
Management Agent is in an abnormal state. Check the status of the Management Agent, and then try the emctl command again. |
|
8 |
Operation was incomplete. The command might have timed out. Try again. |
|
9 |
Usage error. Check the command you are running and try again with the correct command. |
|
10 |
SSL handshake error while communicating with the Management Agent. Secure the Management Agent, and then try the emctl command again. |
|
11 |
Key mismatch while communicating with the Management Agent. Secure the Management Agent, and then try the emctl command again. |
|
255 |
Unable to open the temporary file. Try the emctl command again. |
|
 Copyright © 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|