Upgrade to Enterprise Manager Cloud Control 12c Release 1 ...

1 <Insert Picture Here> Upgrade to Enterprise Manager Cloud Control 12c Release 1 ( )Akanksha Sheoran KalerSenior Product ManagerEM Upgrade Considerations and Requirements Significant architectural enhancements imply EM OMS can only work with EM agents This fundamental fact has brought about two overall procedure required to complete the Upgrade has changed has highlighted the necessity to provide a guided workflow through the entire process Upgrade is designed to be smooth and non-disruptive based on following requirements: 2010 Oracle Corporation Proprietary and Confidentialfollowing requirements: Minimal down time, if at all Pre-deployment checks and validations End to end automation of Upgrade process Dashboard and reporting functionality to administer and manage Upgrade process Support both turn-key and phased approach Ability to restore/revert to old Grid Control quickly.

2 OS Migration along with the Grid Control UpgradeEM - Simplified Pre- Upgrade Console Direct Upgrade from Grid Control Upgrade patch to receive Upgrade console Pre- Upgrade Console: Provides a guided workflow for your Upgrade Single source of truth for Upgrade impact(reports) 2010 Oracle Corporation Proprietary and ConfidentialSingle source of truth for Upgrade impact(reports) Perform mass agent deployment with required plug-ins Software Management for Agent and plug-ins Runs dynamic pre- Upgrade repository checks Before agents are activated administrators can run readiness checks. EM Upgrade Approaches Complete cutover with higher downtime (Using One System)* EM OMS and all agents upgraded at the same time, but with some downtime Both and installations co-exist but only one of them will be active at any given point in time.

3 Entire system (agents, OMS, Repository) gets upgraded/migrated to simultaneously. 2010 Oracle Corporation Proprietary and simultaneously. Phased cutover with minimal downtime (Using Two Systems)* Upgrade can be staggered over time, but this incurs minimal monitoring downtime Both and systems co-exist and be active simultaneously until all targets from are migrated to system in an orderly fashion. system will only contain agents/targets. * Henceforward referred to as One-system and Two-system approaches, respectivelyOne System with existing / EM health-check on EM agents )Quiesce agent queuesb)Shutdown the agents 2010 Oracle Corporation Proprietary and Confidentialc)Start EM the repository(manual)

4 The old EM OMS and Upgrade the the EM accepting EM agent connectionsBackupOne System Approach Vs Prior UpgradesOne System ApproachPrior Version UpgradesAutomated agent upgradeDoesn t use the job system, major version agent Upgrade required SSHH ealth checks and monitoring console availableNo health checks or monitoring of upgradeOut of place Upgrade Agent patching was in-place 2010 Oracle Corporation Proprietary and ConfidentialOut of place Upgrade Agent patching was in-placeOMS, Repository and agent switch over related downtimeOMS / Repository downtime, agents continue to collect dataFallback possibleFallback requires restoreAll agent platforms being monitored must be available (Oracle will make sure all EM agent software is released frequently)Agent upgrades can be staggeredTwo Systems with existing / EM /restore the / configure OMS and Upgrade repositoryX 2010 Oracle Corporation Proprietary and Confidentialupgrade the EM the agents incrementally and activate all agents are successfully moved, decommission the pre-EM OMSB ackupXXEM Post Upgrade StepsPost Upgrade Console (from EM )

5 Deferred data migration Lazy migration of historical data Status tracking from post Upgrade console Ability to retry Accrued target data migration 2010 Oracle Corporation Proprietary and Confidential Applicable for two-system approach only Automatic migration of accrued data from old system to EM Diff reports Configuration or setup-related changes that were manually made to the old system while 2-system Upgrade was happening Deleting Old Agents Ability to perform deletion of old agents from EM Console One System Vs Two System One System ApproachTwo Systems ApproachEntire system goes through downtime Zero downtime for monitoringAll agents switched at onceAgents can be switched over incrementallyFallback possible using restoreRelatively easy fallback if needed 2010 Oracle Corporation Proprietary and ConfidentialNo need for additional systemsRequires additional systemsAll agent platforms need to be available for upgradeAgent upgrades can be staggeredNo additional firewall ports need to be opened for agentAdditional ports to be opened (firewall rule edits needed)

6 Data migration not neededNeed to migrate accrued target data1 System 2 Upgrade ConsoleDecide your Upgrade approach1 View the Upgrade Impact report Manage your software in a central location 3 Mass Deploy Agents 42 System Best Practices 2010 Oracle Corporation Proprietary and ConfidentialPerform Health check1 Backup existing GC Repository324 Switch over agentInstall EM OMS and Upgrade the repository Post Upgrade Console 1 Backup and restore the repository(can be on diff host)Perform Health check32 Install EM OMS and Upgrade the resorted repositoryIncremental agent switchover 42 System Documentation and Help Always refer to the Upgrade guide on OTN: Post your queries on Install forum for any help: ;jsessionid= 2010 Oracle Corporation Proprietary and Confidential38 NcheTe3mMbhiQa38Sb40?

7 ForumID=4137&start=0 Installation and Upgrade collateral page on 2010 Oracle Corporation Proprietary and Confidential12 2010 Oracle Corporation Proprietary and ConfidentialOracle Confidential