Mangled Or Managed


Published on

Presentation on Enterprise Management, reality vs hype, to be delivered to UKOUG Dec 1 2009. V0.9 (some additions and tweaks left)

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • OMS is a J2EE Web application that orchestrates with Management Agents to discover targets, monitor and manage them, and store the collected information in a repository for future reference and analysis. OMS also renders the user interface for the Grid Control console. OMS is deployed to the application server that is installed along with other core components of Grid Control.J2EE ApplicationScalable – via multi-jvmsClusterable – multiple InstancesJava
  • Management Agent is an integral software component that is deployed on each monitored host. It is responsible for monitoring all the targets running on those hosts, communicating that information to the middle-tier Oracle Management Service, and managing and maintaining the hosts and its targets.Monitors its list of targets Defined in targets.xmlDiscovered by discovery process (varies by type)Communicates with management serviceUploads informationRuns jobs Configuration in file (in %ORACLE_HOME%sysmanconfig)
  • Ist of standard portsCan varyFirewalls may well need to be aware.
  • Fairly standard profile for a reasonably used db.
  • Note more useful to look at executions than runs
  • NB this is a non-oracle non tcl based web application running on a highly customised open source tcl application server.
  • Prior tp Release 5 template settings were only chagned where the metric already had a setting and you were setting a new one. So if you wanted to remove a setting you couldn’t.
  • Bugs agent healthcheck for different db versionClone db files must be smaller than 2gb till current version)Subject: Agentca Target Discovery Selects Wrong Database Name For Dataguard TargetAgent Installation Hangs at the Target Discovery Process Due to Customized glogin.sql FileLogfilesOms Note 550395.1 , emagentConfigurationAgent – Note 235290.1OMS Note 733401.1Discovery Targets.xml – Note 239224.1 (discovery) 365252.1(recreate)Non-oracle clusters , eg failsafe, vcs mutating tableStatusGet passwords set. CachingPages show wrong status for a surprising length of time sometimes. Email formatsUntil 5Statspack integrationBetter off doing your own thing
  • Mangled Or Managed

    1. 1. Mangled or Managed?Does Grid Control Deliver<br />
    2. 2. Agenda<br />About <br />Maxima<br />Me<br />Enterprise Manager<br />Architecture<br />Good<br />Bad<br />Troubleshooting<br />Licensing<br />Plugins<br />Conclusion Q&A<br />
    3. 3. Who we are<br />Maxima is one of the UK and Ireland’s leading IT solution and service providers, offering a unique blend of deep industry knowledge and specialist technology expertise to deliver real business value to organizations of all sizes across a wide range of commercial sectors.<br />
    4. 4. Who I am<br />UKOUG – Chair of UKOUG Oracle on Windows SIG (come present for us)<br />Maxima – Consultant DBA, Maxima Managed Services<br />Oak Table – Windows, “you always make me laugh”, “and another thing”. <br /><br />Manager of apps dbas<br />Manager of developers<br />Auditor<br />Father of 3 under 8 – try it, managing developers is easier. <br />Sussex CCC – long suffering then glory.<br />Liverpool FC – glory then long suffering. <br />
    5. 5. Architecture<br />Understanding the design<br />
    6. 6. Enterprise Manager Architecture<br />
    7. 7. Oracle Management Server<br />
    8. 8. Oracle Management Repository<br />Oracle - End Premier Support Jan 2009<br />All EM Releases are patches to base release. Can’t use a supported release as an install target.<br />Note 467677.1 – How to Install Grid Control to use 11g for the Repository<br />
    9. 9. Oracle Management Agent<br />32bit Java application.<br />Does most of the work<br />Communicates <br />
    10. 10. Infrastructure Communications<br />http 7777 – EM Website<br />https 4889 – EM Website including agent to OMS<br />https 1831 – OMS to Agent<br />jdbc - OMS to Repository<br />Check Ports carefully<br />
    11. 11. The good<br />
    12. 12. Performance Tuning<br />
    13. 13. Blackouts<br />Provide a way to schedule reduced monitoring<br />Server room outage<br />Database Upgrade in multi-standby environment<br />
    14. 14. Reporting<br />Remember I used to be a manager!<br />
    15. 15. Scripting<br /><ul><li>Perl jobs</li></li></ul><li>Job System<br /><ul><li>Stats Gathering
    16. 16. ETL
    17. 17. Data Movement</li></li></ul><li>Service Level Management<br /><ul><li>Availability and Performance</li></li></ul><li>Monitoring Templates<br /><ul><li>Work properly as of</li></li></ul><li>Helpdesk Integration<br />Email customisation<br />Remedy Connector<br />Remedy Connector<br />
    18. 18. The bad<br />
    19. 19. Notable bugs<br /><ul><li>Healthcheck for different db version
    20. 20. Clone db files must be smaller than 2gb till current version
    21. 21. Target Discovery Selects Wrong Database Name For Dataguard Target
    22. 22. Agent Installation Hangs at the Target Discovery Process Due to Customized glogin.sql File</li></li></ul><li>Configuration Issues<br />.properties files<br />Status of database instance<br />Non-oracle clusters (lifekeeper ,vcs, etc)<br />Web cache<br />Statspack integration<br />
    23. 23. Troubleshooting<br />
    24. 24. Basic Approach<br />Identify the problem component<br />Record symptoms (error messages, response time).<br />Locate related logfiles<br />Review log files around time of exception for any related error entries.<br />Resolve the error.<br />
    25. 25. Web Server<br />Oracle HTTP Server (Apache)<br />$ORACLE_HOME/Apache/Apache/logs<br />The following log files can be reviewed:<br />Access Log<br />Error Log<br />SSL Log (If using SSL, and error is SSL related)<br />$ORACLE_HOME oms10g<br />
    26. 26. Web Cache<br />Runs in Oracle HTTP Server home<br />$ORACLE_HOME/Apache/Apache/logs<br />Event.log <br />Note 454533.1 Common Troubleshooting Techniques for OracleAS Web Cache<br />Note 259796.1 OracleAS Web Cache event_log messages: Format and Meaning<br />
    27. 27. Oracle Management Server<br />Managed by opmn<br />PATH=$ORACLE_HOME/oms10g/opmn/bin:$PATHexport $PATH<br />Makes it easier to use correct opmnctl<br />Start/Stop components individually<br />opmnctl startopmnctlstartprocias-component=WebCacheopmnctlstartprocias-component=HTTP_Serveropmnctlstartproc process-type=homeopmnctlstartproc process-type=OC4J_EMopmnctlstartproc process-type=OC4J_EMPROV<br />
    28. 28. Management Server Status<br />[oracle@gcserver ~]$ opmnctl status –v<br />Processes in Instance: EnterpriseManager0.gcserver.domain<br />-------------------+--------------------+---------+----------+------------+----------+-----------+------<br />ias-component | process-type | pid | status | uid | memused | uptime | ports<br />-------------------+--------------------+---------+----------+------------+----------+-----------+------<br />DSA | DSA | N/A | Down | N/A | N/A | N/A | N/A<br />HTTP_Server | HTTP_Server | 20759 | Alive | 1327300712 | 42332 | 291:14:29 | http1:7778,http2:7200,https1:4444,https2:1159,http3:4889<br />LogLoader | logloaderd | N/A | Down | N/A | N/A | N/A | N/A<br />dcm-daemon | dcm-daemon | N/A | Down | N/A | N/A | N/A | N/A<br />OC4J | home | 20760 | Alive | 1327300713 | 26852 | 291:14:57 | ajp:12501,rmi:12401,jms:12601<br />OC4J | OC4J_EMPROV | 20761 | Alive | 1327300714 | 29772 | 291:14:57 | ajp:12502,rmi:12402,jms:12602<br />OC4J | OC4J_EM | 14041 | Alive | 1327300754 | 452092 | 86:09:11 | ajp:12503,rmi:12403,jms:12603<br />WebCache | WebCache | 20771 | Alive | 1327300716 | 27612 | 291:14:57 | http:7777,invalidation:9401,statistics:9402<br />WebCache | WebCacheAdmin | 20764 | Alive | 1327300717 | 5924 | 291:14:57 | administration:9400<br />
    29. 29. OC4J Verification<br />home - IsWebCacheWorking<br />HTTP://&lt;GC_URL/ IsWebCacheWorking<br />
    30. 30. OC4J Verification<br />EM – Rules Manager Login <br />http://&lt;GC_URL&gt;/rlmgr/rlmgr_login.htm<br />
    31. 31. OC4J Verification<br />EM Prov – Agent Deploy Page<br />&lt;EM URL&gt;/EMAgentPush/home.jsp<br />
    32. 32. OC4J - Logs<br />$ORACLE_HOME/j2ee/&lt;OC4J_instance&gt;/log/&lt;OC4J_instance&gt;_default_island_1/logfile<br />default-web-access.log<br />server.log<br />2gb limit on some platforms<br />
    33. 33. Licensing<br />
    34. 34. License basis<br />Grid control free<br />Infrastructure Repository Databases A separate Oracle Database can be installed and used as a Recovery Manager (RMAN) repository without additional license requirements, provided that all the Oracle databases managed in this repository are correctly licensed. This repository database may also be used for the Oracle Enterprise Grid Control repository. It may not be used or deployed for other uses.<br />A separate Oracle Database can be installed and used as a Oracle Enterprise Manager Grid Control (OEM Grid Control) repository without additional license requirements, provided that all the targets (databases, applications, and so forth) managed in this repository are correctly licensed. This database may also be used for the RMAN repository. It may not be used or deployed for other uses<br />Management packs do cost<br />Management packs still cost without GC<br />Eg awrrpt.sql <br />
    35. 35. Plugins<br />A wide variety of extra cost options<br /><br />Oracle-l (self developed sqlserver)<br />
    36. 36. Conclusions<br />Grid Control is a mature product.<br />Grid Control can be complex. <br />Probably not worth it for small installations &lt; 5 databases/3 servers<br />Strategic product<br />