Archive

Archive for the ‘Grid Control’ Category

Oracle Grid Control: Agent Collection State Disabled by Upload Manager / How to resync/unblock a Grid Control Agent

Problem description:

Grid Control lists targets for a server as DOWN and agent has an UNKNOWN state. If you are checking the status on the agent, you will see that your agent is running, but has a Collection Status of “Disabled by Upload Manager”:

oracle@racdb01 /u01/app/agent/agent11g/bin # ./emctl status agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.
---------------------------------------------------------------
Agent Version     : 11.1.0.1.0
OMS Version       : 11.1.0.1.0
Protocol Version  : 11.1.0.0.0
Agent Home        : /u01/app/agent/agent11g
Agent binaries    : /u01/app/agent/agent11g
Agent Process ID  : 17105112
Parent Process ID : 8192042
Agent URL         : https://racdb01:3872/emd/main/
Repository URL    : https://gridc01.initso.at:4901/em/upload
Started at        : 2011-07-05 10:12:11
Started by user   : oracle
Last Reload       : 2011-07-05 10:12:11
Last successful upload                       : (none)
Last attempted upload                        : (none)
Total Megabytes of XML files uploaded so far :     0.00
Number of XML files pending upload           :      337
Size of XML files pending upload(MB)         :    50.24
Available disk space on upload filesystem    :    24.84%
Collection Status                            : Disabled by Upload Manager
Last attempted heartbeat to OMS              : 2011-07-05 10:17:07
Last successful heartbeat to OMS             : unknown
---------------------------------------------------------------
Agent is Running and Ready
oracle@racdb01 /u01/app/agent/agent11g/bin #

 
Cause:

On the Management Agents page (accessible via Setup -> Agents Subtab) agents will be marked as blocked:

 

If you display the details of the agent, Grid Control will present you the message “The Oracle Management Server(OMS) has blocked this agent because it has either been reinstalled or restored from a filesystem backup. Please click on the Agent Resynchronization button to resync the agent.”:

 


 
Problem resolution:

Click on “Agent Resynchronization” in order to resync the agent and reestablish a normal agent status (leave “Unblock agent” checked):

 

Grid Control will start to resync the agent configuration immediately:

 

Upon end of the resync process you will be redirected to the agents detail page:

 

“emctl status agent” will now point out that the agent is again able to communicate with the Oracle Management Server and upload collected data:

oracle@racdb01 /u01/app/agent/agent11g/bin # ./emctl status agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.
---------------------------------------------------------------
Agent Version     : 11.1.0.1.0
OMS Version       : 11.1.0.1.0
Protocol Version  : 11.1.0.0.0
Agent Home        : /u01/app/agent/agent11g
Agent binaries    : /u01/app/agent/agent11g
Agent Process ID  : 17105112
Parent Process ID : 8192042
Agent URL         : https://racdb01:3872/emd/main/
Repository URL    : https://gridc01.initso.at:4901/em/upload
Started at        : 2011-07-05 10:12:11
Started by user   : oracle
Last Reload       : 2011-07-05 10:28:35
Last successful upload                       : 2011-07-05 10:29:27
Total Megabytes of XML files uploaded so far :     2.89
Number of XML files pending upload           :        0
Size of XML files pending upload(MB)         :     0.00
Available disk space on upload filesystem    :    25.00%
Last successful heartbeat to OMS             : 2011-07-05 10:28:42
---------------------------------------------------------------
Agent is Running and Ready
oracle@racdb01 /u01/app/agent/agent11g/bin #

 
After processing by the Oracle Management Server, the status information will also update in the graphical interface:

 

Categories: Enterprise Manager, Grid Control, Oracle Tags:

Oracle: HOWTO delete a service which is not configured by Oracle Clusterware

Problem description:

You are running a Real Application cluster database and Grid Control reports that one of your database services is down, but all your database services managed by Oracle Clusterware are up and running.

Cause:

Maybe a no longer used service has still an entry in dba_services (that’s one of the views which Grid Control will check). This for example can happen if you change the database domain parameter after installation.

Problem resolution:

Check all database service entries in dba_services:

SQL> SELECT service_id, name, creation_date, enabled FROM dba_services ORDER BY 1;
 
SERVICE_ID NAME                                                             CREATION_DATE   ENA
---------- ---------------------------------------------------------------- --------------- ---
         1 SYS$BACKGROUND                                                   20-MAY-11       NO
         2 SYS$USERS                                                        20-MAY-11       NO
         3 O11GXDB                                                          20-MAY-11       NO
         4 O11G                                                             20-MAY-11       NO
         5 O11G.oracle.initso.at                                            23-MAY-11       NO
         6 O11GFAIL                                                         25-MAY-11       NO
 
6 ROWS selected.
 
SQL>

In my case, O11G was the service Grid Control reported as down, as after changing the database domain to “oracle.initso.at”, the service was no longer used.

If you want to remove a service which is no longer used by Oracle Clusterware or database connections, you can remove it by using the following commands (if the service was configured using srvctl/Oracle Clusterware, please use srvctl to remove the service!):

SQL> EXEC dbms_service.delete_service('O11G');
 
PL/SQL PROCEDURE successfully completed.
 
SQL>

Grid Control will now no longer report the service as down, because it’s no longer known by the database:

SQL> SELECT service_id, name, creation_date, enabled FROM dba_services ORDER BY 1;
 
SERVICE_ID NAME                                                             CREATION_DATE   ENA
---------- ---------------------------------------------------------------- --------------- ---
         1 SYS$BACKGROUND                                                   20-MAY-11       NO
         2 SYS$USERS                                                        20-MAY-11       NO
         3 O11GXDB                                                          20-MAY-11       NO
         5 O11G.oracle.initso.at                                            23-MAY-11       NO
         6 O11GFAIL                                                         25-MAY-11       NO
 
5 ROWS selected.
 
SQL>