Database Reference
In-Depth Information
Table 3-1.
(
continued
)
Command
Description
emctl status agent cpu [-depth n | -full_
cpu_report]
Provides CPU statistics (either a top-n listing using
depth
or
full
details). Requires
topMetricReporter=true to be set
in emd.properties
.
emctl status agent dbconnections
Shows the contents of the DBConnection Cache.
emctl status agent jobs
Shows the status of the jobs that are currently running.
emctl status agent mcache <target
name>,<target type>,<metric>
Shows the metric names that have values in the metric cache.
emctl status agent scheduler
Shows all scheduled, ready, or running collection threads.
emctl status agent -secure
Shows whether the agent is running in secure mode, as well as
the security of the OMS it is reporting to.
emctl status agent target <target
name>,<target type>,<metric>
Shows detailed status of the specific targets in the order of
target name, target type.
emctl status blackout [<Target_
name>[:<Target_Type>]]....
Provides the status of the blackout of the target.
emctl stop agent
Stops the management agent.
emctl stop blackout <Blackoutname>
Stops the blackout that was started on a particular target. Only
blackouts that are started by the EMCTL tool can be stopped
using EMCTL.
emctl unsecure agent
Unsecures the agent. Generally, this isn't a recommended
practice.
emctl verifykey
Verifies the communication between the OMS and agent by
sending
pingOMS
.
When you run an
emctl
command, the output from that command is captured in the
emctl.log
file, located
under the
$AGENT_HOME/agent_inst/sysman/log
directory. (Some commands also display their output to
stdout
.)
More details on agent log and trace files are given in the upcoming section cleverly named “Agent Log and Trace Files.”.
The EMCLI Utility
Before you look at agent log and trace files in more detail, though, let's examine the other command-line utility for
managing agents, the Enterprise Manager Command Line Interface utility (EMCLI). The EMCLI utility is mainly used
for automating commands that need to be executed against a large number of targets, because scripting this can be
much faster than selecting each target to process the operation on via the EM console.
As an example, let's say you have a group of Production databases called
ProdDB
that are administered by
someone who is leaving the organization. If you have 500 databases in that group, you wouldn't want to update the
Contact
lifecycle properties one by one. Instead, you could do the following:
emcli set_target_property_value -property_records="ProdDB:composite:Contact:psharman"
-propagate_to_members
