Starting Always-On Monitoring

% $AOM_HOME/scripts/emsctl start
Oracle Enterprise Manager Cloud Control 13c Release 5
Copyright (c) 2017, 2021 Oracle Corporation. All rights reserved.
------------------------------------------------------------------
Pinging Always-On Monitoring...
Always-On Monitoring is not running.
Starting Always-On Monitoring.
Waiting for process to start
Retrying...
Notifications Enabled : false
Total Downtime Contacts Configured : 1
Always-On Monitoring is up.

Getting Status & Logs

Use the emsctl status command to ascertain the operational status of Always-On Monitoring.

Example:

% $AOM_HOME/scripts/emsctl status

Oracle Enterprise Manager Cloud Control 13c Release 5
Copyright (c) 2017, 2021 Oracle Corporation. All rights reserved.
------------------------------------------------------------------
Pinging Always-On Monitoring...
Always-On Monitoring is not running.
Starting Always-On Monitoring.
Waiting for process to start
Retrying...
Notifications Enabled : false
Total Downtime Contacts Configured : 1
Always-On Monitoring is up.

Pinging Always-On Monitoring

In addition to running the emsctl status command, you can also issue the ping command if you just want to see that Always-On Monitoring service is up without listing all the operational details.

Example:

$AOM_HOME/scripts/emsctl ping
 
Oracle Enterprise Manager Cloud Control 13c Release 5
Copyright (c) 2017, 2021 Oracle Corporation. All rights reserved.
------------------------------------------------------------------
Always-On Monitoring is running

Log Files

Log files record Always-On Monitoring events that occur during operation and are generated as follows:

• emsca logs: emsca.err (only errors), emsca.log.0 (rotating log file that contains all output including errors).

• ems logs: ems.err (only errors), ems.log.0 (rotating log file that contains all output including errors).

These files are located in the $AOM_HOME/logs directory.

Log levels determine the type and operational severity of information recorded in the log files. Levels can be set to any one of the following:

• INFO: Always-On Monitoring operational events such and login, logout, or any other events tied to Always-On Monitoring lifecycle.

• DEBUG: Information considered useful when tracing the flow of Always-On Monitoring events to isolate specific problems.

• WARN (default setting): Unexpected operational Always-On Monitoring events. These are Always-On Monitoring events that should be tracked, but may not require immediate administrator intervention.

• ERROR: Always-On Monitoring operational malfunction.

To change the log level, add the logLevel=... property to $AOM_HOME/conf/emsConfig.properties. Note that this applies only to the current Always-On Monitoring instance.

Stopping the Service

Use the emsctl stop command to stop Always-On Monitoring.

$AOM_HOME/scripts/emsctl stop
Oracle Enterprise Manager Cloud Control 13c Release 5
Copyright (c) 2017, 2021 Oracle Corporation. All rights reserved.
------------------------------------------------------------------
Shutting down Always-On Monitoring.
Always-On Monitoring is stopped.