• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer navigation

The Geek Diary

  • OS
    • Linux
    • CentOS/RHEL
    • Solaris
    • Oracle Linux
    • VCS
  • Interview Questions
  • Database
    • oracle
    • oracle 12c
    • ASM
    • mysql
    • MariaDB
  • DevOps
    • Docker
    • Shell Scripting
  • Big Data
    • Hadoop
    • Cloudera
    • Hortonworks HDP

Log file locations for Enterprise Manager Cloud Control 13c (OMS)

by admin

OMS is a web-based application that communicates with the agents and the Oracle Management Repository to collect and store information about all the targets on the various agents. The OMS is also responsible for rendering the user interface for the console. Like the agent, the OMS can be controlled via both the EM13c console and the command-line utilities.

The Trace and Log Files of OMS

The Oracle Management Service has two applications: OMS Console (emgc) and OMS Platform (empbs). The trace and log files of these applications are located in “sysman/log” directory in the EM Instance Home (for example: /u01/oracle/gc_inst/em/EMGC_OMS1/sysman/log ). These logs are very useful to diagnose OMS related problems.

logfile Description
emoms.log The main log file for the OMS Console (emgc) application.
emoms.trc The main trace file for the OMS Console (emgc) application.
emoms_pbs.log The main log file for the OMS pbs (empbs) application.
emoms_pbs.trc The main trace file for the OMS pbs (empbs) application.
secure.log This log provides additional logs for “emctl secure oms” command.
emctl.log This log contains OMS startup/shutdown details.
emctl.msg This log is created by the OMS HealthMonitor thread, when it re-starts the OMS due to a critical error.

The Trace and Log Files of EM Managed Server

EM Managed Server is the weblogic server hosting OMS applications. The logs are located in “logs” directory in EM Manager Server Home folder (for example: /u01/oracle/gc_inst/user_projects/domains/GCDomain/servers/EMGC_OMS1/logs):

logfile Description
EMGC_OMS1.log The EMGC_OMSn instance writes all messages from its subsystems and applications to this logfile.
EMGC_OMS1.out The messages written to sysout and syserr are saved in this file by the nodemanager. This log file is rotated by the nodemanager only at the time of Managed server start, and older files need to be manually purged.
access.log This log file contains details of HTTP requests processed by EM Managed Server.
EMGC_OMS1-diagnostic.log This log file contains application-related security errors.

The Trace and Log Files of Oracle HTTP Server (OHS)

Oracle HTTP Server (OHS) is the web server component of EM13c. It works as a reverse proxy for Oracle WebLogic Server and the framework for hosting static pages. It’s located in “logs” folder in the “OHS Home” (/u01/oracle/gc_inst/user_projects/domains/GCDomain/servers/ohs1/logs):

log file Description
access_log Access logs stores all the client requests. The HTTP Response code is useful in identifying whether the client request was successful or not.
ohs1.log This is the error log for the OHS.
admin_log This log file keeps Oracle Dynamic Monitoring Service (DMS) requests.
em_upload_http_access_log The log file contains entries for Agent uploads in http mode.

The Trace and Log Files of EM Agents

The agent log files are located in the “sysman/log” folder in the “Agent Instance Home” (for example: /u01/oracle/emagent/agent_inst/sysman/log).

log file Description
gcagent.log This log file contains trace, debug, information, error, or warning messages from the Agent. It can be used for debugging Agent framework issues.
gcagent_errors.log It’s similar to the gcagent.log but it contains only the log messages of ERROR and FATAL levels. The log has no size limit.
emagent.nohup Nohup logs of the agent. This log contains startup and shutdown messages including JVM flags. It can be used to determine when the agent is down, and the errors generated on startup of shutdown can be examined with this log.
gcagent_mdu.log This log tracks the metadata updates (such as save or remove targets, blackouts, deployments of metric extensions) to the Agent.
gcagent_sdk.trc The gcagent_sdk.trc file contains log messages from each of the plugins and can be used for debugging plugin related issues.
emctl.log emctl.log provides logging for emctl commands.
emdctlj.log emdctlj.log contains logging for the entry point and the exit codes of the emctl commands.
secure.log This log provides additional logs for “emctl secure agent” command, and can be useful to diagnose failures during securing of the Agent.
emagent_perl.trc Trace file for the PERL scripts. EM uses perl scripts to gather some metrics and target discovery. The log level can be changed by modifying EMAGENT_PERL_TRACE_LEVEL variable in “sysman/config/emd.properties” file.

Filed Under: oracle

Some more articles you might also be interested in …

  1. How to rename Oracle-Managed Files (OMFs)
  2. How to connect sqlplus without tnsnames.ora
  3. Oracle Database Storage Architecture – Overview
  4. How to get datafile information when PDB is Mounted/Read-Write/Restricted Mode
  5. Oracle Database 12c New Feature – Move a Datafile Online
  6. Steps to relink Oracle Forms 12c in Linux/UNIX
  7. How to Enable or Disable Automated Statistics Collection in Oracle Database
  8. List of OCFS2 threads
  9. ORA-39170: Schema expression ‘OPS’ does not correspond to any schemas
  10. How to Set Timeout for WebLogic Web Service Client (JAX-WS and JAX-RPC)

You May Also Like

Primary Sidebar

Recent Posts

  • aws ec2: CLI for AWS EC2 (Command Examples)
  • aws cur – Create, query, and delete AWS usage report definitions (Command Examples)
  • aws configure – Manage configuration for the AWS CLI (Command Examples)
  • aws cognito-idp: Manage Amazon Cognito user pool and its users and groups using the CLI

© 2023 · The Geek Diary

  • Archives
  • Contact Us
  • Copyright