em notes

Subscribe to posts

EM11g install - RAC found on Single Instance

posted 7 Jun 2012, 03:06 by Alan Nolan-Davies

Whilst running the EM11g installer I received an error telling me that the value of the initi parameter cluster_database was incorrect.

As I was trying to install EM11g on a single instance database this was not expected at all.

Looking into the logfiles crated I discovered that this error was being thrown out as the installer was querying the Real Application Clusters paramter in V$option and discovering that it was true?

Now although I do have RAC Enabled in this ORACLE_HOME I am not currently hosting any RAC databases, so on this occasion I was able to relink Oracle in this ORACLE_HOME with RAC turned off.
  1. shutdown all db's using this ORACLE_HOME
  2. cd $ORACLE_HOME/rdbms/lib
  3. make -f ins_rdbms.mk rac_off ioracle
  4. restart all db's and check v$option

If I was then going to use the same ORACLE_HOME for RAC and non-RAC databases I could then enable RAC once the Em11g install completed, or create a seperate ORACLE_HOME for the EM11g Repository Database.


Query OEM Targets in the Repository

posted 19 Mar 2012, 10:52 by Alan Nolan-Davies   [ updated 19 Mar 2012, 10:53 ]



This query can be imported into SQL Developer to show a graph of the targets in the OEM Repository and then further detail in a child query.

This runs against OEM 11.1

| Attachments: OEM_Targets.xml

Cloning the Oracle EM11g Agent

posted 25 Nov 2011, 02:17 by Alan Nolan-Davies

Copy the software to the new node

./runInstaller -clone -forceClone ORACLE_HOME=<full path of Oracle home> ORACLE_HOME_NAME=<Oracle home name> -noconfig -silent OMS_HOST=<oms_host> OMS_PORT=<oms_port>

>> prompted to run ORACLE_HOME/root.sh for the agent at this point <<

$<ORACLE_HOME>/bin/agentca -f -c "node1, node2, node3...."

EM12c Install Screenshots

posted 19 Oct 2011, 06:14 by Alan Nolan-Davies

em12c installation overview

em12c repository database recomendations

em12c plug ins

EM12c Launched at Oracle OpenWorld 2011

posted 5 Oct 2011, 13:26 by Alan Nolan-Davies   [ updated 5 Oct 2011, 13:27 ]

EM12c

Default Ports for EM11g

posted 20 Sept 2011, 09:17 by Alan Nolan-Davies


Enterprise Management

posted 19 Apr 2010, 03:53 by Alan Nolan-Davies   [ updated 22 Jul 2011, 07:46 ]

Using the Oracle Support Hub with 10.2.0.5 Grid Control

posted 15 Dec 2009, 03:36 by Alan Nolan-Davies   [ updated 22 Jul 2011, 08:04 ]

Reference Oracle Support Note: 886615.1 & http://download.oracle.com/docs/html/E14501_02/stdalone_rptr.htm
This guide is for how i did it on my RHEL 5 Grid Control host, but the Support Note referenced gives Windows examples as well.

  1. Check OMS host
    • $ORACLE_HOME/opmn/bin/opmnctl status -l | grep HTTP_Server
    • HTTP_Server        | HTTP_Server        |   24017 | Alive    | 1544486943 |   356216 |  20:02:24 | http1:7778,http2:7201,https1:4444,https2:1159,http3:4889
    • this identifies http3 (the direct console port) as 4889 [handy as this is the default value]
  2. The command line tool for the OCM Repeater is found in $ORACLE_HOME/ocm/bin
    • ./ocmrepeaterctl status
  3. I need to modify the Proxy Settings so that a connection can be made to the internet.
    ./ocmrepeaterctl configure

    enter the proxy details as username@proxy.host:80 - using your own username and proxy host of course, port is 80 "mostly"

    This will stop and start the repeater through opmn and checking the status again will show this is now set.




On the clients that will use the support hub, you configure using the files in $ORACLE_HOME/ccr/bin

  1. If this is a new install you will need to run setupCCR to deploy the OCM Application
    • may need to use setupCCR -s -d (if no connection to the internet is possible)
  2. then run $ORACLE_HOME/ccr/bin/emocmrsp -repeater http://<hostname>[:<port>]
  3. this creates an ocm.rsp (a response file with your proxy details)
  4. then run configCCR -R ocm.rsp
  5. finally test using emCCR -verbose test and you should see your hub server is used.


Grid Control Metrics Browser

posted 26 Oct 2009, 03:58 by Alan Nolan-Davies   [ updated 12 Sept 2011, 07:47 ]

It's possible in Grid Control to get the Agent on a monitored host to publish it's information to a browser without the need for a logon.

Very useful if you want to check that the Agent is working correctly, or for providing some useful links to developers while they are trying to debug peformance etc.
A text based list is viewable on your browser which you can drill down on to see more detail.



Below is the output when drilling down on the problemTbsp Metric.

UPDATE: The OEM 11.1 Manual is found at 

To enable the Metric Browser see the Troubleshooting Metrics chapter in the Enterprise Manager Framework, Host and Services Metric Reference Manual.

Follow these steps to enable the Metric Browser.

  1. The Metric Browser is enabled by setting the enableMetricBrowser property in the Management Agent's emd.properties file. The location of that file depends on the type of Management Agent you are working with:

    • For the Grid Control (central|standalone) Management Agent, the file is:

      <AGENT_HOME>/sysman/config/emd.properties

    • For a clustered (RAC) Management Agent install, the file is:

      <AGENT_HOME>/<hostname>/sysman/config/emd.properties

    • For the Database Control Management Agent, the file is:

      <DATABASE_HOME>/<hostname>_<SID>/sysman/config/emd.properties

    • For Application Server Control Management Agent, the file is:

      <AS_HOME>/sysman/config/emd.properties

  2. Make a backup copy of the emd.properties file.

  3. Edit the file and locate the line that reads:

    #To enable the metric browser, uncomment the following line
    #This is a reloadable parameter
    #
    #enableMetricBrowser=true

  4. Uncomment the line: #enableMetricBrowser=true, so that it reads:

    enableMetricBrowser=true

  5. Reload the Management Agent Configuration using the command:

    <AGENT_HOME>/bin/emctl reload agent

  6. After reloading the Management Agent, the Metric Browser will be enabled and therefore accessible using a browser.




Stress Testing using Grid Control

posted 20 Jul 2009, 08:17 by Alan Nolan-Davies   [ updated 22 Jul 2011, 08:04 ]

Using Grid Control Jobs to generate Load on the Database   


exec dbms_session.set_identifier('Alan Stress Test 5');
exec dbms_application_info.set_module('Alan Stress Test 5','Create Table');
create table alanstresstest5 as select * from alanloadtest;
exec dbms_application_info.set_module('Alan Stress Test 5','Query Table');
select count(*) from alanstresstest5;
exec dbms_application_info.set_module('Alan Stress Test 5','Update Table');
update alanstresstest5 set status =  'STRESS' where owner='ALANNOLANDAVIES';
exec dbms_application_info.set_module('Alan Stress Test 5','Create Index');
create index stressindex5 on alanstresstest5(object_name);
exec dbms_application_info.set_module('Alan Stress Test 5','Delete from Table');
delete from alanstresstest5 where object_id between 1000 and 2000;
exec dbms_application_info.set_module('Alan Stress Test 5','Query Table');
select count(*) from alanstresstest5;
exec dbms_application_info.set_module('Alan Stress Test 5','Drop Table');
drop table alanstresstest5;


| Attachments: performance.pdf

1-10 of 10