Configuration / Patching of EM 12c
Download as PPTX, PDF1 like1,131 views
Enterprise Manager 12c configuration and patching best practices are discussed. Key points include tuning thresholds and memory settings for optimal performance, applying the latest patches to the OMS, agents, plugins, and databases on a regular basis either monthly or quarterly, and testing patches on dev/qa groups first before deploying to production. The document provides recommendations on setting up credentials, groups, and patching strategies.
Configuration / Patching of EM 12c
- 1. sysco.no Enterprise Manager 12c – Config / Patching EM 12c Deep dive
- 2. sysco.no Overview • Configuration – Tuning thresholds – Tuning setup • Patching OMS / Agents – OMS – Agents – Plugins – Diagnostic agents – WLS – Database
- 3. sysco.no Overview • Goals – Stable EM Solution – Get new features/updates • Challenges – Updates cost – Do you have SLA on EM? – Will patches be successful?
- 4. sysco.no Performance • Have sufficient memory and cpu! • Disk access must be fast! • Previous version 12.1.0.2 of EM had «Performance Patch Bundle» • If you are on older version – upgrade (or new install)
- 5. sysco.no What to do after fresh install? • Read Note Oracle Enterprise Manager 12c Configuration Best Practices (Doc ID 1553342.1) • OMS – If you have more than 250 agents, increase the -Xmx parameter (maximum size) for the java heap to 2 gb Configuration
- 6. sysco.no Configuration Best Practices • Repository Recommendations – Repvfy execute optimize: establishes a baseline and sets the environment to the “recommended” values based on the config – Increase Task Workers – Check that there is no backlog – Increase Ping Grace Period – When 100’s or 1000’s of agents – Maintaing Audit Data: Initialize audit trail cleanup, set archive timestamp for audit records, create purge job Configuration
- 7. sysco.no Configuration Best Practices • Agent – Steps to Tune the Cloud Control 12c Agent Performance When Monitoring a Large Number of Targets (Doc ID 1349887.1) – enableAutoTuning=true (default on) – FMW: -Dweblogic.ThreadPoolPercentSocketReaders=80 -Dweblogic.ThreadPoolSize=XX (SOA may have lot of targets – and agent may die if not adjusted) Configuration
- 8. sysco.no Patch Set Update • Release Schedule of Current Enterprise Manager Releases and Patch Sets (10g, 11g, 12c) (Doc ID 793512.1) • Latest 12.1.0.3.2 Enterprise Manager Base Platform Patch Set Update (PSU) - Patch 18090046 • 12.1.0.4 expected Q2 CY14 according to MOS – And did – was released Tuesday - June 3rd Patching
- 9. sysco.no Patching EM Cloud Control • You can use EM to patch EM • First you need to setup connection to Oracle Support • You may need to add proxy Patching
- 10. sysco.no Patching EM Cloud Control • Or you may need to change in firewall – check note: Cannot Connect From 12c Cloud Control To https://updates.Oracle.Com (Doc ID 1436653.1) • At minimum, the following URLs should be made available through the firewall: – aru-akam.oracle.com – ccr.oracle.com – updates.oracle.com – login.oracle.com – support.oracle.com Patching
- 11. sysco.no Patching EM Cloud Control • Do not use your personal MOS account – must have access to all • Force an update Patching
- 12. sysco.no Upgrading Agents • Agents are versioned – for example 12.1.0.3 – Bundle patches have version number for example 12.1.0.3.9 • Upgrading a Management Agent modifies its installation base directory structure • Done from CLI or console Patching
- 13. sysco.no Patching Agents / Plugins • Enterprise Manager 12.1.0.3 Bundle Patch Master Note (Doc ID 1572022.1) • Current bundle patches • Bundles released last day of the month Patching
- 14. sysco.no Patching Agents • Management Agent • Recommended vs. not recommended (as in you do not have to) Patching
- 15. sysco.no Patching WLS • EM suggests WLS patches – PSU and other • Cannot patch OMS WLS from console, must use CLI • Patching WLS in OMS would require WLS Mgmt Pack Patching
- 16. sysco.no Experiences • Patching OMS using CLI (OPatch) • Patching Agents/Plugins using Console • Patching WLS using CLI (bsu) – The OMS is running on the WLS • Patching OMS sometimes takes long time (plugins) • You do not get patching advisory for Plugins, only Agents – But in 12.1.0.4 you do Patching
- 17. sysco.no Recommendations • Set up named credentials / preferred credentials • Create relevant groups used for patching • The Groups will give relevant Patch advise • The Groups will help you to patch with fewer steps • Separate groups in Dev, QA, Prod so that you can test on a smaller number of targets first Patching
- 18. sysco.no Recommendations • Decide on a patching strategy – Decide on if you will patch each month, quarterly, 2X per year ? – Will you patch as soon as a patch is available ? • Look at cost/benefit Patching
- 19. sysco.no Sequence • Patch OPatch on OMS (11.1) • Apply latest PSU to OMS • Apply latest WLS Patch • Apply latest patches to plug-ins OMS-side • Apply latest agent patches • Apply latest patches to plug-ins agent-side – Plugins may have two patches, ex Discover + Monitoring, not necessarily in same bundle patch version Patching
- 20. sysco.no What more to patch? • Upgrade JVMD/ADP engines with latest patches • Upgrade JVMD/ADP agents with latest patches • EMDIAG Repvfy Kit • Database • JVM • RDA Patching
- 21. sysco.no 12.1.0.4 - Features • The Self Update feature - Agent software, plug-ins • Global Preferred Credentials • Plug-in Management • Advanced Thresholds Management (adaptive) • Middleware: Target Management Best Practices • ++++++ • http://docs.oracle.com/cd/E24628_01/doc.121/e25353/whats_new.htm New version
- 22. sysco.no Q&A • Email: jonpetter.hjulstad@sysco.no • Twitter: jphjulstad