Oracle Enterprise Manager 11g - OEM 11g Log file location

 

$ORACLE_HOME/sysman/config/emInstanceMapping.properties

This file will tell you the internal ID (OMS name) of the OMS, and a pointer to the file with all the port and directory details used for this OMS.

EMGC_OMS1=/app/oracle/gc_inst/em/EMGC_OMS1/emgc.properties

Once you know the location of the instance specific files of the OMS, everything else will fall into place. Take note of three key properties in the file, which will help you find the log files

EM_INSTANCE_HOME	EM_INSTANCE_HOME=/app/oracle/gc_inst/em/EMGC_OMS1
EM_DOMAIN_NAME	EM_DOMAIN_NAME=GCDomain
EM_DOMAIN_HOME	EM_DOMAIN_HOME=/app/oracle/gc_inst/user_projects/domains/GCDomain
EM_WEBTIER_INSTHOME	EM_WEBTIER_INSTHOME=/app/oracle/gc_inst/WebTierIH1
The OMS application log files	<EM_INSTANCE_HOME>/sysman/log
	/oracle/gc_inst/em/EMGC_OMS1/sysman/log
OMS Java Application log files	<EM_DOMAIN_HOME>/servers/<OMS ID>/logs
	/oracle/gc_inst/user_projects/domains/GCDomain/servers/EMGC_OMS1/logs
The Application stack log files:	<EM_DOMAIN_HOME>/servers/EMGC_ADMINSERVER/logs
	/oracle/gc_inst/user_projects/domains/GCDomain/servers/EMGC_ADMINSERVER/logs
The Apache (HTTP Server) log files	<EM_WEBTIER_INSTHOME>/diagnostics/logs/OHS/ohs1
	/app/oracle/gc_inst/WebTierIH1/diagnostics/logs/OHS/ohs1

 

Reference: https://blogs.oracle.com/oem/entry/differences_between_em10g_and

Oracle OEM Grid 11g Setting up Notification Rule for Alert Escalation via E-mail

 

Access this from OEM Grid Right Top Corner –> Preferences –> Notification Rule –> Metrics

Then on the Actions tab, check the Send Email box

OEM 11g: Setting up Repeat Notification alert

 

There is a Repeat Notification option on OEM Grid, which can be useful on monitoring.

It will ensure that alerts are not missed. Since by design OEM Grid will notify only once.

OEM Grid will not page again on the threshold until it goes under the threshold and then exceeds it again.

What it serves:

  When a metric or availability alert is neither acknowledged nor cleared it will keep notify 3 more times in frequency of  four hours.

It can be seen at the Setup –> Notification Methods.

How to generate AWR Report from OEM Grid

 

1. Choose the Database for which, AWR report to be generated

2. Choose Performance -> Snaphosts -> Automatic Workload Repository -> Run AWR Report

3. Select Beginning Snapshot, Go to time  -> Click Go -> Click Ok

4. Select Ending Snapshot   Go to time -> Click Go -> Click Ok

Now, you will be seeing on the screen "Processing View report....."

This how you will get the AUTOMATIC WORKLOAD REPOSITORY report for your Database

If you are looking to find SQL ID in past consumed much of the resource or caused performance issues, use Performance –> Top Activity –> Historical View , chose the time frame

How to register a database to use RMAN catalog using OEM Grid 11g

 

1. Login Oracle Enterprise Manager.
2. Select Target –> Chose the database
3. Go Availability tab and click "Recovery Catalog Settings" under Backup/Recovery Setup.
4. Choose "Use Recovery Catalog" option.
5. Click "Add Recovery Catalog" button to add recovery catalog.
6. And fill required fields such as host, port,sid, username, etc

 

OEM Collection Status : Disabled by Upload Manager

 

oracle@DBSRVR1:/app/oracle/product/11g/db_1/network/admin $ oemagent status Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0 Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved. --------------------------------------------------------------- Agent Version     : 11.1.0.1.0 OMS Version       : 11.1.0.1.0 Protocol Version  : 11.1.0.0.0 Agent Home        : /app/oracle/product/em/agent11g/DBSRVR1.production.siva.com Agent binaries    : /app/oracle/product/em/agent11g Agent Process ID  : 16164 Parent Process ID : 18735 Agent URL         : https://DBSRVR1.production.siva.com:3872/emd/main Repository URL    : https://GRIDCTLSRVR.siva.com:1159/em/upload Started at        : 2011-10-03 12:25:14 Started by user   : oracle Last Reload       : 2011-10-03 12:25:14 Last successful upload                       : 2011-10-05 18:32:35 Total Megabytes of XML files uploaded so far :  1400.06 Number of XML files pending upload           :      390 Size of XML files pending upload(MB)         :    51.97 Available disk space on upload filesystem    :    26.53% Collection Status                            : Disabled by Upload Manager Last attempted heartbeat to OMS              : 2011-10-05 20:44:10 Last successful heartbeat to OMS             : 2011-10-05 18:32:15 --------------------------------------------------------------- Agent is Running and Ready

Causes:

1. There are too many files backlogged
2. There is not enough free space on the directory
3. The size of the files backlogged is too large.
4. It could be of network issue between OEM Agent and OMS Server
   

Please check the emd.properties file to override the defaults that automatically disable collection

How to monitor ASM Disk group usage on OEM Grid

1. Connect to OEM
2. Connect to the Host
3. From the Host –> Go to Target Tab
   
4. From the listed target, select ASM by looking at type as  “Automatic Storage Management”
   
   
   
5. Now select type ASM, then we will be landed at ASM on OEM Grid Control.
6. On the Home Page of ASM, we can find the Disk group usage
   
   
7. Also from the Home, go to tab Disk Group
   
   
   

OEM Grid Agent command to list it’s targets

Here is the command to find the target of an OEM Agent.

./emctl config agent listtargets

Here is the example of the command

oracle@dbsrvr1:/app/oracle/product/em/agent11g/bin $ ./emctl config agent listtargets Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0 Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved. [dbsrvr1.production.dorvin.org:3872, oracle_emd] [usrncwd, cluster] [LIS_RCATP_01_dbsrvr1.production.dorvin.org, oracle_listener] [LISTENER_dbsrvr1_dbsrvr1.production.dorvin.org, oracle_listener] [pla31p.dorvin_pla31p1, oracle_database] [son49p.dorvin, rac_database] [+ASM1_dbsrvr1.production.dorvin.org, osm_instance] [dbsrvr1.production.dorvin.org, host] [rcatp.dorvin, oracle_database]

EM Alert: target is broken, Suspended on Agent Unreachable

Error: EM Alert:Suspended on Agent Unreachable

Diagnosis
/app/oracle/product/em/agent11g/sysman/log/emagent.log

2011-07-27 16:12:34,737 Thread-4083678112 target {CLUSTERNAME, cluster} is broken: cannot compute dynamic properties in time. (00155)
2011-07-27 16:12:37,342 Thread-4099427232 target {+ASM1_nodename02.domain.com, osm_instance} is broken: cannot compute dynamic properties in time. (00155)
2011-07-27 16:14:04,597 Thread-4093127584 target {RACDB.DOMAIN.COM, rac_database} is broken: cannot compute dynamic properties in time. (00155)

/app/oracle/product/em/agent11g/sysman/log/emagent.trc

2011-07-29 12:03:35,253 Thread-3985230752 ERROR upload: 1 Failure(s) in a row or XML error for C0002000.xml, retcode = -2, we give up
2011-07-29 12:03:48,271 Thread-4035967904 ERROR pingManager: Did not receive valid response to ping "ERROR-Loader/Receiver disabled on this OMS"
2011-07-29 12:03:48,359 Thread-4035967904 ERROR pingManager: Did not receive valid response to ping "ERROR-Loader/Receiver disabled on this OMS"
2011-07-29 12:05:18,641 Thread-3994700704 ERROR pingManager: Did not receive valid response to ping "ERROR-Loader/Receiver disabled on this OMS"
2011-07-29 12:06:18,875 Thread-3985230752 ERROR pingManager: Did not receive valid response to ping "ERROR-Loader/Receiver disabled on this OMS"
2011-07-29 12:08:36,023 Thread-3985230752 WARN upload: FxferSend: received http error in header from repository: https://em.domain.com:1159/em/upload
ERROR-300|Loader/Receiver disabled on this OMS
2011-07-29 12:08:36,024 Thread-3985230752 ERROR upload: Failed to upload file C0002002.xml: HTTP error.
Response received: ERROR-300|Loader/Receiver disabled on this OMS
2011-07-29 12:08:36,175 Thread-3985230752 WARN upload: FxferSend: received http error in header from repository: https://em.domain.com:1159/em/upload
ERROR-300|Loader/Receiver disabled on this OMS

Solution:

Click the configure button and go through the steps without making any changes.

Target {database instance, oracle_database} is broken: cannot compute dynamic properties in time [ID 739993.1] which advised to change the dynamicPropsComputeTimeout property in the emd.properties

OEM OMS 10g Server Commands to start, stop and know the status (opmnctl)

Check status of the GRID management server

1) export ORACLE_HOME=/app/oracle/product/10g/oms10g/opmn 2) cd $ORACLE_HOME/bin 3) ./opmnctl status

oracle@omsrvrap$  export ORACLE_HOME=/app/oracle/product/10g/oms10g/opmn
oracle@omsrvrap$  cd $ORACLE_HOME/bin
oracle@omsrvrap$  opmnctl status

Processes in Instance: EnterpriseManager0.omsrvrap.dbosmsrvr.siva.com
-------------------+--------------------+---------+---------
ias-component      | process-type       |     pid | status 
-------------------+--------------------+---------+---------
LogLoader          | logloaderd         |     N/A | Down   
HTTP_Server        | HTTP_Server        |    9146 | Alive  
dcm-daemon         | dcm-daemon         |     N/A | Down   
OC4J               | home               |    9147 | Alive  
OC4J               | OC4J_EM            |    9148 | Alive  
OC4J               | OC4J_EMPROV        |    9150 | Alive  
OC4J               | OCMRepeater        |    9151 | Alive  
WebCache           | WebCache           |    9152 | Alive  
WebCache           | WebCacheAdmin      |    9153 | Alive  
DSA                | DSA                |     N/A | Down   

Stop the GRID management server

1) export ORACLE_HOME=/app/oracle/product/10g/oms10g/opmn 2) cd $ORACLE_HOME/bin 3) ./opmnctl stopall

oracle@omsrvrap$  export ORACLE_HOME=/app/oracle/product/10g/oms10g/opmn
oracle@omsrvrap$  cd $ORACLE_HOME/bin
oracle@omsrvrap$  opmnctl status

opmnctl: stopping opmn and all managed processes...

Start the GRID management server

1) export ORACLE_HOME=/app/oracle/product/10g/oms10g/opmn 2) cd $ORACLE_HOME/bin 3) ./opmnctl startall

oracle@omsrvrap$  export ORACLE_HOME=/app/oracle/product/10g/oms10g/opmn
oracle@omsrvrap$  cd $ORACLE_HOME/bin
oracle@omsrvrap$  opmnctl status

opmnctl: starting opmn and all managed processes...

OEM Grid 10g Agent commands to start, stop and know the status. ( emctl )

Oracle10g OEM GRID Agent ( emctl )Commands

Check status of the GRID control agent

1) export ORACLE_HOME=/app/oracle/product/10g/agent10g 2) cd $ORACLE_HOME/bin 3) ./emctl status agent

oracle@dbsrvr1$ export ORACLE_HOME=/app/oracle/product/10g/agent10g
oracle@dbsrvr1$ cd $ORACLE_HOME/bin
oracle@dbsrvr1$ ./emctl status agent
Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.
Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
Agent Version : 10.2.0.5.0
OMS Version : 10.2.0.5.0
Protocol Version : 10.2.0.5.0
Agent Home : /app/oracle/product/10g/agent10g
Agent binaries : /app/oracle/product/10g/agent10g
Agent Process ID : 20124
Parent Process ID : 20080
Agent URL : https://dbsrvr1.dbsrvr.siva.com:3872/emd/main/
Repository URL : https://hp6600ap.dbsrvr.siva.com:1159/em/upload
Started at : 2010-03-09 12:04:07
Started by user : oracle
Last Reload : 2010-03-09 12:08:39
Last successful upload : 2009-07-09 14:26:42
Total Megabytes of XML files uploaded so far : 291.89
Number of XML files pending upload : 0
Size of XML files pending upload(MB) : 0.00
Available disk space on upload filesystem : 35.13%
Last successful heartbeat to OMS : 2010-03-09 12:26:07
Agent is Running and Ready

STOP the GRID control agent

1) export ORACLE_HOME=/app/oracle/product/10g/agent10g 2) cd $ORACLE_HOME/bin 3) ./emctl stop agent

oracle@dbsrvr1$ export ORACLE_HOME=/app/oracle/product/10g/agent10g
oracle@dbsrvr1$ cd $ORACLE_HOME/bin
oracle@dbsrvr1$ ./emctl stop agent
Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.
Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.
Stopping agent ... stopped.

START the GRID control agent

1) export ORACLE_HOME=/app/oracle/product/10g/agent10g 2) cd $ORACLE_HOME/bin 3) ./emctl start agent

.

oracle@dbsrvr1$ export ORACLE_HOME=/app/oracle/product/10g/agent10g
oracle@dbsrvr1$ cd $ORACLE_HOME/bin
oracle@dbsrvr1$ /emctl start agent
Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.
Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.
Starting agent ................................ started.

OEM Agent Log Files

The OEM Agent files are placed on AGENT_HOME/sysman/log/ by default.

OEM Agent Log File	Management Agent log file	emagent.log
OEM Agent Trace File	Management Agent trace file	emagent.trc
OEM Agent startup log file	Management Agent startup log file	emagent.nohup

Oracle Enterprise Manager – OEM

 

OEM Management Framework configuration consists of

1. Managed Targets
2. Management Services
3. Grid Control
4. DB Console
5. Application Server Console

OEM Services in Windows.

OEM DB Console in Unix

Start dbconsole

emctl start dbconsole

Stop dbconsole

emctl stop dbconsole

Status dbconsole

emctl status dbconsole

Accessing Enterprise Manager Database Control, using browser client

http://hostname:portnumber/em