Grid Control - Revision history

Stuart: /* Get rid of an agent that won’t go away in the Grid screens */

2018-09-04T13:30:38Z

‎Get rid of an agent that won’t go away in the Grid screens

2018-09-04T09:37:25Z

‎Change dbsnmp password

2018-09-04T09:30:45Z

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

2018-09-04T09:28:46Z

‎A useful set of emcli commands

2018-09-04T09:15:49Z

‎Get rid of an agent that won’t go away in the Grid screens

2018-09-04T09:15:20Z

‎Get rid of an agent that won’t go away in the Grid screens:

2018-09-04T09:13:58Z

2017-01-05T16:20:29Z

‎Start a host level blackout from command line

2017-01-05T16:19:34Z

‎Agent Unreachable

2014-11-17T20:43:47Z

@@ Line 80: / Line 80: @@
 </pre>
 ===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!<br />

@@ Line 185: / Line 185: @@
 ===Change dbsnmp password===
 Changing this password is easy as long as it is done correctly. It is a three step process.<br />
-Step 1. Change the password in the traditional manner.
+====Change the password in the traditional manner====
 <pre>
 SQL> alter user dbsnmp identified by &new_password account unlock;
 </pre>
-Step 2. Change the password in the targets.xml file.
+====Change the password in the targets.xml file====
 <pre>
 vi ${AGENT_HOME}/sysman/emd/targets.xml
@@ Line 197: / Line 197: @@
 <Property NAME=”password” VALUE=”<new password>” ENCRYPTED=”FALSE”/>
 </pre>
-Step 3. Restart the agent. Picks up the new password (and encrypts it)
+====Restart the agent. Picks up the new password (and encrypts it)====
 <pre>
 emctl restart agent

@@ Line 42: / Line 42: @@
 </pre>
 ====Follow a plugin deployment (on the OMS / on an agent)====
 <pre>
--- Oracle Database plugin
+emcli get_plugin_deployment_status -plugin_id=oracle.sysman.db
 </pre>
 ====Import an update (for example: a plugin update) into the software library====
 <pre>

@@ Line 16: / Line 16: @@
 ===A useful set of emcli commands===
 * [https://laurent-leturgez.com/2012/06/11/useful-emcli-commands-in-em-cloud-control-12c/ laurent-leturgez.com]
 ===Get rid of an agent that won’t go away in the Grid screens===

@@ Line 26: / Line 26: @@
 <pre>
 sqlplus / as sysdba
-exec mgmt_admin.cleanup_agent('<host>:<port>')
+exec mgmt_admin.cleanup_agent('<host>:<port>');
 exit
 </pre>

@@ Line 17: / Line 17: @@
 * [https://laurent-leturgez.com/2012/06/11/useful-emcli-commands-in-em-cloud-control-12c/ laurent-leturgez.com]
-===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===
-This has the effect of removing everything related to the host in question!<.br />
+This has the effect of removing everything related to the host in question!<br />
 <pre>
 emctl stop agent
 </pre>

@@ Line 13: / Line 13: @@
 * 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
+This has the effect of removing everything related to the host in question!<.br />
- exec mgmt_admin.cleanup_agent('<myserver>:<port>')
+<pre>
- emctl start agent
+On host where agent is running...
 ===Get rid of targets that won’t go away in the Grid screens:===
- exec mgmt_admin.delete_target('target_name','target_type’)
+<pre>
 See mgmt_targets table in sysman schema for list of known targets.

@@ Line 50: / Line 50: @@
 ''Check the agent log in $ORACLE_HOME/sysman/log''
-===Start a host level blackout from command line===
+===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...
 <pre>
 emctl start blackout server_maint -nodeLevel
 </pre>
 ===Start a host level blackout for a certain duration===
 This starts a blackout from now until now + 8 hours

← Older revision		Revision as of 16:19, 5 January 2017
Line 50:		Line 50:

	''Check the agent log in $ORACLE_HOME/sysman/log''		''Check the agent log in $ORACLE_HOME/sysman/log''
		+	===Start a host level blackout from command line===
		+	This could be included in a shell script before patching, for example...
		+	<pre>
		+	emctl start blackout server_maint -nodeLevel
		+	</pre>
		+	===Start a host level blackout for a certain duration===
		+	This starts a blackout from now until now + 8 hours
		+	<pre>
		+	emctl start blackout server_maint -nodeLevel -d 08:00
		+	</pre>
		+	===Stop a blackout from command line===
		+	When patching is done?...
		+	<pre>
		+	emctl stop blackout server_maint
		+	</pre>

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

← Older revision		Revision as of 20:43, 17 November 2014
Line 1:		Line 1:
		+	* [http://www.oracle.com/technetwork/oem/grid-control/twp-security-best-practices-133704.pdf Grid security best practices]
	==Definitions==		==Definitions==
	The 10g Enterprise Manager Grid Control includes the following Components:<br />		The 10g Enterprise Manager Grid Control includes the following Components:<br />