11g Grid | Monitoring Management Services and Repository
Management Services and Repository:
Lets you monitor system performance and access diagnostic information for the Oracle Management Services and Management Repository.
Management Services and Repository:
Lets you monitor system performance and access diagnostic information for the Oracle Management Services and Management Repository.
If you are receiving tonnes of alerts from grid as below, here is a simple solution.
If you can’t see directory structure properly, use this file Read more…
Migrating from previous Oracle Enterprise Manager releases to Grid Control is a two-step process: Read more…
List Alerts and number of times they have been raised?
select substr(message_nlsid,1,50),count(*) from mgmt_current_severity where message_nlsid is not null group by message_nlsid having count(*) > 10 order by 2 desc,1 ; Read more...
The availability of the targets you manage is directly affected by the availability of the Management Agents, which gather data about your managed targets, and the host computers on which your targets are installed. As a result, it is important to understand how Enterprise Manager determines host and Management Agent availability.
As a DBA, one can’t look at entire application performance. But there is an easy way to see if database server load is normal when you hit issues . It’s done by creating and comparing baselines/snapshots under 11g Grid. This option doesn’t work with 10g so you will need 11g database.
How Grid Repository Stores Data?
The agents upload data at MGMT_METRIC_RAW table which is retained for 7 days.
Raw data are aggregated by Grid Control based on a predefined policy into 1-hour records, stored in MGMT_METRIC_1HOUR.
After 31 days or a month, 1-hour records in MGMT_METRIC_1HOUR are subject for further aggregation that rolls into 1-day records.
These 1-day records are stored in MGMT_METRIC_1Day for 365 days or 1 year before purged by Grid Control.
It often happens that DBMS statistics though do good for most queries can turn a best performing query into worse performing piece of SQL.
Here is a process I used to raise an Grid alert when a good query turns BAD.
To prevent unauthorized access to the Grid Control console, Enterprise Manager will automatically log you out of the Grid Control console when there is no activity for a predefined period of time. For example, if you leave your browser open and leave your office, this default behavior prevents unauthorized users from using your Enterprise Manager administrator account.
By default, if the system is inactive for 45 minutes or more, and then you attempt to perform an Enterprise Manager action, you will be asked to log in to the Grid Control console again.
Although, I can use grid to carry my RMAN backups I am not entirely convinced about it’s transparency. As a DBA I like to have more control to myself and I trust my custom scripts used for years more than anything else. Here is a small process I added to raise alert for failed rman backups.
I have number of systems on grid and I want to keep grid working as smoothly as I can.
Since there are many alerts/notificatins raised & inserts/deletes happening every single minute, often repository tables will need rebuild to gain EM performance.
I have SQL script to track tables in need of a rebuild. Read more…
Often you will come across a failed Agent installation or old agent to be removed before installing new one. Here is a porocess ..
Here , I wish to locate disk space acquired by a Remote target Host using df command
Please read post Using EMCLI , A command line Grid Control Interface to understand how EMCLI is used
The Enterprise Manager Command Line Interface (EM CLI) enables you to access Enterprise Manager Grid Control functionality from text-based consoles (shells and command windows) for a variety of operating systems. You can call Enterprise Manager functionality using custom scripts, such as SQL*Plus, OS shell, Perl, or Tcl, thus easily integrating Enterprise Manager functionality with a company’s business process.
Stop OMS Services
[oracle@OMS_HOST bin]$ $OMS_HOME/bin/emctl stop oms
Oracle Enterprise Manager 11g Release 1 Grid Control
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Stopping WebTier…
WebTier Successfully Stopped
Stopping Oracle Management Server…
Oracle Management Server Successfully Stopped
Oracle Management Server is Down
Generally we use grid for performance and availability monitoring . I have a NON- DBA user configured at a grid preferred credential. Sometimes I have to use grid to carry DBA tasks and here is a way to switch database preferred credentials & become a DBA
Navigate to TARGETs -> Select Databases you wish to run AWR reports at -> Server TAB
Oracle grid can display number of processes for a host. But I have a odd requirement where I need to keep track of oracle/java processes on the server.
To get AGENT working with OMS Grid , you will need ports 3872,4889/4900 accessible between machines.
If you wish to delete host from OMS Grid then delete Targets/Host at grid control first. Now use following SQL script to make sure it’s not exisitng at OMS repository . It will save you lot of frustration. Read more…
I fixed a failed 11g dbconsole installation using http://www.oracledbasupport.co.uk/standalone-11g-dbconsole-configuration But Dbconsole picked up port 5500 instead of our usual EM port 1159.
I installed Oracle 11g today on RHEL 5.4 but dbconsole failed to startup. Here is a process to fix this issue.
EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet..
Maks sure AGENT_HOME is set and EMCTL is not running from ORACLE_DATABASE_HOME than AGENT_HOME
1. Configure “Notification Methods” to receive alerts.
Login at OMS Console and click on “Setup” at top right hand corner.Click on “Notification Methods” at Left hand side.