Database Reference
In-Depth Information
As an example, here's a command executed to complete setup on a local workstation:
$ ./emcli setup -url=
https://em12.acme.com/em
-username=psharman -autologin
Once the command completes, you will have access to all the verbs EMCLI recognizes. There are way too many
to describe here, but executing the command
emcli help
will list them for you. It provides quite a long listing, so you
may want to redirect the output to a file for easier perusal. You can get detailed help on any particular verb by passing
that verb as an argument to the
help command
. For example,
emcli help setup
gives you more detailed help on
the setup verb. There is also a complete manual on the EMCLI utility available in the EM12c documentation set
Agent Log and Trace Files
When you install a management agent, you are prompted for an
AGENT_BASE
directory. This directory is similar to
the
ORACLE_BASE
directory used in database installations. Underneath it, you will find the agent instance directory
(
agent_inst
, which contains all the agent-related configuration files), as well as the management agent home. The
management agent home will be
<AGENT_BASE>/core/12.1.0.2.0
. Obviously, the version number in the directory
name reflects the version number for the agent, so depending on your installation, this number may differ from the
example just given. Most of the agent log and trace files you will need are found somewhere under this management
agent home directory. Some of the directories you may need to look at to find information are shown in Table
3-2
.
In this table,
<AGENT_HOME>
refers to the management agent home (for example,
<AGENT_BASE>/core/12.1.0.2.0
),
while
<AGENT_INST>
refers to the agent instance directory (for example,
<AGENT_BASE>/agent_inst
).
Table 3-2.
Locations of Agent Log and Trace Files
Type of Information
Location
<AGENT_INST>/sysman/log/gcagent.log
Agent heartbeat history
<AGENT_INST>/sysman/log/emagent.nohup
Agent startup information for both agent
and watchdog
<AGENT_INST>/sysman/log/*.trc
Agent trace files
<AGENT_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log
Configuration assistant errors
emctl
command output
<AGENT_INST>/sysman/log/emctl.log
<AGENT_INST>/sysman/log/secure.log
Errors on securing agent
<AGENT_INST>
/sysman/emd/dumps
/
SystemDump_<number>.xml
System state dumps
■
the watchdog referred to in table
3-2
is the agent watchdog. When the agent is started, it also starts an agent
watchdog process whose role is to monitor the agent and attempt to restart it should it fail.
Note
You can control the number and size of these files by using an
emctl
command. By default, the agent writes only
informational, warning, and critical messages to the trace file, but you can change the level of information written by
using the following command:
$ emctl set property agent -name "Logger.log.level" -value "<LEVEL>"
