That’s Me

Gavin Soorma
  • Oracle Certified Professional
  • 7.3, 8i, 9i,10g, 11g
  • 11i Apps DBA OCP
  • 10g RAC OCE
  • Certified GoldenGate Implementation Specialist
  • 10g OCM
  • 11g OCM

  • Feedback

    1,650,000 hits

    Thanks A MILLION for your support!

    Please send me your valuable feedback and suggestions






    OEM Tablespace Space Used % Alerts and the AUTOEXTEND effect

    I performed a simple test to try and help clarify a rather confusing topic about when OEM will send out alerts for tablespace usage and what happens when autoextend is turned on and what about the MAXSIZE and UNLIMITED parameters of the AUTOEXTEND ON clause.

    A number of Metalink support notes discuss this topic like:

    Database Tablespace Full Metric Alerts not Generated In Grid Control [ID 357049.1]
    Troubleshooting a Database Tablespace Used(%) Alert problem [ID 403264.1]
    Oracle Recommended Patches For Tablespace Monitoring using the Tablespace Space Used % metric [ID 849498.1]

    What happens if autoextend is turned on but in some cases we have specified an upper limit for the MAXSIZE parameter or have just left it to UNLIMITED? How will OEM handle those cases?

    To clarify things, OEM alert notification mechanism will query the DBA_TABLESPACE_USAGE_METRICS view to determine the Used % in a tablespace in relation to the Warning and Critical thresholds which have been

    Continue reading OEM Tablespace Space Used % Alerts and the AUTOEXTEND effect

    Installing Oracle 10.2.0.5 Enterprise Manager Grid Control on Linux and upgrading the repository database to 10.2.0.5

    This note explains the procedure used to install 10.2.0.5 Grid Control on a Linux operating system (64 bit Red Hat Enterprise Linux Server release 5.6) as well as the steps taken to upgrade the repository database from the default 10.1.0.4 version to 10.2.0.5.

    We will be using the silent installation method and not doing the installation using the OUI in interactive mode.

    The steps can be broadly outlined as follows:

    • Install any missing RPM’s especially the 32 bit RPM’s needed for OEM
    • Create the users and groups
    • Configure kernel parameters and hosts file
    • Edit the response files needed for the silent installation
    • Install Grid Control 10.2.0.3 (OMS and Agent) using response files
    • Upgrade Grid Control to 10.2.0.5 using response files
    • Configure database repository (10.1.0.4) and OMS using response files
    • Upgrade repository database to 10g Release 2 (10.2.0.1) using DBUA
    • Apply 10.2.0.5 patch to database software and upgrade repository database to 10.2.0.5

    Download the software

    Download the Grid Control software from the following

    Continue reading Installing Oracle 10.2.0.5 Enterprise Manager Grid Control on Linux and upgrading the repository database to 10.2.0.5

    Upgrading Enterprise Manager Grid Control 10.2.0.5 to 11g

    Purpose:

    This note describes the steps taken to upgrade an existing 10.2.0.5 Enterprise Manager Grid Control environment hosted on Red Hat Linux 5.5 to Enterprise Manager 11g (11.1.

    The upgrade of the 10.2.0.5 OEM broadly involves the following steps

    • Install the Oracle 11g Release 2 database software. This will be used for the repository database.

    • Install Oracle 11g Release 1 WebLogic Server

    • Upgrade the 10.2.0.5 repository database to 11g Release 2

    • Install the 11g OEM Grid Control software and upgrade Management Server (OMS) from 10g to 11g.

    • Upgrade existing 10g management agents to 11g

    The following tasks can be performed while the 10g Grid Control environment is up and running.

    • Install the Oracle Database Software – 11g Release 2

    • Install the Oracle 11g WebLogic Server (10.3.2)

    • Install the Java Runtime Environment 1.6 Update 18

    ….
    ……..

    Download this note ….

    11g Grid Control - how to change the OMS Repository Database Listener Port or Hostname

    In versions prioor to 11g Grid Control we had to update the emoms.properties file in case we needed to modify the Listener Port used to connect to the repository database. But in 11g OEM, it has been changed and we now have to use the emctl command.

    There are a lot of other options added to the emctl command which can be seen via the emctl -help command.

    To change the listener port or the hostname of the Repository Database we now have to use the emctl config oms command as shown below.

    emctl config oms -store_repos_details -repos_port 1528 -repos_sid emrep -repos_host wintest01 -repos_user SYSMAN -repos_pwd oracle11g

    To check what are the OMS Repository details we can use the emctl config oms -list_repos_details command.

    For example –

    D:\Oracle\Product\Middleware\oms11g\BIN>emctl config oms -list_repos_details

    Oracle Enterprise Manager 11g Release 1 Grid Control
    Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
    Repository Connect Descriptor : (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=wintest01)(PORT=1528)))(CONNECT_DATA=(SID=emrep)))
    Repository Host : wintest01
    Repository Port

    Continue reading 11g Grid Control – how to change the OMS Repository Database Listener Port or Hostname

    Some more 11g Grid Control Installation and Configuration Notes

    Some time back I had posted a few notes on the 11g Grid Control installation and configuration.

    11g Grid Control Installation Tips and Solutions

    11g Enterprise Manager Grid Control Installation Overview

    I would like to highlight an extremely good resource on all things related to the 11g Grid Control setup including the WebLogic and Agent installation.

    Here is the link –

    How to Build a Grid Control Environment (11g)

    Also, here is a very good presentation by Ray Smith “An Introduction to OEM 11g” which was also presented at the Oracle Open World 2010 recently held in San Francisco.

    Ray has been kind to share this with the community and it has a lot of information on what has changed in the Oracle 11g Grid Control environment and includes both a run through of the architecture and an overview of the installation.

    Presentation: An Introduction To OEM 11g

    11g Grid Control Installation - tips and solutions

    Here are some notes I put together after performing a couple of installations of 11g Grid Control on a Solaris SPARC 64 bit platform. I also encountered some issues with the 11g agent and 9i and 10g databases. There is not too much user experiences available online, so I thought that I would share a few of my observations and feedback of the issues encountered and how I managed to overcome those issues.

    Kindly provide feedback of your experience with the 11g Grid Control product for the good of all the user community.

    For installation on 64 bit platforms, WebLogic Server (WLS) 10.3.2 is supplied as a generic .jar file: wls1032_generic.jar.

    For example: java -d64 -jar wls1032_generic.jar

    The java from jdk 1.6 must be used to install WLS, but this java is not embedded in the WLS stage on the 64bit platforms and must be downloaded and installed separately. We need to use

    Continue reading 11g Grid Control Installation – tips and solutions

    11g Enterprise Manager Grid Control Installation Overview

    Last week on the 23rd of April, Oracle has announced availability of 11g EM Grid Control on the Linux x86 and the Linux x86-64 platforms.

    I am attaching a document which has the screen shots of the installation process. There are some differences in the install process as well as prerequisites as compared to the 10g EM Grid Control which I will try to highlight.

    Before installing Enterprise Manager Grid Control, we need to install Oracle WebLogic Server 10.3.2. This is available on OTN under the Oracle Fusion Middleware 11g Software Downloads category.

    The installation will create a new Web Logic domain called GCDomain and we need to provide the location of the Oracle Middleware Home which was used to install the Web Logic server.

    The Oracle Middleware Home will be the location for the Web Logic Server and it’s components, the OMS and the Management Agent as well.

    In earlier releases of EM

    Continue reading 11g Enterprise Manager Grid Control Installation Overview

    EM Grid Control and High Availability

    A question often asked is can we use Oracle Data Guard as a high availibility option for the EM Grid Control Repository database. The repository database contains information on all the targets, the jobs configured, alerts and notification history etc. It has a lot of very valuable information and can be deemed as a fairly critical production database especially if there are hundreds of targets and hundreds of jobs defined in EM Grid Control. Also, how do we protect the Application Server part of the Grid Control environment? What do we do if lose the host where the management server resides?

    This note will provide an overview of setting up a DR environment for the EM Grid Control Repository database. It will show how using Oracle Data Guard, a database failover is done to the standby site as well as how to set up an additional OMS (Oracle Management Service)

    Continue reading EM Grid Control and High Availability

    How to manually clear EM Grid Control alerts

    We can use the procedure outlined below to clear outstanding warning and critical alerts which are displayed on the EM Grid console home page. Normally these alerts get cleared automatically when the event ot threshold which caused these events in the first place is longer in the ‘critical’ or ‘warning’ state.

    But there are some times when we wish to manually clear the alerts – there are some notes on Metalink which document cases where alerts are not cleared even after the event which caused them no longer exists – and also we may want to clear all the warning alerts which concern alerts related to logins by SYS user – out of the box auditing of the SYS user logins is enabled and every time SYS connects, it will generate a warning alert.

    In a forthcoming post I will detail now to create a customised monitoring template and deploy it enterprise

    Continue reading How to manually clear EM Grid Control alerts

    10g EM Grid Control Notification Rules and Corrective Action Jobs

    In 10g Enterprise Manager Grid Control, we can create corrective action or ‘fixit’ jobs which can automatically run if say a metric threshold is crossed or a particular event occurs. For example, we may have situations where we monitor the disk space used by the archive log files and as soon as the disk space free or available comes below a threshold, we would like another action to automatically occur which in this case could be to backup the archive log files to tape and then delete them to free up the disk space.

    Read more about this feature in this worked example …….