Display agent version from Grid Control repository

Run this query in your Grid Control repository (from user SYSMAN) to get the list of Grid Control agents with OS and Version infomation:

SELECT tar.target_name,  tar.type_qualifier1 target_os, mp.property_value version

  FROM mgmt$target tar, mgmt$target_properties mp

WHERE tar.target_guid = mp.target_guid AND

      tar.target_type = 'oracle_emd' AND

      mp.property_name = 'Version' AND

      tar.type_qualifier1 IN ('SunOS', 'Linux' ) AND

      ( tar.target_name NOT LIKE '%enta%' AND tar.target_name NOT LIKE '%abnet%')

ORDER BY tar.target_name;      

Remove Grid Control agent

1. Blackout the agent

To Un-install the agent please follow the below action plan

1) Remove the host, Agent and all the monitored targets from the Grid Control repository

2) Take an OS level backup of the entire Agent Oracle Home

2) Example: <AGENT_ORACLE_HOME>/oui/bin/runInstaller -deinstall ORACLE_HOME=/u01/app/oracle/agent10g "REMOVE_HOMES={/u01/app/oracle/agent10g}" -silent

Once the agent is removed. Remove the complete folder agent10g/agent11g

Start a fresh install of the agent10g,

Drop OMS Repository - 11g

Remove the repository objects from the database with the following commands:

Stop the Grid Control web site and logon to SQLPLUS as user SYS or SYSTEM, and drop the sysman  and sysman_mds accounts and mangement objects:

SHUTDOWN IMMEDIATE;
STARTUP RESTRICT;


EXEC sysman.emd_maintenance.remove_em_dbms_jobs;
EXEC sysman.setEMUserContext('',5);
REVOKE dba FROM sysman;


DECLARE
   CURSOR c1 IS
     SELECT owner, synonym_name name
       FROM dba_synonyms
     WHERE table_owner IN ('SYSMAN', 'SYSMAN_MDS');
BEGIN
   FOR r1 IN c1 LOOP
     IF r1.owner = 'PUBLIC' THEN
        EXECUTE IMMEDIATE 'DROP PUBLIC SYNONYM '||r1.name;
     ELSE 
        EXECUTE IMMEDIATE 'DROP SYNONYM '||r1.owner||'.'||r1.name;
     END IF;
   END LOOP;
END;
/


DROP USER mgmt_view CASCADE;
DROP ROLE mgmt_user;
DROP USER sysman CASCADE;
DROP USER sysman_mds CASCADE;
delete from SCHEMA_VERSION_REGISTRY where COMP_NAME='Metadata Services';
ALTER SYSTEM DISABLE RESTRICTED SESSION;

List Grid Agent targets

myserver:ora$ emctl config agent listtargets
 
Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0. 
Copyright (c) 1996, 2009 Oracle Corporation.  All rights reserved.
[abb-srvr-13-dpieng.myserv.com:3872, oracle_emd]
[RAC_barvaw_crs, cluster][abb-srvr-13-dpieng.myserv.com, host]
[SAPMGPG_SAPMGPG1, oracle_database]
[LISTENER_BARVAWDB1_abb-srvr-13-dpieng.myserv.com, oracle_listener]
[SAPMGPGDG, rac_database]

Problem: Agent Start: Start agent fails with "The Oracleagent10gAgent service could not be started."

Applies to: 
Enterprise Manager Grid Control - Version: 10.2.0.1 to 10.2.0.3
Microsoft Windows 2000
Microsoft Windows Server 2003
Microsoft Windows (32-bit)




Symptoms
After Agent installation, the following error occurs when attempting to stop and start agent:

Stopping Agent

C:\> /bin/emctl stop agent 
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright © 1996, 2007 Oracle Corporation. All rights reserved.
The Oracleagent10gAgent service is not started.
More help is available by typing NET HELPMSG 3521.

Problem: DST: Workaround to EM Agent Restart Problem Due to a Daylight Savings Change

Applies to: 
Enterprise Manager Grid Control - Version: 10.1.0.3.0 to 10.2.0.3.0
This problem can occur on any platform.
Symptoms
Oracle Management Agent does not start.

How To Run The Discovery Of The 10.2 Agent Manually

Applies to: 
Enterprise Manager Grid Control - Version: 10.2.0.1 to 10.2.0.3
Information in this document applies to any platform.

Goal
The Agent Configuration Assistant (agentca) script is used to reconfigure the agent and rediscover the targets on the machine. This script is useful when you want to rediscover a newly added target on the machine and/or to convert a standalone agent to a RAC Agent.

This article gives the steps to rediscover targets with the option -d

How to re-link Grid Control Agent on Windows due to changing a Management Server

Let’s suppose the situation when you installed a new Grid Control Management Server on a new machine and want to re-link already existed Grid Control Agent on Windows.

Make the following steps:

1.  Go to %AGENT_HOME%\sysman\config directory and open emd.propertiesfile.
2. Find ‘REPOSITORY_URL‘ item and change the name of the server to the new one.
3. Find ‘emdWalletSrcUrl‘ item and change the name of the server to the new one.
4. After the above steps restart Grid Control Agent service.

How To Configure a 10g Database When DB Control Shows The Status Of Unavailable

The information in this article applies to:

Enterprise Manager for RDBMS - Version: 10.1.0.2
This problem can occur on any platform.

Symptoms:

When attempting to use DB Control to administer a 10g Database, the database shows down in the UI but it is actually started and accepting connections.
emoms.log file might contain:
OMSHandshake failed (AGENT URL = …..:1830/emd/main) (ERROR =INTERNAL_ERROR) - Io Exception: the network adapter could not establish the connection

If you attempt to start it from the DB Control UI, the following errors occur:
ORA 12500 "TNS:listener failed to start a dedicated server process"
ORA-12514 TNS:listener could not resolve SERVICE_NAME given in connect descriptor

How to copy User-Defined Metrics (Two-Columns) to another target

It is not possible to copy UDMs in Grid Control 10.2 between two targets in the case that UDM is Two-Columns type. In this doc I will provide information of how to perform this in 4 minutes. For example I will take two databases already defined on Grid Control: the source database is M300 and the target is SVTN.

All the above is workable ONLY in the case that them are being monitored via the same user. For example: dbsnmp

How to reload Grid Agent with a new OMS installation

Applies to:

Enterprise Manager Grid Control - Version: 10.1.0.2 to 10.1.0.3
This problem can occur on any platform.

 Symptoms

Oracle Management Agent, version 10.1.0.2.0 (or 10.1.0.3.0), is not able to upload to Oracle Management Server.

emctl upload returns the error:

"OMS VERSION NOT CHECKED YET"

emctl status agent shows a backlog of files waiting to be uploaded and no data in the OMS Version field.