1. Cloud Control Advanced Installation and Configuration Guide
  2. Overview of the Installation and Configuration Log Files

A Overview of the Installation and Configuration Log Files

This appendix lists the locations of the various log files that are created during the prerequisites check, installation, and configuration phases of Enterprise Manager Cloud Control components.

In particular, this appendix covers the following:

Enterprise Manager Cloud Control Installation Logs

This section describes the following log files that are created while installing Enterprise Manager Cloud Control:

Installation Logs

The following are the installation logs, which provide complete information on the installation status:

  • <ORACLE_INVENTORY_HOME>/logs/install<timestamp>.log

  • <ORACLE_HOME>/cfgtoollogs/oui/install<timestamp>.log

    Note:

    The install log file is located in the <ORACLE_INVENTORY_HOME> directory by default. This log file will be copied on to the above-mentioned Oracle home location after the installation is complete.

Configuration Logs

This section describes the following configuration logs:

General Configuration Logs

The Oracle Management Service (OMS) configuration logs are located in the following location of the Oracle home of the OMS.

<ORACLE_HOME>/cfgtoollogs/omsca

Table A-1 lists the configuration logs for different installation types.

Table A-1 General Configuration Logs

Installation Type Location

Install a new or Upgrade Enterprise Manager system

  • <ORACLE_HOME>/cfgtoollogs/cfgfw/CfmLogger<timestamp>.log

  • <ORACLE_HOME>/cfgtoollogs/cfgfw/oracle.sysman.top.oms.<timestamp>.log

Note: <ORACLE_HOME> refers to the Oracle home of the OMS.

Add an additional Management Service

  • <ORACLE_HOME>/cfgtoollogs/omsca/logs/omsca<timestamp.log>

  • <ORACLE_HOME>/cfgtoollogs/cfgfw/oracle.sysman.top.oms.<timestamp>.log

Note: <ORACLE_HOME> refers to the Oracle home of the OMS.

Install Oracle Management Agent

  • <ORACLE_HOME>/cfgtoollogs/cfgfw/CfmLogger

  • <ORACLE_HOME>/cfgtoollogs/cfgfw/oracle.sysman.top.agent.<timestamp>.log

Note: <ORACLE_HOME> refers to the Oracle home of the Management Agent.

Repository Configuration Logs

This section describes the following repository configuration logs:

SYSMAN Schema Operation Logs

The SYSMAN schema operation logs are available in the following location of the Oracle home of the OMS. Listed in this directory is an overall log file, emschema.log, which logs all the actions performed by all the instances of RepManager run.

$<ORACLE_HOME>/sysman/log/schemanager/

In this location, for each run of RepManager, a new subdirectory is created based on the time at which the RepManager was run.

For example, if the RepManager was run and an instance was created at 09/29/2019 12:50PM, then the following subdirectory is created.

$<ORACLE_HOME>/sysman/log/schemananager/m_092919_1250_PM/

An instance of RepManager (or equivalently RepManager) can have schema actions, mainly CREATE, DROP, UPGRADE, TRANSX, and RESUME_RETRY. For each action, a subdirectory is created.

For example, if a CREATE action is performed by a RepManager instance at 09/29/2019 12:51PM, then the following subdirectory is created. Listed under this subdirectory are RCU-related log files and emschema.log.CREATE log file that logs the CREATE action-specific messages.

$<ORACLE_HOME>/sysman/log/schemananager/m_092919_1250_PM/m_092919_1251PM.CREATE/

In general, in $<ORACLE_HOME>/sysman/log/schemananager/m_<time-stamp>/m_<time-stamp>.<schema-action>, the following files are created:

  • RCU per component (i.e. init, common, modify, drop, config, outofbox, preupgrade log

  • RCU log

  • Schema action-specific RCU logs

  • TransX action-specific log (emrep_config.log)

If the any of the schema operations (CREATE/UPGRADE/PREUPGRADE/DROP) fail in SQL execution, and if you retry the operation by clicking Retry, then a separate subdirectory titled m_<time-stamp>.RESUME_RETRY is created.

The following shows the overall directory structure of repository operation logs for different schema actions:

$<ORACLE_HOME>/sysman/log/schemamanager
               emschema.log
        m_030219_0349_AM
            m_030219_0325_AM.TRANSX
                emrep_config.log
                emschema.log.TRANSX
        m_030219_0438_AM
            m_030219_0438_AM.DROP (Same structure for Drop and Dropall actions)
                rcu.log
                emschema.log.DROP
                em_repos_drop.log
        m_030219_0450_AM
            m_030219_0450_AM.CREATE
                 custom_comp_create_tbs.log
                 em_repos_common.log
                 em_repos_init.log
                 emrep_config.log.3
                 emrep_config.log.2
                 emrep_config.log.1
                 emrep_config.log
                 emschema.log
                 rcu.log
                 emschema.log.CREATE
                 em_repos_config.log
        m_030219_1006_PM
            m_030219_1006_PM.RESUME_RETRY
                emrep_config.log.3
                emrep_config.log.2
                emrep_config.log.1
                emrep_config.log
                emschema.log
                rcu.log
                emschema.log.RESUME_RETRY
                em_repos_modify.log
        m_030219_1021_PM
            m_030219_1021_PM.UPGRADE
                em_repos_init.log
                emrep_config.log.3
                emrep_config.log.2
                emrep_config.log.1
                emrep_config.log
                emschema.log
                rcu.log
                emschema.log.UPGRADE
                em_repos_modify.log 
        m_030219_1100_PM
            m_030219_1100_PM.PREUPGRADE
                em_repos_preupgrade.log
                emschema.log.PREUPGRADE
                rcu.log
                em_repos_init.log
                emrep_config.log.3
                emrep_config.log.2
                emrep_config.log.1
                emrep_config.log
                em_repos_common.log
        m_030219_1125_PM
            m_030219_1125_PM.MY_ORACLE_SUPPORT
                emschema.log.MY_ORACLE_SUPPORTm_030219_1135_PM            m_030219_1135_PM.PLUGINPURGE                emschema.log.PLUGINPURGE
em_repos_pluginpurge.logrcu.log
EMPrereqKit Logs

For EMPrereqKit, the logs are available at the <oraInventoryLoc>/logs/ location.

The details of execution of the prerequisites per prerequisite component location is available at:

<oraInventoryLoc>/logs/emdbprereqs/LATEST/componentLog/<log_filename>

For example,

<oraInventoryLoc>/logs/emdbprereqs/LATEST/componentLog/repository.log

The details of execution of the EMPrereqkit is available at:

<oraInventoryLoc>/logs/emdbprereqs/LATEST/emprereqkit.log

The errors are located at:

<oraInventoryLoc>/logs/emdbprereqs/LATEST/emprereqkit.err

MDS Schema Operation Logs

MDS Schema Creation Log

For MDS schema creation operation, the following log is available in the Oracle home of the OMS:

$<ORACLE_HOME>/cfgtoollogs/cfgfw/emmdscreate_<timestamp>.log

For more information, review the following logs from the Oracle home of the OMS:

$<ORACLE_HOME>/sysman/log/schemamanager/m_<timestamp>/m_<timestamp>.CREATE/mds.log

$<ORACLE_HOME>/sysman/log/schemamanager/m_<timestamp>/m_<timestamp>.CREATE/rcu.log

MDS Schema Drop Logs

For MDS schema drop operation, the following logs are available in the location you specified by using the -logDir argument while invoking the MDS schema drop command:

$<user_specified_location>/mds.log

$<user_specified_location>/emmdsdrop_<timestamp>.log

However, if you did not specify any custom location while invoking the MDS schema drop command, then the logs are created in the Oracle home of the OMS. For example, /scratch/OracleHomes/oms13c/mds.log and /scratch/OracleHomes/oms13c/emmdsdrop_<timestamp>.log.

Secure Logs

For OMS, the following secure log is available in the OMS Instance Base location. Here, <oms_name>, for example, can be EMGC_OMS1.

<OMS_INSTANCE_HOME>/em/<oms_name>/sysman/log/secure.log

For Management Agents, the following secure log is available in the Oracle home of the Management Agent.

<Agent_Instance_Home/sysman/log/secure.log

Oracle Management Service Logs

The following log files that provide information about the running OMS are available in the OMS Instance Base location. Here, <oms_name>, for example, can be EMGC_OMS1.

<OMS_INSTANCE_HOME>/em/<oms_name>/sysman/log/emoms.trc

<OMS_INSTANCE_HOME>/em/<oms_name>/sysman/log/emoms.log

Add Host Log Files

This section describes the locations for the following Add Host log files:

Initialization Logs

Table A-2 lists the initialization logs of the remote host and their locations. Note that <OMS_INSTANCE_HOME> mentioned in this table refers to the OMS instance base directory (by default, it is gc_inst/em/EMGC_OMS1,which is present in the parent directory of the middleware home, by default).

Table A-2 Initialization Logs

Log File Location

<hostname>_deploy.log

<OMS_INSTANCE_HOME>/sysman/agentpush/<time-stamp>/applogs

Application Prerequisite Logs

Table A-3 lists the application prerequisite logs and their locations. Note that <OMS_INSTANCE_HOME> mentioned in this table refers to the OMS instance base directory (by default, it is gc_inst/em/EMGC_OMS1,which is present in the parent directory of the middleware home, by default), and <install_type> mentioned in this table refer to one of the installation types mentioned in Table A-4.

Table A-3 Prerequisite Logs

Log File Location

prereq<time_stamp>.log

<OMS_INSTANCE_HOME>/sysman/agentpush/<time-stamp>/prereqlogs/<install_type>_logs/<hostname>/

prereq<time_stamp>.out

<OMS_INSTANCE_HOME>/sysman/agentpush/<time-stamp>/prereqlogs/<install_type>_logs/<hostname>/

prereq<time_stamp>.err

<OMS_INSTANCE_HOME>/sysman/agentpush/<time-stamp>/prereqlogs/<install_type>_logs/<hostname>/

Table A-4 Install Types

Install Type Description Target Operating System Type

emagent_install

New Agent Installation

UNIX

emagent_clone

Agent Cloning

UNIX

nfs_install

Shared Agent Installation

UNIX

System Prerequisite Logs

Table A-5 lists the system prerequisite logs and their locations. Note that <OMS_INSTANCE_HOME> mentioned in this table refers to the OMS instance base directory (by default, it is gc_inst/em/EMGC_OMS1,which is present in the parent directory of the middleware home, by default).

Table A-5 System Prerequisite Logs

Log File Location

prereqchecker<time_stamp>.log

<OMS_INSTANCE_HOME>/sysman/agentpush/<time-stamp>/prereqlogs/productprereq_logs/<hostname>/

launcher<time_stamp>.log

<OMS_INSTANCE_HOME>/sysman/agentpush/<time-stamp>/prereqlogs/productprereq_logs/<hostname>/

oraInstall<time_stamp>.out

<OMS_INSTANCE_HOME>/sysman/agentpush/<time-stamp>/prereqlogs/productprereq_logs/<hostname>/

oraInstall<time_stamp>.err

<OMS_INSTANCE_HOME>/sysman/agentpush/<time-stamp>/prereqlogs/productprereq_logs/<hostname>/

Agent Installation Logs

Table A-6 lists the agent installation logs and their locations. Note that <OMS_INSTANCE_HOME> mentioned in this table refers to the OMS instance base directory (by default, it is gc_inst/em/EMGC_OMS1,which is present in the parent directory of the middleware home, by default).

Table A-6 Agent Installation Logs

Log File Location Description

install.log/.err

<OMS_INSTANCE_HOME>/sysman/agentpush/<time-stamp>/logs/<hostname>

Fresh and Cloned Agent install logs

nfs_install.log/.err

<OMS_INSTANCE_HOME>/sysman/agentpush/<time-stamp>/logs/<hostname>

Shared Agent installation logs

cfgfw/*.log

<OMS_INSTANCE_HOME>/sysman/agentpush/<time-stamp>/cfgtoollogs/<hostname>

Agent Configuration logs

Other Add Host Logs

Table A-7 lists all the other installation logs that are created during an agent installation using the Add Host wizard. Note that <OMS_INSTANCE_HOME> mentioned in this table refers to the OMS instance base directory (by default, it is gc_inst/em/EMGC_OMS1,which is present in the parent directory of the middleware home, by default).

Table A-7 Other Add Host Logs

Logs Location Description

EMAgentPushLogger<TIMESTAMP>.log.0

<OMS_INSTANCE_HOME>/sysman/agentpush/logs/

Agent Deploy application logs.

remoteInterfaces<TIMESTAMP>.log

<OMS_INSTANCE_HOME>/sysman/agentpush/logs/

Logs of the remote interfaces layer.

deployfwk.log

<OMS_INSTANCE_HOME>/sysman/agentpush/<time-stamp>/applogs/

Add Host Deployment Framework logs

ui.log

<OMS_INSTANCE_HOME>/sysman/agentpush/<time-stamp>/applogs/

Add Host User Interface logs.

Manual Management Agent Installation Logs

Table A-8 lists the installation logs that are created when a Management Agent is installed manually, that is, in silent mode. Note that <ORACLE_HOME> mentioned in this table refers to the target Management Agent Oracle Home, that is, <AGENT_BASE_DIR>/13.3.0.0.0/.

Table A-8 Manual Management Agent Installation Logs

Logs Location Description

agentDeploy<TIMESTAMP>.log

<ORACLE_HOME>/cfgtoollogs/agentDeploy/

Installation logs

prereq<TIMESTAMP>.log

<ORACLE_HOME>/cfgtoollogs/agentDeploy/

Installation prerequisite logs

CfmLogger<TIMESTAMP>.log

<ORACLE_HOME>/cfgtoollogs/cfgfw/

Configuration logs

AttachHome<TIMESTAMP>.log

<ORACLE_HOME>/cfgtoollogs/agentDeploy/

Attach home logs

UpdateHomeDeps<TIMESTAMP>.log

<ORACLE_HOME>/cfgtoollogs/agentDeploy/

Update home logs

cloneActions<TIMESTAMP>.log

<ORACLE_HOME>/cfgtoollogs/agentDeploy/

Clone action logs

Agent Gold Image Log Files

Table A-9 lists the log files that need to be scrutinised for a failure of Gold Image creation process.

Table A-9 Agent Gold Image Creation Failure Logs

Logs Location Description

Output log.

From the Enterprise Manger Cloud Control home page click Setup and select Manage Cloud Control and then click Agent Gold Images.

On the Agent Gold Images page click on Show all activities link to see all the jobs. Click on the job name to see the job result and the output logs.

Output logs for the agent gold image job run.

GoldAgentImageLogger<timestamp>.log

<OMS_INSTANCE_HOME>/EMGC_OMS1/sysman/goldagentimage/logs/

OMS side logs.

goldimagecreate<timestamp>.log

<AGENT_INSTANCE_HOME>/install/<TIMESTAMP>/

Agent side logs.

Table A-10 lists the log files that need to be scrutinised for Agent update failure.

Table A-10 Agent Update Failure Logs

Logs Location Description

agentDeploy<timestamp>.log

<New oracle home>/cfgtoollogs/agentDeploy/

Note: If the <New oracle home>/cfgtoollogs/agentDeploy/ location is not editable, the logs are created in <AGENT_INSTANCE_HOME>/install/logs/ folder.

Agent deploy logs.

All log files.

<AGENT_INSTANCE_HOME>/sysman/logs

Additional information logs.

All log files.

<OMS_INSTANCE_HOME>/EMGC_OMS1/sysman/logs

OMS side exception logs.

All log files.

user_projects/domains/EMGC_DOMAIN/servers/EMGC_OMS1/logs/

Server side logs.

Additional OMS Installation Logs

Table A-11 lists the installation logs that you can view when adding an OMS fails:

Note:

  • ORACLE_HOME refers to the home for the new additional OMS. However, for Admin logs, ORACLE_HOME refers to the home for the primary OMS.

  • INSTANCE_HOME refers to the OMS instance directory (that is, gc_inst,which is present in the parent directory of the middleware home, by default).

Table A-11 Additional OMS Installation Logs

Logs Location

omsca failure

$ORACLE_HOME/cfgtoollogs/omsca

Plug-in failure

$ORACLE_HOME/cfgtoollogs/pluginca

Managed server logs

  • emLogs (emoms logs)

  • msLogs (Managed server logs, if server fails to start)

  • nmLogs

$ORACLE_HOME/cfgtoollogs/omsca/log_<timestamp>/

Admin logs

$INSTANCE_HOME/user_projects/domains/GCDomain/servers/EMGC_ADMINSERVER/logs

(If out of memory error or space issue occurs, this logs on the primary OMS)

Deployment procedure output

Deployment procedure screenshots

Clone logs

$ORACLE_HOME/cfgtoollogs/clone