Skip Headers
Oracle® Enterprise Manager Ops Center Feature Reference Guide
12c Release 1 (12.1.4.0.0)

Part Number E27511-09
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

C Logs and Directories

Each Enterprise Manager Ops Center component has some auditing capability. Follow audit advice in this document and regularly monitor audit records.

Enterprise Manager Ops Center performs each action as a job. The details of a job show the order of operations in the job and the managed assets that were targets of the job. You can view the details of a job from either the browser or the command-line interface. Each job is stored until it is deleted explicitly.

In addition to the jobs record, log files can be a source of activity records. Logs are written during operations and can provide additional detail about system activity. Log files are protected by file permissions and therefore requires a privileged user to access them.

C.1 Installation

  • Log of the most recent installation or uninstallation: /var/tmp/installer.log.latest

  • Log of previous installation or uninstallation operations: /var/tmp/installer.log.xxxx

  • Log of an agent installation: /var/scn/install/log

C.2 General Events

  • Messages: /var/adm/messages*

  • Sessions with IP address and port: /var/opt/sun/xvm/logs/audit-logs*

  • BUI: /var/opt/sun/xvm/logs/emoc.log

  • Actions of the BUI and remote clients on the Enterprise Controller:

    • On Oracle Solaris: /var/cacao/instances/oem-ec/audits/

    • On Linux: /var/opt/sun/cacao/instances/oem-ec/audits/

  • Events between controllers and agents:

    • On an Oracle Solaris Enterprise Controller: /var/cacao/instances/oem-ec/logs

    • On a Linux Enterprise Controller: /var/opt/sun/cacao/instances/oem-ec/logs

    • On each Oracle Solaris Proxy Controller: /var/cacao/instances/scn-proxy/logs/cacao.n

    • On each Linux Proxy Controller: /var/opt/sun/cacao/instances/scn-proxy/logs/cacao.n

C.3 High Availability

When Oracle Enterprise Manager Ops Center is in a High Availability configuration, each Enterprise Controller is a Clusterware node. The Clusterware resource activity is logged and the following log file is updated each time the active Enterprise Controller's resource action script's check() function is executed. The default interval is 60 seconds.

On Oracle Solaris: /var/opt/sun/xvm/ha/EnterpriseController.log

C.4 Software Updates

The Software Update component has its own server with its own logs. The following logs provide information on the activity for this server:

  • Audit Log

    • On Oracle Solaris: /var/opt/sun/xvm/uce/var.opt/server/logs/audit.log

    • On Linux: /usr/local/uce/server/logs/audit.log

  • Errors

    • On Oracle Solaris: /var/opt/sun/xvm/uce/var.opt/server/logs/error.log

    • On Linux: /usr/local/uce/server/logs/error.log

    • Log of errors in download jobs: /opt/SUNWuce/server/logs/SERVICE_CHANNEL/error.log

  • Job Log

    • On Oracle Solaris: /var/opt/sun/xvm/uce/var.opt/server/logs/job.log

    • On Linux: /usr/local/uce/server/logs/job.log

C.5 Agents

  • /var/scn/update-agent/logs directory.

  • /var/opt/sun/xvm/logs

C.6 Local Database

  • On the Enterprise Controller:

    • For installation events:

      /var/opt/sun/xvm/oracle/cfgtoollogs/dbca/OCDB/*

      /var/tmp/installer.log.latest

    • For operational events, reported by the ecadm sqlplus utility:


      /var/opt/sun/xvm/oracle/diag/rdbms/ocdb/OCDB/alert/log.xml.*
      /var/opt/sun/xvm/oracle/diag/rdbms/ocdb/OCDB/trace/alert_OCDB.log.*
      /var/opt/sun/xvm/oracle/diag/tnslsnr/hostname/oclistener/alert/log.xml.*
      /var/opt/sun/xvm/oracle/diag/tnslsnr/hostname/oclistener/trace/listener.log.*
    • For schema changes:

      /var/opt/sun/xvm/log/satadmsqlplus.log

      /var/opt/sun/xvm/logs/alter_oracle_schema.out

      /var/opt/sun/xvm/logs/alter_oracle_storage.out

    • For backup, restore, and migrate operations:

      /var/tmp/sat-backup-<`date +%F-%T`>.log

      /var/tmp/sat-restore-<`date +%F-%T`>.log

      /var/opt/sun/xvm/logs/migrate.log

  • On the Proxy Controller: /var/opt/sun/xvm/proxydb/*

  • On each agent: /var/opt/sun/xvm/agentdb/*

C.7 Upgrade

The log of upgrade actions for the Enterprise Controller and its co-located proxy controller is in the /var/scn/update-saved-state/update_satellite_bundle_12.1.n.xxxx/updatelog.txt file.

The log of upgrade actions for a Proxy Controller that is not co-located is in the /var/scn/update-saved-state/update_proxy_bundle_12.1.n.xxxx/updatelog.txt file.

After an upgrade, the state of the database is saved in the /var/scn/update-saved-state/update_satellite_bundle_12.1.n.xxxx/dblogs folder.

C.8 Event Logs for Jobs

Event logs for jobs are generated by tasks as they progress. See Viewing Jobs for instructions on viewing job event logs.

C.9 Controlling the Number of Common Agent Container Log Files

The Common Agent Container cacao is a common Java container for JDMX/JMX management and handles the interactions between controllers and agents. All events are recorded in the cacao log files and events that are above the level of INFO are also logged in the syslog. You can view the contents of the current log file using the Ops Center BUI.

  • On an Oracle Solaris Enterprise Controller: /var/cacao/instances/oem-ec/logs/cacao.n

  • On a Linux Enterprise Controller: /var/opt/sun/cacao/instances/oem-ec/logs/cacao.n

  • On each Oracle Solaris Proxy Controller: /var/cacao/instances/scn-proxy/logs/cacao.n

  • On each Linux Proxy Controller: /var/opt/sun/cacao/instances/scn-proxy/logs/cacao.n

The maximum file size is 1 MB. When the limit is reached, the current log file is closed and a new one created. The default number of log files is three. You can change the number of log files Ops Center retains, using the Common Agent Container's management utility, cacaoadm.

To view the current number of log files maintained for the Enterprise Controller, issue the following command on the system where the Enterprise software is running:

# cacaoadm get-param log-file-count -i oem-ec
log-file-count=3

To view the number of log files maintained for a Proxy Controller, issue the following command on the system were the proxy controller software is running:

# cacaoadm get-param log-file-count -i scn-proxy
log-file-count=3

To change the number of log files on the Enterprise Controller, a Proxy Controller, or both:

  1. Verify that there are no active jobs.

  2. Stop the Common Agent Container service on the Enterprise Controller.

    • On Oracle Solaris:

      # /opt/SUNWxvmoc/bin/satadm stop -w -v
      
    • On Linux:

      # /opt/sun/xvmoc/bin/satadm stop -w -v
      

      Stop the Common Agent Container service on a Proxy Controller:

    • On Oracle Solaris:

      # /opt/SUNWxvmoc/bin/proxyadm stop -w -v
      
    • On Linux:

      # /opt/sun/xvmoc/bin/proxyadm stop -w -v
      
  3. Specify the maximum number of log files to be retained in addition to the current log file. In the following example, the count of 10 specifies that nine log files of previous events are retained in addition to the log file for current events. On the Enterprise Controller:

    # cacaoadm set-param log-file-count=10 -i default
    

    On a Proxy Controller:

    # cacaoadm set-param log-file-count=10 -i scn-proxy
    
  4. Start the Enterprise Controller.

    • On Oracle Solaris:

      # /opt/SUNWxvmoc/bin/satadm start -w -v
      
    • On Linux:

      # /opt/sun/xvmoc/bin/satadm start -w -v
      
  5. Verify that the Enterprise Controller has been restarted completely before attempting other operations. For example, if you have stopped both the Enterprise Controller and a Proxy Controller, wait for the Enterprise Controller to restart before restarting each Proxy Controller. On an Oracle Solaris Proxy Controller:

    # /opt/SUNWxvmoc/bin/proxyadm start -w -v    
    

    On a Linux Proxy Controller:

    # /opt/sun/xvmoc/bin/proxyadm start -w -v    
    
  6. Verify that all controllers have restarted completely before attempting other operations.