The document discusses Dell's upgrade from Oracle Enterprise Manager 10.2.0.5 to 12.1 using a two system upgrade approach. It describes the key components and architecture of Enterprise Manager 12c Cloud Control. It then outlines the four phases of the upgrade process: 1) reviewing requirements and preparing, 2) planning the upgrade using the pre-upgrade console, 3) upgrading the repository and installing the 12.1 OMS, and 4) deploying 12.1 agents and migrating data. The two system approach allows upgrading with zero downtime while maintaining the ability to rollback to the previous system if needed.
The document discusses Dell's upgrade from Oracle Enterprise Manager 10.2.0.5 to 12.1 using a two system upgrade approach. It describes the key components and architecture of Enterprise Manager 12c Cloud Control. It then outlines the four phases of the upgrade process: 1) reviewing requirements and preparing, 2) planning the upgrade using the pre-upgrade console, 3) upgrading the repository and installing the 12.1 OMS, and 4) deploying 12.1 agents and migrating data. The two system approach allows upgrading with zero downtime while maintaining the ability to rollback to the previous system if needed.
The document discusses Dell's upgrade from Oracle Enterprise Manager 10.2.0.5 to 12.1 using a two system upgrade approach. It describes the key components and architecture of Enterprise Manager 12c Cloud Control. It then outlines the four phases of the upgrade process: 1) reviewing requirements and preparing, 2) planning the upgrade using the pre-upgrade console, 3) upgrading the repository and installing the 12.1 OMS, and 4) deploying 12.1 agents and migrating data. The two system approach allows upgrading with zero downtime while maintaining the ability to rollback to the previous system if needed.
The document discusses Dell's upgrade from Oracle Enterprise Manager 10.2.0.5 to 12.1 using a two system upgrade approach. It describes the key components and architecture of Enterprise Manager 12c Cloud Control. It then outlines the four phases of the upgrade process: 1) reviewing requirements and preparing, 2) planning the upgrade using the pre-upgrade console, 3) upgrading the repository and installing the 12.1 OMS, and 4) deploying 12.1 agents and migrating data. The two system approach allows upgrading with zero downtime while maintaining the ability to rollback to the previous system if needed.
Roger Lopez, System Engineer, Dell Global Solutions Engineering Kai Yu, Sr. System Engineer Consultant, Dell Global Solutions Engineering Akanksha Sheoran, Seniour Product Manager, Oracle Corporation
Global Marketing About Authors Roger Lopez, System Engineer, Dell Oracle Solutions Lab 5 years as a Solutions Engineer Oracle expertise with Oracle VM and Oracle RAC databases Specialize in iSCSI SAN storage, Fibre Channel Storage, and Oracle database sizing Oracle VM Blog: http://rogerovm.com Kai Yu, Senior System Engineer, Dell Oracle Solutions Lab 16 years with Oracle Technology: DBA, Apps DBA, Engineer/Architect Oracle ACE Director, author and presenter 2011 OAUG Innovator of the Year Award Winner Oracle Blog: http://kyuoracleblog.wordpress.com Akanksha Sheoran, Senior Product Manager, Oracle Corporation Lead and manage the entire lifecycle of Enterprise Manager
2 Global Marketing Agenda Enterprise Manager Cloud Control 12.1 Architecture Dell Environment Two System Upgrade Approach (Zero downtime upgrade) Dell using Two System Upgrade Approach to perform upgrade from 10.2.0.5 to 12.1 Q&A
3 Global Marketing Enterprise Manager Cloud Control Architecture Enterprise Manager 12c Cloud Control consists of four main components:
4 Plug-ins Plug-ins Plug-ins Global Marketing Dells 10.2.0.5 Environment 5 10.2.0.5 Grid Control on Enterprise Linux 4.7 64 bit
Two Dell PowerEdge R710
One Dell Compellent Fibre Channel Storage
Various Database Clusters attached to 10.2.0.5 OMS
Global Marketing 12.1 Key Upgrade Improvements
Guided workflow and automation for upgrade process
Reporting functionality to administer and manage upgrade process
Near zero downtime
Pre-deployment checks and validations
Ability to upgrade agents in phases Ability to restore/revert to old Grid Control quickly Clarity and well defined upgrade path Details on what Software/Plug-in versions are required OS Migration along with upgrade Clarity on data that is migrated as part of upgrade process
6 Global Marketing Enterprise Manager 12.1 :Two System Upgrade approach 1. Start with existing 10.2.0.5 / 11.1 system 2. Apply the Upgrade console patch 3. Deploy 12.1 agents from upgrade console 4. Backup /restore the repository (Manually) 5. Deploy / configure OMS (can be on different host) and upgrade repository 6. Start the 12.1 OMS 7. Shutdown the 10.2.0.5 / 11.1 agents incrementally and activate12.1 agents 8. When all agents are successfully moved, decommission the pre-12.1 OMS Backup X X 7 Global Marketing 2- Systems Approach how to restore old system? 1. You will have your old GC system intact. We don't touch your old OMS. 2. We don't touch your repository and it will be up and running 3. You have to manually start your old agent 4. You have your old GC back
8 Global Marketing Highlights of the new upgrade approach provided by Enterprise Manager 12.1 You can plan your upgrade ! NO downtime of your OMS during upgrade Reports ! Reports ! Various reports to give you overall picture of your upgrade. Reports will tell you if your environment is ready for upgrade and what is required Simplifies upgrade process by allowing direct upgrade from Enterprise Manager 10.2.0.5/11.1.0.1 to 12.1 Provides a guided workflow for your complete upgrade process Easy fallback
9 Global Marketing Upgrading to Enterprise Manager 12.1
Phase 2 Phase 3 Phase 4 Phase 1 (Generic)
1.Review the Hardware/Software requirements of 12.1
2.Review the Certification Matrix to see if your repository and OS is certified with 12.1
3.Apply the Patch 10044087 to OMS home to get the Pre-upgrade console
4.Create a shared location (accessible from OMSes ) to store your 12.1 agent binaries and plugins
10 Global Marketing Phase 1 (Generic) Global Marketing Phase 1 Read the Upgrade guide Go through the Hardware and Software Requirements of 12.1 Go through the Certification Matrix for the repository and agent certification We had 10.1.0.4 repository with 10.2.0.5 Grid control. We upgraded it 10.2.0.5 before starting the upgrade to 12.1 Apply the patch 10044087 to your OMS home to get the Pre- Upgrade console. Follow the Readme for patch application instructions OPatch utility version must be 10.2.0.0.0 or higher
Created a shared location to store our EM 12c agent binaries and agents (i.e. via an NFS share) 12 Global Marketing What is Pre-Upgrade Console ? This is the starting point of your Upgrade planning Provides a guided workflow for your Upgrade Single source of truth for upgrade impact(reports) Agent Upgradability Target Upgradability Provides different upgrade approaches Perform 12.1 mass agent deployment with required plug-ins (this is the agent upgrade) We don't need any SSH connectivity to deploy the agents from the upgrade console as we use the existing agent communication(10.2.0.5 or 11.1) to transfer the bits Software Management for 12.1 Agent and plug-ins Runs dynamic pre-upgrade repository checks Before 12.1 agents are activated administrators can run readiness checks
13 Global Marketing
Phase 2 Global Marketing Identify Host and Port In this section, one must enter the a)Fully qualified hostname where they plan to install the 12.1 OMS b)12.1 OMS HTTPS Upload Port c)12.1 OMS HTTP Upload Port
Note: You have to provide the same ports while doing the 12.1 OMS Install 15 Global Marketing Manage Software 1. Provide shared location and click Validate
2. Contents of Shared Location : Agent and Plugin software
16 [oracle@kblademgr admin]$ cd /mnt/staging/ [oracle@kblademgr staging]$ ls 12.1.0.0.0_AgentCore_226.zip 12.1.0.0.0_AgentSoftware_226.zip 12.1.0.0.0_oracle.sysman.beacon_2000_0.opar 12.1.0.0.0_oracle.sysman.csa_2000_0.opar 12.1.0.0.0_oracle.sysman.db_2000_0.opar 12.1.0.0.0_oracle.sysman.emas_2000_0.opar 12.1.0.0.0_oracle.sysman.emct_2000_0.opar 12.1.0.0.0_oracle.sysman.emfa_2000_0.opar Global Marketing Manage Software 2 3. Go through the reports 17 This version of OS will not be supported by 12.1 so the report clearly display the message. If you want this target to be monitored by 12.1 then upgrade your OS to a certified version Global Marketing
Phase 3 Global Marketing Upgrade to Enterprise Manager 12c Install Oracle Enterprise Linux 5.5 and have access to shared storage After Deployment Confirm that all servers can accept and respond to ICMP traffic (i.e. ping) Install the latest oracle- validated RPM on target system Pre-upgrade steps have been completed from EM 12c Upgrade Console Install the Oracle Database 10.2.0.5 software and restore your backed up 10.2.0.5 database 19 Global Marketing Backup your existing Grid control repository You can choose any backup mechanism ( cold/hot backup, dbca, RMAN ..etc) to back your existing grid control repository
20 Repository Backup Date & Time Global Marketing Invoke the 12.1 installer to upgrade your existing EM While you invoke the 12.1 installer it gives you upgrade options
Select the correct option and provide the middleware home location. 12.1 Installer installs the WLS 10.3.5 along with 12.1 The 12.1 OMS is similar to fresh install with upgraded repository 21 Global Marketing Repository upgrade Provide the old (backed up) repository details and perform the repository upgrade 22 Global Marketing Upgrade done Once the upgrade is done go back to the pre-upgrade console 23 Global Marketing Create link to upgraded repository In the pre-upgrade console, provide the connect descriptor and click Create DB link
The location of the Connect Descriptor can be found at the following location: $OMS_12c_HOME/gc_inst/em/EMGC_OMS1/emgc.properties Location assigned to variable EM_REPOS_CONNECTDESCRIPTOR 24 Global Marketing
Phase 4 Global Marketing Agent Upgrades : Deploy and Configure 26 Mass Agent deployment Agent upgrades to 12.1 is out-of-place so you will get a fresh 12.1 oracle home. After deploying the 12.1 agent they are up and running but not uploading the data to 12.1 OMS Global Marketing Agent Upgrades : Deploy and Configure Integration with SUDO and Power broker
Ability to run the script pre or post agent deployment
27 Global Marketing Job Run: Deploying 12.1 Agents 28 Global Marketing Generate Health Report 29 Health report does various checks on the 12.1 agent before it starts uploading the data to 12.1 OMS It also does the ping check between the 12.1 agent and 12.1 OMS Global Marketing Sign Off Health Report 30 Global Marketing Switch from 10g Agents to 12.1 Agents 31 Global Marketing Agent Upgrade Status 32 Global Marketing Enterprise Manager 12c 33 Global Marketing Enterprise Manager 12c Agents 34 Global Marketing Post Upgrade Steps Data Migration Post Upgrade Console (from 12.1 Grid Control) Deferred data migration Lazy migration of historical data Status tracking from post upgrade console Ability to retry Accrued target data migration Applicable for two-system approach only Automatic migration of accrued data from old system to 12C 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 12c Console Global Marketing Questions or Feedback? 36