OEM Grid Control

What's new in Oracle Enterprise Manager 11g for Oracle Database 11g Release 2

posted Feb 24, 2011, 6:06 AM by Sachchida Ojha   [ updated May 29, 2011, 3:15 PM ]

Did you know that the latest release of Oracle Enterprise Manager 11g features new capabilities for managing Oracle Database 11g Release 2 and Oracle Exadata V2. These new enhancements were developed and built to help administrators focus on managing their database environments more efficiently and with less manual effort.
In addition to all the rich capabilities including; performance tuning, configuration and change management, provisioning, patching, data masking, and testing--Oracle Enterprise Manager 11g also introduced new support for:

Compression Advisor: A Compression Advisor has been added in Oracle Database 11g Release 2 to facilitate choosing the correct compression level for your data. The Compression Advisor is available through Oracle Enterprise Manager 11g Grid Control console. As part of the existing Advisor framework in Oracle Database 11g, the compression advisor analyzes objects in the database, discovers the possible compression ratios that could be achieved, and recommends optimal compression settings.

Instance Caging: Oracle Enterprise Manager 11g introduces more flexible alternatives to server partitioning to support resource management. Instance caging allows you to limit CPU count per instance and enables resource management that has more consistent support across operating systems compared to resource managers available in many operating systems. It also has lower administration overhead than traditional virtualization techniques.

Global RAC Diagnostics: Oracle Enterprise Manager 11g extends Automatic Database Diagnostics Monitor (ADDM) for Oracle Database 11gR2 by greatly enhancing cluster-wide performance analysis for Real Application Clusters (RAC) databases. For RAC environments ADDM analyses the RAC cluster and reports on issues that are affecting the entire database as well as its individual instances. DBAs can now use ADDM to perform database-wide analysis of global resources, such as high-load SQL, global cache interconnect traffic, network latency issues, skew in instance response times, and I/O capacity.

Tuning Standby Databases: Active Session History (ASH) is now available for performance diagnostics for standby databases. Using Grid Control, DBAs can quickly drill-down into problem areas that are affecting performance and resolve them with minimal impact.


Extensive Oracle Exadata V2 Support: Oracle Exadata can now be managed through Grid Control as a target or as an aggregate service, and takes full advantage of Enterprise Manager's rich comprehensive management capabilities. In addition, there are some Exadata specific features that are supported in Oracle Enterprise Manger 11gR1, including:


Monitoring of Exadata storage;

Exadata aware SQL monitoring for performance diagnostics and tuning;

I/O resource management for Exadata;

For more in-depth technical details on managing Oracle Exadata V2, check out the Oracle Technology Network site.
High Availability Console: Accessed through Grid Control, the new High Availability Console allows you a configuration-wide summary view, with charts, of RAC and HA setups instead of individual targets. It provides HA configuration best practices and standards, along with recommendations from the new Maximum Availability Architecture Advisor, to help you implement a HA system. The HA Console also uses EM's powerful workflows and provisioning automation to minimize downtime for things like single instance to MAA conversions. Take a look at the following HA Console screen shot to better understand its functionality:

The HA console also show availability related events across the configuration, and includes new manage role-based standby databases allowing you to convert physical standby databases to Oracle Active Data Guard instances.
Another great feature of the HA Console is its non-intrusive, always-on, performance monitoring with drill-down capabilities, and provides smart alerting and instant notifications with adaptive thresholds to guard against unexpected outages.

Be sure to watch the latest Oracle Enterprise Manager 11g webcast to learn more about all these new database manageability features.

Installing OEM Grid Control on Solaris (SPARC) (64-bit)

posted Sep 23, 2010, 10:47 AM by Sachchida Ojha   [ updated Sep 23, 2010, 10:52 AM ]

1. Download and Install WebLogic 10.0 and Later MPs for Solaris 10 on SPARC Using Sun 64-Bit JDK
http://download.oracle.com/docs/cd/E13196_01/platform/suppconfigs/configs/solaris/solaris10_100.html#101333

2. Download and Install Oracle 11G
http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html

3.Download and Install Oracle 11G 11.1.0.1.0 Grid Control
http://www.oracle.com/technetwork/oem/grid-control/downloads/index.html

emctl pingOMS

posted Sep 23, 2010, 10:40 AM by Sachchida Ojha

Problem:
./emctl pingOMS
Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.
Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.

EMD pingOMS error: Invalid ping response "ERROR-Agent is blocked. Blocked reason is: Agent is out-of-sync with repository. This most likely means that the agent was reinstalled or recovered. Please contact an EM administrator to unblock the agent by performing an agent resync from the console. Please contact EM adminstrator to unblock the agent"

Solution: log into OEM. Click on all target. Select Agent from drop down list. Select the agent which was blocked. click on unblock to unblock the agent.

Steps to restore ORACLE_HOME

posted Sep 22, 2010, 2:27 PM by Sachchida Ojha

I took archive of ORACLE_HOME and I wanted to restore ORACLE_HOME .
Here is what I have done

tar -cvf /test/orabakup.tar $ORACLE_HOME
should the restoration is

cd /test - where the tar file is located
tar -xvf /test/orabakup.tar $ORACLE_HOME

Restore Agent

backup before
tar -cvf agent10gbeforerefresh $ORACLE_HOME/agent10g
restore after refresh
$tar -xvf agent10gbeforerefresh $ORACLE_HOME/agent10g

EMD upload error: Upload was successful but collections currently disabled - disk full

posted Sep 22, 2010, 8:58 AM by Sachchida Ojha


#Cause

The EMD disk system shows used percent at 99%.
The agent default for space required for upload files is 98%. The collections will stop when the
space on the disk is beyond that.

#Solution

To implement the solution, please execute the following steps:
1. Update the AGENT OH/sysman/config/emd.properties with the parameter:

UploadMaxDiscUsedPct=99

UploadMaxDiskUsedPctFloor=99

2. Stop the agent: ./emctl stop agent

3. Start the agent: ./emctl start agent

4. Upload to the OMS: ./emctl upload agent

Enterprise Manager Grid Control Agent Failed to start HTTP listener

posted Sep 21, 2010, 4:49 PM by Sachchida Ojha

1. Go to $AGENT_HOME/sysman/config

2. Modify the emd.properties file as follows:

Change the parameter

AgentListenOnAllNICs=TRUE to AgentListenOnAllNICs=FALSE

Note: This will cause the Agent to only listen on the specific NIC as stated in the EMD_URL parameter in the emd.properties configuration file.

2. Startup the Agent
$AGENT_HOME/bin/emctl start agent

How to check the Port

netstat -an |grep 3872

Important EM Agent Directories

posted Sep 21, 2010, 11:27 AM by Sachchida Ojha

When you install Oracle Database 10g, a set of directories and files related to Enterprise Manager is created in the Oracle Home directory:

    * emca and emctl utilities are installed in the ORACLE_HOME/bin
    * Files that are shared among all instances of the database are stored in ORACLE_HOME/sysman
    * Files that are unique to each instance of the database are stored in ORACLE_HOME/hostname_sid/
    * The log files for the Management Agent for that instance are installed in ORACLE_HOME/hostname_sid/sysman/log/
    * The files required to deploy the Database Control application are installed in the ORACLE_HOME/oc4j/j2ee directory structure.
    * The emd.properties and emoms.properties files store agent run-time parameters, and targets.xml lists the configured targets.

EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet..

posted Sep 9, 2010, 12:36 PM by Sachchida Ojha   [ updated Sep 9, 2010, 12:41 PM ]

Try following options

- emctl stop agent
- delete all files in $AGENT_HOME/sysman/emd/upload and $AGENT_HOME/sysman/emd/state
- emctl clearstate agent
- emctl secure agent (you need to enter the secure agent password)
- emctl start agent

You can also try this

-  $AGENT_HOME/emctl stop agent

# Clean agent files

1. rm -r $AGENT_HOME/sysman/emd/state/*
2. rm -r $AGENT_HOME/sysman/emd/collection/*
3. rm -r $AGENT_HOME/sysman/emd/upload/*
4. rm $AGENT_HOME/sysman/emd/lastupld.xml
5. rm $AGENT_HOME/sysman/emd/agntstmp.txt
6. rm $AGENT_HOME/sysman/emd/blackouts.xml
7. rm $AGENT_HOME/sysman/emd/protocol.ini

- $Agent_home/emctl clearstate agent

- $OMS_HOME/bin/emctl secure unlock

- $AGENT_HOME/bin/emctl start agent

1-8 of 8