upgrading em13c collaborate 2016

Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Oracle Confidential 2

Kellyn Pot’Vin-Gorman and the EM Development GroupConsulting Member of Enterprise Manager Technical TeamStrategic Customer ProgramApril, 2016

Upgrade Oracle Enterprise ManagerThe Why and the How

Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Confidential – Oracle Internal/Restricted/Highly Restricted 3

DBA Kevlar, the Geek Goth Girl

Copyright © 2014 Oracle and/or its affiliates. All rights reserved. |

Safe Harbor StatementThe following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

Oracle Confidential 4


Program Agenda

1

2

3

4

5

Why Upgrade to EM 13.1.0.0

Enterprise Manager 13.1.0.0 - Deployment and Configuration

Road map : Zero Downtime EM Update and Upgrade

Gold Agent Image Upgrades

Tips and Learning More


Why Upgrade to Release Enterprise Manager 13c?


EM13c Deployment and ConfigurationEM 13.1.0.0 is full EM release

– EM (OMS +Agent +Plug-ins) binaries for all platforms available on same day

– Supports both Fresh Install and Upgrade to EM 13.1.0.0 • Management Repository supported in DB version 12.1.0.2 • OMS application deployed on WLS version 12.1.0.3 with JDK 1.7.0_71 • Integrated Deploy and Configure while doing Fresh Install OR Upgrade

– BI Publisher 12.1.0.3 integrated – JVMD 1.7 PSU80 integrated

• Simplified Binary extraction – No need to unzip the files


What does that mean?

Two more processes that are part of the EM startup results-


Upgrade Considerations and Requirements

• Newer version of OMS 13.1.0.0 is backward compatible with 12.1.0.3, 12.1.0.4, 12.1.0.5 agent version while going through the Upgrade process

– ***You can not deploy a fresh agent of version 12.1.0.x from OMS 13.1.0.0 • • Minimum Infrastructure Requirement for Linux-64 bit

*** Unless you find how to do it in Kellyn’s blog.


Tasks to Perform in Preparation

• Collect Diagnostics

• Prepare a step by step path for upgrade and encompass plans for all outliers:

-plugins

-features that will need to be updated for upgrade.

• Backup software in SW Repository


EM Diagnostics

• $ repvfy diag all

This includes as part of this collection:

-A verification sweep

-System reports like the system, performance, space report

- And specific sub-system health_report

- Performance oriented reports


Retaining Old Agent Images

./emcli get_supported_platforms ----------------------------- Version = 12.1.0.5.0 Platform = Linux x86-64Platforms list displayed successfully.

Query What Platforms are Available:

Export the Agent Software Out, (Note- You can only export the newest version of an agent out of the SW Library):

$./emcli get_agentimage -destination=/home/oracle/125 -platform="Platform = Linux x86-64" -version=12.1.0.5.0

Export File will be created, store in safe place…


Managing Downtime for Enterprise Manager

Phase 1: Always-On Monitoring

Phase 2: Zero Downtime Patching/Upgradee


What is Always On Monitoring?Highly available and scalable service that provides core monitoring capabilities

– Can be ‘always on’ to ensure continuous monitoring of mission critical environments

• Safeguards against impact of planned and unplanned EM downtime

– Available as a separate java application (Self-Update)


Key Features of Always On MonitoringMost Importantly:

– Receives target availability alerts and metric alerts from agents – Sends email notifications for target down, critical metric alerts

• Emails sent to addresses in ‘Downtime Contact’ target property


It’s All in the Details

• Downtime Contact target property – Global level: recipients for all alerts across all targets – Target-specific level: recipients for all alerts on the target.

• Can be populated based on current email recipients for target down event rule via sync with Enterprise Manager Cloud Control repository


What Part of Enterprise Manager Updates Require Downtime?

Patches

– Most EM patches involve code changes in Java and PL/SQL layers, requiring bounces in mid-tier and repository layers

– PL/SQL changes causes state invalidations and requires recompilation of other packages that are not participating in the patch bundle changes

– Sometimes, patch bundles include new features or features changes that involve schema changes


Plugins are Mini-Applications

Plug-ins and Platform

– They introduce new features, big schema changes (object definitions change) and new Java and PL/SQL code.

– The code and schema(s) are not organized to support multiple versions to co-exists, key requirement for on-line ability of “app”


Managing Enterprise Manager Downtime


Customers That Avoid Downtime….

Customer profile and expectations

– Almost all customers who wants zero-downtime updates have multiple-OMS architecture, (Maximum Availability Architecture)

– The big pain point is ‘frequent’ patch and plug-in updates. Eliminating as many of these through automation, (patch plans, automated blackouts and notification suppression during maintenance) is beneficial.

– For Platform updates: constrained version of EM (critical monitoring visibility) during Update often satisfies demand.


Zero Downtime with Edition Based Redefinition, (EBR)

• RDBMS 11.2+ has a feature called EBR that we can “adopt”.

• Provides high-availability of the objects to application when the objects are undergoing a change

• Provides a way for the application to switch to new edition of objects or rolled back to old edition of objects on demand

• Provides a way to support data-consistency during application’s switch-over


An EBR Based Rolling Update

• Divert Traffic from Each OMS Properly.

• Shutdown OMS1 and apply patch, then create edition.

• Bring backup OMS1, logon to new edition and divert traffic back to OMS1.

• Follow same steps now to OMS2 and then bring OMS2 back.


Timeline for an EBR Based EM Update


The Gold Agent Image• Provision, upgrade, and update Agents/Plug-ins in a highly scalable approach • Create Gold Image from live test agent patched and updated with required plug-ins • Export/Import of gold image( test agent) from Test to Prod EM • Promote gold images based on maturity level: Prod, Test • Report to show distribution of agents deployed with gold images • Picks configuration data from source agent emd.properties file • Cleanup of old Agent homes, Oracle home targets, and backup directories


Simplified Agent Standardization and Deployment

Jan 2016 PSU + Couple more patches*April 2016 Add 5 more patches + Config ChangesJuly 2016 PSU + 2 Plug-in Patches


Simple Dashboard Post EM13c Upgrade

No Need to Worry During Upgrade Process


Simplified Agent Lifecycle

• Update activity runs in batches based on the success criteria and frequency

– For example, if there are 1000 Agents deployed in your enterprise, the batch size is set to 100, and the batch success rate is set to 90, the Agents are updated in batches of 100. In this case, once a batch is complete, the application moves to the next batch only if 90 per cent of the total number of Management Agents are updated successfully.


Tips for Upgrading

1. Always Run an EM Diagnostics, (repvfy –details) before you decide to upgrade.

2. The health of your environment is crucial to a successful upgrade. If the environment has been neglected, then the upgrade process could be painful.

3. Ensure plugins are available. Most plugins are managed by the individual product group.

4. Backup older software from EM12c library before upgrading.


And Last but not Least...

Release 13.2 will be out before Oracle Open World.

Lots of fixes…


Questions?


Connect with me via Social Media:

upgrading em13c collaborate 2016

Technology