Difference between revisions of "Grid Control"
From dbawiki
(→Agent Unreachable) |
(→Definitions) |
||
| Line 1: | Line 1: | ||
==Definitions== | ==Definitions== | ||
| + | The 10g Enterprise Manager Grid Control includes the following Components:<br /> | ||
| + | <br /> | ||
| + | This document describes the troubleshooting steps to be followed when there is a communication problem between the Oracle Management Service (OMS) and the Grid Agent.<br /> | ||
| + | <br /> | ||
| + | ====Additional references:==== | ||
| + | * Note 951076.1: How to Troubleshoot Communication From a Grid Agent to the Oracle Management Service (OMS) in 10g Enterprise Manager Grid Control? | ||
| + | * Note 1089443.1: How to Troubleshoot Communication From the Grid Console (UI) Machine to the Oracle Management Service (OMS) in 10g Enterprise Manager Grid Control? | ||
| + | * Note 1089693.1: How to Troubleshoot Communication From the Oracle Management Service (OMS) to the Grid Control Repository Database in 10g Enterprise Manager Grid Control? | ||
| + | |||
* OMS - Management Service - This is responsible for communicating with the user via a GUI and communicating with the OMR | * OMS - Management Service - This is responsible for communicating with the user via a GUI and communicating with the OMR | ||
* OMR - Management Repository - This is a collection of tables owned by the sysman schema that stores all the data collected by the OMA | * OMR - Management Repository - This is a collection of tables owned by the sysman schema that stores all the data collected by the OMA | ||
| − | * OMA - Management Agent - This is a perl program that runs on the database host (one for all databases on the host) and uploads data to the OMS | + | * OMA - Management Agent - This is a perl program that runs on the database host (one for all databases on the host) and uploads data to the OMS for storage in the OMR |
===Get rid of an agent that won’t go away in the Grid screens:=== | ===Get rid of an agent that won’t go away in the Grid screens:=== | ||
Revision as of 16:50, 11 February 2014
Contents
- 1 Definitions
- 1.1 Additional references:
- 1.2 Get rid of an agent that won’t go away in the Grid screens:
- 1.3 Get rid of targets that won’t go away in the Grid screens:
- 1.4 Re-discover targets
- 1.5 Agent Unreachable
- 1.6 Backend WLS or EM application seems to be down
- 1.7 To list targets known to an agent:
- 1.8 Some useful Metalink Master Documents related to Grid Control
Definitions
The 10g Enterprise Manager Grid Control includes the following Components:
This document describes the troubleshooting steps to be followed when there is a communication problem between the Oracle Management Service (OMS) and the Grid Agent.
Additional references:
- Note 951076.1: How to Troubleshoot Communication From a Grid Agent to the Oracle Management Service (OMS) in 10g Enterprise Manager Grid Control?
- Note 1089443.1: How to Troubleshoot Communication From the Grid Console (UI) Machine to the Oracle Management Service (OMS) in 10g Enterprise Manager Grid Control?
- Note 1089693.1: How to Troubleshoot Communication From the Oracle Management Service (OMS) to the Grid Control Repository Database in 10g Enterprise Manager Grid Control?
- OMS - Management Service - This is responsible for communicating with the user via a GUI and communicating with the OMR
- OMR - Management Repository - This is a collection of tables owned by the sysman schema that stores all the data collected by the OMA
- OMA - Management Agent - This is a perl program that runs on the database host (one for all databases on the host) and uploads data to the OMS for storage in the OMR
Get rid of an agent that won’t go away in the Grid screens:
emctl stop agent
exec mgmt_admin.cleanup_agent('<myserver>:<port>')
emctl start agent
Get rid of targets that won’t go away in the Grid screens:
exec mgmt_admin.delete_target('target_name','target_type’)
See mgmt_targets table in sysman schema for list of known targets.
Re-discover targets
cd $ORACLE_HOME/bin ./agentca -d
Agent Unreachable
- Is the agent running?
From SQL*Plus:
select username,program from v$session where LOWER (program) like 'emagent%';
If no rows selected, the agent is not running. or
From Unix: . oraenv agent11g (how to see [[which databases are running on the machine]]) emctl status agent ps -ef|grep [a]gent
There should be a handful. If only a few, kill them and restart the agent.
emctl start agent
Check the agent log in $ORACLE_HOME/sysman/log
Backend WLS or EM application seems to be down
To list targets known to an agent:
emctl config agent listtargets
It looks at the file $AGENT_HOME/sysman/emd/targets.xml
Manually add targets by editing this file and running:
emctl config agent addtargets $AGENT_HOME/sysman/emd/targets.xml
Check state and upload directories under $AGENT_HOME/sysman/emd for .err files
- Master Index for Managing Oracle Database and Listener with Grid Control [ID 1304021.1]
- Master Note for 10g Grid Control Agent Process Control (Start, Stop & Status) & Configuration [ID 1082009.1]
- How to Run the RDA against a Grid Control Installation [ID 1057051.1]
- How to Run the RDA against a Grid Control Installation Release 11g [ID 1190193.1]
- Grid Control Target Maintenance: Steps to Diagnose Issues Related to "Agent Unreachable" Status [ID 271126.1]
- Master Note for 10g Grid Control Enterprise Manager Communication and Upload issues [ID 1086343.1]
- Master Note for Target Maintenance Through 10g Enterprise Manager Grid Control [ID 1202453.1]
- Receiving agent unreachable notification emails very often after 10.2.0.4 agent upgrade [ID 752296.1]
- Healthcheck Metric failing for a 10.2.0.4 Target Database with 10.2.0.4 Agent [ID 602633.1]
