grid_control
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| grid_control [2018/12/06 21:05] – created 91.177.234.129 | grid_control [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Grid_Control ====== | ||
| - | * [[http:// | ||
| - | ======Definitions====== | ||
| - | The 10g Enterprise Manager Grid Control includes the following Components:< | ||
| - | <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 /> | ||
| - | ====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? | ||
| - | <br /> | ||
| - | * 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 | ||
| - | |||
| - | =====A useful set of emcli commands===== | ||
| - | * [[https:// | ||
| - | |||
| - | ====Login to EM on OMS==== | ||
| - | < | ||
| - | ====logout of EM on OMS==== | ||
| - | < | ||
| - | ====Sync imcli with OMS==== | ||
| - | < | ||
| - | ====List promoted targets==== | ||
| - | < | ||
| - | ====Delete a specific target==== | ||
| - | < | ||
| - | ====Delete an agent and its targets==== | ||
| - | < | ||
| - | ====Follow a plugin deployment (on the OMS / on an agent)==== | ||
| - | Oracle Database plugin | ||
| - | < | ||
| - | Oracle Fusion Middleware plugin | ||
| - | < | ||
| - | My Oracle Support plugin | ||
| - | < | ||
| - | |||
| - | ====Import an update (for example: a plugin update) into the software library==== | ||
| - | < | ||
| - | ====Deploy a plugin on the OMS==== | ||
| - | < | ||
| - | ====Deploy a plugin on EM agent(s)==== | ||
| - | < | ||
| - | ====List available agents in the library==== | ||
| - | < | ||
| - | ====Download an agent from the library (used for agentDeploy.sh script method)==== | ||
| - | < | ||
| - | ====Set monitoring credentials for a specific target (example given for an Oracle database instance)==== | ||
| - | < | ||
| - | |||
| - | =====Uninstall the agent oracle home that registered with inventory===== | ||
| - | If you are getting "agent home is already registered with the inventory", | ||
| - | Agent Homes are stored in / | ||
| - | Removing the entry from oragchomelist makes no difference.< | ||
| - | It's in the Oracle Inventory file – its location can be found in / | ||
| - | < | ||
| - | =====Get rid of an agent that won’t go away in the Grid screens===== | ||
| - | This has the effect of removing everything related to the host in question!< | ||
| - | On host where agent is running... | ||
| - | < | ||
| - | On Grid server... | ||
| - | < | ||
| - | On host where agent is running... | ||
| - | < | ||
| - | |||
| - | =====Get rid of targets that won’t go away in the Grid screens: | ||
| - | < | ||
| - | |||
| - | See mgmt_targets table in sysman schema for list of known targets. | ||
| - | =====Re-discover targets===== | ||
| - | < | ||
| - | =====Agent Unreachable===== | ||
| - | * Is the agent running? | ||
| - | From SQL*Plus: | ||
| - | < | ||
| - | If no rows selected, the agent is not running. | ||
| - | or | ||
| - | < | ||
| - | There should be a handful. If only a few, kill them and restart the agent. | ||
| - | < | ||
| - | |||
| - | //Check the agent log in $ORACLE_HOME/ | ||
| - | =====Start a host level blackout from command line (blackout has to already have been created via OEM)===== | ||
| - | This could be included in a shell script before patching, for example... | ||
| - | < | ||
| - | |||
| - | =====Start a host level blackout for a certain duration===== | ||
| - | This starts a blackout from now until now + 8 hours | ||
| - | < | ||
| - | =====Stop a blackout from command line===== | ||
| - | When patching is done?... | ||
| - | < | ||
| - | |||
| - | ===== [[Backend WLS or EM application seems to be down]] ===== | ||
| - | ===== To list targets known to an agent: ===== | ||
| - | < | ||
| - | It looks at the file $AGENT_HOME/ | ||
| - | |||
| - | Manually add targets by editing this file and running: | ||
| - | < | ||
| - | Check state and upload directories under $AGENT_HOME/ | ||
| - | =====Change sysman password===== | ||
| - | This works until 11.1. For a more complete guide see metalink note [[https:// | ||
| - | <br /> | ||
| - | //For the DB Control Release 11.2 and higher, you need to set the environment variable ORACLE_UNQNAME to the value of the DB_UNIQUE_NAME database parameter.// | ||
| - | |||
| - | Changing this password is easy as long as it is done correctly. It is a three step process.< | ||
| - | Step 1. Change the password in the traditional manner. | ||
| - | < | ||
| - | Step 2. Change the password in the emoms.properties file. | ||
| - | < | ||
| - | Change the following 2 lines by entering the clear text password where the encrypted password is, and set True to False | ||
| - | < | ||
| - | Step 3. Restart the agent. Picks up the new password (and encrypts it) | ||
| - | < | ||
| - | |||
| - | =====Change dbsnmp password===== | ||
| - | Changing this password is easy as long as it is done correctly. It is a three step process.< | ||
| - | ====Change the password in the traditional manner==== | ||
| - | < | ||
| - | ====Change the password in the targets.xml file==== | ||
| - | < | ||
| - | Change the following line by entering the clear text password where the encrypted password is, and set True to False | ||
| - | < | ||
| - | ====Restart the agent. Picks up the new password (and encrypts it)==== | ||
| - | < | ||
| - | |||
| - | =====Quick Checklist===== | ||
| - | borrowed from [[http:// | ||
| - | < | ||
| - | |||
| - | |||
| - | |||
| - | References | ||
| - | |||
| - | NOTE: | ||
| - | NOTE: | ||
| - | NOTE: | ||
| - | |||
| - | =====Some useful Metalink Master Documents related to Grid Control===== | ||
| - | *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: | ||
| - | *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]] | ||
grid_control.1544130326.txt.gz · Last modified: 2018/12/06 21:05 by 91.177.234.129