This is an old revision of the document!

Grid_Control

Grid security best practices

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

A useful set of emcli commands

laurent-leturgez.com

Login to EM on OMS

0@@

logout of EM on OMS

1@@

Sync imcli with OMS

2@@

List promoted targets

3@@

Delete a specific target

4@@

Delete an agent and its targets

5@@

Follow a plugin deployment (on the OMS / on an agent)

Oracle Database plugin

6@@

Oracle Fusion Middleware plugin

7@@

My Oracle Support plugin

8@@

Import an update (for example: a plugin update) into the software library

9@@

Deploy a plugin on the OMS

10@@

Deploy a plugin on EM agent(s)

11@@

List available agents in the library

12@@

Download an agent from the library (used for agentDeploy.sh script method)

13@@

Set monitoring credentials for a specific target (example given for an Oracle database instance)

14@@

Uninstall the agent oracle home that registered with inventory

If you are getting “agent home is already registered with the inventory”, it means there is an entry for this home in OraInventory.xml already and it will need removing before installing to the same directory. Agent Homes are stored in /etc/oragchomelist (Linux, AIX) and /var/opt/oracle/oragchomelist (Solaris). Removing the entry from oragchomelist makes no difference. It's in the Oracle Inventory file – its location can be found in /etc/oraInst.loc (Linux, AIX) and /var/opt/oracle/oraInst.loc (Solaris).

15@@

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…

16@@

On Grid server…

17@@

On host where agent is running…

18@@

Get rid of targets that won’t go away in the Grid screens:

19@@

See mgmt_targets table in sysman schema for list of known targets.

Re-discover targets

20@@

Agent Unreachable

Is the agent running?

From SQL*Plus:

21@@

If no rows selected, the agent is not running. or

22@@

There should be a handful. If only a few, kill them and restart the agent.

23@@

Check the agent log in $ORACLE_HOME/sysman/log

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…

24@@

Start a host level blackout for a certain duration

This starts a blackout from now until now + 8 hours

25@@

Stop a blackout from command line

When patching is done?…

26@@

[[Backend WLS or EM application seems to be down]]

To list targets known to an agent:

27@@

It looks at the file $AGENT_HOME/sysman/emd/targets.xml

Manually add targets by editing this file and running:

28@@

Check state and upload directories under $AGENT_HOME/sysman/emd for .err files

Change sysman password

This works until 11.1. For a more complete guide see metalink note 270516.1 or note 259379.1 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.

29@@

Step 2. Change the password in the emoms.properties file.

30@@

Change the following 2 lines by entering the clear text password where the encrypted password is, and set True to False

31@@

Step 3. Restart the agent. Picks up the new password (and encrypts it)

32@@

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

33@@

Change the password in the targets.xml file

34@@

Change the following line by entering the clear text password where the encrypted password is, and set True to False

35@@

Restart the agent. Picks up the new password (and encrypts it)

36@@

Quick Checklist

borrowed from oraxprt.com

37@@

References

NOTE:235290.1 – Understanding the Enterprise Manager Management Agent 10g ‘emd.properties’ File NOTE:358953.1 – What ports are used in communication between the Grid Control OMS and a Management Agent? NOTE:471842.1 – Understanding Proxy Settings in Enterprise Manager Grid Control

Some useful Metalink Master Documents related to Grid Control

*Master Index for Managing Oracle Database and Listener with Grid Control 1304021.1 *Master Note for 10g Grid Control Agent Process Control (Start, Stop & Status) & Configuration 1082009.1 *How to Run the RDA against a Grid Control Installation 1057051.1 *How to Run the RDA against a Grid Control Installation Release 11g 1190193.1 *Grid Control Target Maintenance: Steps to Diagnose Issues Related to “Agent Unreachable” Status 271126.1 *Master Note for 10g Grid Control Enterprise Manager Communication and Upload issues 1086343.1 *Master Note for Target Maintenance Through 10g Enterprise Manager Grid Control 1202453.1 *Receiving agent unreachable notification emails very often after 10.2.0.4 agent upgrade 752296.1 *Healthcheck Metric failing for a 10.2.0.4 Target Database with 10.2.0.4 Agent 602633.1

dbawiki

Table of Contents