Your SlideShare is downloading. ×
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

UPGRADING FROM ORACLE ENTERPRISE MANAGER 10G TO CLOUD CONTROL 12C WITH ZERO DOWNTIME

2,606

Published on

A step-by-step description of using the 2-System Method to upgrade from Oracle Enterprise Manager 10g to Enterprise Manager Cloud Control 12c while upgrading database and migrating platforms with near …

A step-by-step description of using the 2-System Method to upgrade from Oracle Enterprise Manager 10g to Enterprise Manager Cloud Control 12c while upgrading database and migrating platforms with near zero downtime.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,606
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
109
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Manageability1 Session # 864UUPGRADING FROMPGRADING FROM OORACLERACLE EENTERPRISENTERPRISE MMANAGERANAGER 1010G TOG TOCCLOUDLOUD CCONTROLONTROL 1212C WITHC WITH ZZEROERO DDOWNTIMEOWNTIMELeighton L. Nelson, MercyAbstractOracle Enterprise Manager 12c is the comprehensive enterprise management product specially suited for Oracle infrastructureand applications including Oracle Database Server, Fusion Middleware and Oracle Linux. It has been significantly improvedcompared to previous versions. However, if you already have a previous version deployed and you need to take advantage ofall the features in 12c you need to have a solid path for doing so. Fortunately, Enterprise Manager provides the framework forseamlessly upgrading your environment.In addition, if your currently deployed environment is vital to your IT datacenter operations and you have already invested insignificant time and effort into enhancing your environment such as custom reporting, job scheduling and user-definedmetrics, then you should ensure that there is minimal disruption to these services. The 2-System Method Upgrade methodprovides the framework for achieving these goals.In this paper we will take a look at how Mercy used this method to migrate from AIX 6.1 to Red Hat Enterprise Linux 6.2,upgrade repository database version from 11.1.0.6 to 11.2.0.3 while upgrading to Enterprise Manager from Grid Control 10gto Cloud Control 12c.Target AudienceThis paper will benefit those responsible for configuring, managing and monitoring Oracle databases and Fusion Middlewarecomponents using Oracle Enterprise Manager. These are typically database administrators or enterprise manageradministrators.Executive SummaryLearners will be able to:• Learn about the different upgrade methods for Enterprise Manager Cloud Control 12c• See how the 2-System Method is used to migrate from an older version of Enterprise Manager to Cloud Control 12cwith minimal downtime.• Identify pitfalls and lessons learned from the upgrade.BackgroundOur existing Enterprise Manager Grid Control 10g environment had the following configuration.Current Architecture (IBM JS21 Blades)• Single Management Service – 10.2.0.5 / AIX 6.1• Single Instance Repository Database – 11.1.0.6 / AIX 6.1• Agents – 100 (AIX + Linux)• Targets – 500+• Proposed Architecture (VMware vSphere)• OMS – 12.1.0.2 / RHEL 6.2• Repository Database – 11.2.0.3 / RHEL 6.2
  • 2. Manageability2 Session # 864• Agents – 100 (AIX + Linux)• Targets – 500+Proposed Architecture (VMware vSphere)• 2 Management Services (load balanced) – 12.1.0.2 / RHEL 6.2• Repository Database with local Data Guard – 11.2.0.3 / RHEL 6.2• Agents – 100 (AIX + Linux)• Targets – 500+Technical Discussions and Examples1. Install Pre-Upgrade ConsolePSU 3 or greater required to be installed. Check the inventory for applied patches and PSUs using opatch. In the examplebelow.oemhost1[emrep]-/home/oracle >opatch lsinventory -bugs_fixed|grep PSU9174904 9702579 Wed Nov 23 12:37:30 CST 2011 ENTERPRISE MANAGER OMS 10.2.0.5.2 PSU9282397 9702579 Wed Nov 23 12:37:30 CST 2011 ENTERPRISE MANAGER OMS 10.2.0.5.3 PSUWITH OMS PSU3 INSTALLED9702579 9702579 Wed Nov 23 12:37:30 CST 2011 ENTERPRISE MANAGER OMS 10.2.0.5.4 PSU? EM CONTENT(PSU-4) JUL2010Shutdown the OMSoemhost1[emrep]-/home/oracle >$OMS_HOME/bin/emctl stop omsOracle Enterprise Manager 10g Release 5 Grid ControlCopyright (c) 1996, 2009 Oracle Corporation. All rights reserved.Oracle Management Server is Down.Set ORACLE_HOME to OMS_HOMEoemhost1[emrep]-/u05/orastage/14375077 >export ORACLE_HOME=$OMS_HOMEGo to patch location and run opatchoemhost1[emrep]-/u05/orastage >which opatch/u04/app/oracle/oms10g/OPatch/opatchoemhost1[emrep]-/u05/orastage >cd 14375077oemhost1[emrep]-/u05/orastage/14375077 >opatch applyEnd of patch should say succeeded.Return Code = 0OPatch succeeded.oemhost1[emrep]-/u05/orastage/14375077 >cd $OMS_HOME/sysman/preupgcoemhost1[emrep]-/u04/app/oracle/oms10g/sysman/preupgc >sqlplus /nologSQL*Plus: Release 11.2.0.1.0 Production on Fri Sep 14 11:30:21 2012Copyright (c) 1982, 2009, Oracle. All rights reserved.SQL> conn / as sysdbaConnected.SQL> @puc_dblink_pkgdef.sql
  • 3. Manageability3 Session # 864Package created.No errors.Package created.SQL> @puc_dblink_pkgbody.sqlPackage body created.No errors.Package body created.SQL>@pre_upg_console.sql…1 row merged.optimized l_target_guids.COUNT : 4oracle.sysman.beacon SMPADDON 10.2.0.5.0 Oracle Beacon Pluginoracle.sysman.emrep SMPADDON 10.2.0.5.0 Oracle Management And Repository Pluginoracle.sysman.oh SMPADDON 10.2.0.5.0 Oracle OracleHomeoracle.sysman.csa SMPADDON 10.2.0.5.0 Oracle Client System Analyzeroracle.sysman.db SMPADDON 10.2.0.5.0 Oracle Database Pluginoracle.sysman.emas SMPADDON 10.2.0.5.0 Oracle Fusion Middleware Pluginoracle.sysman.empa ADDON 10.2.0.5.0 Oracle Siebel Pluginoracle.sysman.vt ADDON 10.2.0.5.0 Oracle Virtualization Pluginoracle.fmw.bhv ADDON 10.2.0.5.0 Oracle Beehive PluginPL/SQL procedure successfully completed.PL/SQL procedure successfully completed.PL/SQL procedure successfully completed.Commit complete.Start OMSoemhost1[emrep]-/u04/app/oracle/oms10g/sysman/preupgc >$OMS_HOME/bin/emctl start omsOracle Enterprise Manager 10g Release 5 Grid ControlCopyright (c) 1996, 2009 Oracle Corporation. All rights reserved.opmnctl: opmn is already runningStarting HTTP Server ...Starting Oracle Management Server ...Checking Oracle Management Server Status ...Oracle Management Server is Up.
  • 4. Manageability4 Session # 8642. Log into the EM Console and click on the Deployments tab.A new Upgrade procedure and Enterprise Manager 12c Upgrade Console link appears (see Figure 1).Figure 1 – Enterprise Manager 12c Upgrade Console link after apply Pre-Upgrade patchFigure 2 below show the Pre-Upgrade Console
  • 5. Manageability5 Session # 864Figure 2 – Upgrade Console
  • 6. Manageability6 Session # 8643. Select the 2-System radio button to activate the procedures for this method.4. Identify Host and Port for New Enterprise Manager SystemEnter the fully qualified domain name of the target host and OMS HTTPS Upload Port and OMS HTTP Upload Port – 4899and 4889 by default. If you are using a Server Load balance you should also check the associated box.You may also disable the deferred data migration and accrued data migration jobs by checking the respective boxes. ClickSave.Figure 3 – Identify Host and Ports for new OMS
  • 7. Manageability7 Session # 8645. Manage SoftwareClick the Manage Software Link in the Upgrade Console page. This allows you to define the path of the plug-ins and agentsdownloaded from OTN (see Figure 4). This should preferably be a shared location accessible by the new and old OMS. Plug-ins will be upgraded during the new OMS installation.Figure 4 – Manage Software and plug-ins6. Enter the path of the downloaded plug-ins and agent software for the platforms you want to manage. From the OTN page(see Figure 5) follow steps carefully to select the plug-ins and agents needed for your path.
  • 8. Manageability8 Session # 864Figure 5 – Agent Software and Plug-ins for OEM upgradeIn this case we are following Path 1 – Upgrade from EM 10.2.0.5/11.1.0.1 to EM 12.1.0.2The directory listing below shows all the files downloaded and staged.oemhost1[emrep]-/mnt/em_upgrade/em12cr2_plugins >ls -ltrtotal 2019520-rw-r--r-- 1 oracle dba 1762394 Sep 14 10:0312.1.0.2.0_oracle.sysman.oh_2000_0.opar-rw-r--r-- 1 oracle dba 119951825 Sep 14 10:0612.1.0.2.0_oracle.sysman.beacon_2000_0.opar-rw-r--r-- 1 oracle dba 11758937 Sep 14 10:0712.1.0.2.0_oracle.sysman.mos_2000_0.opar-rw-r--r-- 1 oracle dba 298841 Sep 14 10:0712.1.0.2.0_oracle.sysman.emrep_2000_0.opar-rw-r--r-- 1 oracle dba 328765196 Sep 14 10:1212.1.0.2.0_oracle.sysman.db_2000_20120804.opar-rw-r--r-- 1 oracle dba 333968065 Sep 14 10:16 12.1.0.2.0_AgentCore_212.zip-rw-r--r-- 1 oracle dba 233396034 Sep 14 10:17 12.1.0.2.0_AgentCore_226.zip
  • 9. Manageability9 Session # 8647. Once the files have been downloaded and staged, you can add this path to software location and click Validate button. Thiswill submit a job that will refresh and validate the targets for upgradeability.Note: Agent Upgradeability and Target Upgradeability charts should be displayed in green. This will signify that all targets canbe upgraded. If not, further remediation may be required before continuing with the rest of the upgrade.Figure 6 – Refresh And Validate Target job submitted8. Check the Section Under Software Required for Upgrade (see Figure 7) to verify that all plug-ins listed has beendownloaded and staged. If there are missing plug-ins or agents you should download and stage them in the directory pathspecified by Software Location and retry the Validation.Figure 7 – Verify Agent and Plug-in Software
  • 10. Manageability10 Session # 864At this point there are two options1) Backup repository before deploying the Agents2) Deploy agents and then take the repository backupThe option you choose will depend on the number of targets you have to migrate, how often agents are added and deleted,and the duration of elapsed time before performing agent switchover. If the environment is fairly static either option can bechosen. If there are expected changes during the migration over a period of at least a week you may want to perform thebackup after doing the agent deployment. Here we will deploy and configure agents before taking a backup of the repositorydatabase.Deploy and Configure AgentsSince only 12c agents can communicate with 12c OMS, you must deploy the 12c agents before upgrading your OMS. Go tothe Deploy and Configure Agents section of the Upgrade Console to deploy the agents to the existing targets.Note: Agent deployment will create host level jobs that require the software installation owner i.e. oracle to be able toaccess the servers. If you don’t use local authentication (via /etc/passwd) then you should work with your systemsadministrator to setup PAM for emagents. (PAM modules exist for ldap, Kerberos, secureid etc.)Add the agents you want to deploy to the procedure. You can filter agents by platform or version to limit a set of agents to bedeployed. Enter the path for the agent base and instance directories (see Figure 8).Note: The top-level directory chosen should either be owned by oracle or root. This may require installing the agenton a different filesystem.Note: The procedure automatically uses ‘agent12g’ instead of ‘agent12c’ in the agent base and instance paths. You maywant to use the latter nomenclature.There is also the option of using the same path for all hosts (recommended). In some cases you may have to use separatepaths.Provide the agent credentials for the deployment. This is typically ‘oracle’. If you use a sudo or Power Broker for securitypurpose you may also check these settings.Select the agents to be deployed and configured and click Next.
  • 11. Manageability11 Session # 864Figure 8 – Deploy and Configure Agents
  • 12. Manageability12 Session # 864Enter the root credentials to run the root.sh script. If you don’t have access to root credentials you can still enter any dummyusername/password here. Deployment will still succeed but you will have to manually run root.sh scripts later.Figure 9 – Pre-Deploy Options for AgentClick Submit to create the Deploy agent job (see Figure 10).Figure 10 – Submit Job to Deploy and Configure Agents
  • 13. Manageability13 Session # 864Clicking on the job link will take you to the screen where you can monitor job progress (see Figure 11).Figure 11 – Job Activity progress for Agent DeploymentIf the valid root password was not provided during agent deployment you should run the root.sh scripts manually. If not ,youmay get errors while executing host jobs using the new agent. (ERROR: NMO Not Setuid-root)Backup repository databaseIn the case of migrating between similar platforms you can also use DBCA (recommended) or RMAN backups.However, in order to do a platform migration from AIX to Linux only two options available.1. Datapump Import/Export2. Cross Platform Transportable TablespacesNote: Using either option above requires that both source and target databases use the same character set.See Oracle Database Server 11g documentation on using Cross-Platform tablespaces.For cross-platform migration refer to MOS note 388090.1Both these cases require a pre-existing database that is certified with the 10.2.0.5 or 11.1 version of Enterprise Manager.See Appendix A for database backup details.Oracle EM 12.1.0.2 provides a seed database template which is already pre-configured for Enterprise Manager 12c installation.The template requires Oracle Database 11.2.0.3 software to be installed on the target server. For details on using the templaterefer to the Oracle Enterprise Manager Cloud Control Basic Installation Guide.Before performing the repository backup ensure that the emkey has been copied to the repository using the followingcommand.emctl config emkey –copy_to_repos –sysman_pwd <password>
  • 14. Manageability14 Session # 864Once the database has been backed up successfully, verify that SYSMAN schema doesn’t contain invalid objectsSELECT count(*) from user_objectsWHERE status=‘INVALID’;Provide Repository backup detailsEnter the date/time when the repository backup was taken. This is used by the ADDMP and DDMP after the OMS isupgraded. You can find use the timestamp of the data pump log files to get the backup time.Figure 12 – Repository Database Backup Date/TimeUpgrade OMS and Repository ManuallyNext step will be to Upgrade the OMS and Repository.It is important to verify that all your pre-requisites are met for the OMS and repository before beginning the upgrade.Repository Database Pre-requisites• Verify database initialization parameters• PROCESSES parameter is at least 300. The installer can also make the changes if desired.• Set JOB_QUEUE_PROCESSES to 0• Set SHARED_POOL_SIZE to 700MB or greater• PGA_AGGREGATE_TARGET should be at least 1GB• SGA_TARGET should be at least twice PGA_AGGREGATE_TARGET• Grant execute on DBMS_RANDOM to DBSNMP and SYSMAN• Unlock ORACLE_OCM account• Increase your redo log size to at least 300MB due to the high level of transactions during the repository.• Check to make sure your emkey is in the repositoryTip: Create guaranteed restore point on both the old and new repository database so that changes can be easily flashed back;create restore point PRE_OMS_UPGRADE guarantee flashback database;EM Prerequisite Kit UtilityEM Prerequisite Kit Utility can verify that the database pre-requisites are met before starting the upgrade. The example belowshows the pre-requisites that will be checked. See Appendix B for additional details.EM12c_STAGE_DIR/install/requisites/bin/emprereqkit -executionType upgrade -prerequisiteXMLLoc install/requisites/list -connectString"(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=dbhost1)(PORT=1521)))(CONNECT_DATA=(SID=emrep)))" -dbUser SYS -dbPassword -dbRole sysdba -showPrereqs
  • 15. Manageability15 Session # 864OMS Server Verification• Verify that server meets pre-requisites• Check ulimit to make sure it’s at least 4096• ulimit –n• If using RHEL 6.2 or Oracle Linux 6.2 – make sure you have the following package installed or else your installation mayfail at OMS Configuration Assistant.• glibc-2.12-1.47.0.2.el6_2.12.x86_64• See MOS note: EM12c: Installation Fails On Linux 6 at "Start Oracle Management Service" step (Doc ID 1472216.1)for workaroundStart runInstallercd /stage/./runInstallerFigure 13 – Run Upgrade on the new OMS Server using the OEM12c OUI
  • 16. Manageability16 Session # 864It is recommended to download software updates during upgrade. See MOS Note 1099123.1 for details on the “Auto Update”feature. This is not selected in the figure 14 below.Figure 14 – Check for Software Updates
  • 17. Manageability17 Session # 864Provide the location for the inventory and choose the OS group for the software owner. This will typically be ‘oinstall’ or‘dba’ depending on your environment.Figure 15 – Provide Inventory location and Select OS group
  • 18. Manageability18 Session # 864Verify that all pre-requisites have been met. If there are any warnings or errors, examine and fix them before proceeding withthe installation. In Figure 16 below, the glibc pre-requisite check failed. This is a known issue. See workaround in MOS note1472216.1. This may not be applicable to more recent versions of Linux.Figure 16 – Check Pre-requisitesbash $ rpm -qa|grep glibc-2.12-1.47glibc-2.12-1.47.el6.x86_64glibc-2.12-1.47.el6.i686
  • 19. Manageability19 Session # 864The installer is checking for an exact match for glibc-2.12-1.47.0.2.el6_2.12.x86_64. Install this package if possible beforecontinuing with the installation. If not, further workarounds may be necessary before completing the installation. In Figure 17below, it is ignored to complete the demonstration.Figure 17 – Pre-requisite Check for Packages FailedChoose the “Upgrade an Existing Enterprise Manager System” option for Two System Upgrade as shown in Figure 18.
  • 20. Manageability20 Session # 864Figure 18 – Select Upgrade Method
  • 21. Manageability21 Session # 864Provide the repository database fully qualified hostname, port, service/SID as well as SYS and SYSMAN passwords.Figure 19 – Repository Database Connection DetailsReview any errors discovered in the configuration by reviewing the log files from the emprereqkit.
  • 22. Manageability22 Session # 864Verify that all default plug-ins are selected as seen in figure 20 below. Only select plug-ins which are already available anddownloaded into a location accessible by the OMS.Figure 20 – Plug-in Deployment
  • 23. Manageability23 Session # 864Provide a connect descriptor for the old repository database and the password for the SYSMAN user on the pre-12crepository. You may locate the repository connection information on the pre-12c OMS server by checking the$OMS_HOME/sysman/config/emoms.properties file for the oracle.sysman.eml.emdRepConnectDescriptor value with leadingslashes removed (see Figure 21).Figure 21 – Provide Pre-12c Repository Database Connection InformationProvide the path for the datafile used for the JVM Diagnostic Data Tablespace.
  • 24. Manageability24 Session # 864Figure 22 – JVM Diagnostics Data Tablespace
  • 25. Manageability25 Session # 864Review and verify the ports to be used for the new OEM system (see Figure 23). You can also check the target system toverify if the ports are in use or being blocked by a firewall. In the case of the latter, you should arrange with your network orsecurity administrator to open up the required ports.Figure 23 – OMS Port SummaryReview the installation summary.
  • 26. Manageability26 Session # 864Figure 24 – Installation Summary ReviewAt the end of the installation you can verify whether if the OMS is running.[oracle@omshost bin]$ /u01/app/oracle/Middleware/oms/bin/emctl status oms -detailsOracle Enterprise Manager Cloud Control 12c Release 2Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved.Enter Enterprise Manager Root (SYSMAN) Password :Console Server Host : omshost.example.comHTTP Console Port : 7788HTTPS Console Port : 7802HTTP Upload Port : 4889HTTPS Upload Port : 4899EM Instance Home : /u01/app/oracle/Middleware/gc_inst/em/EMGC_OMS1OMS Log Directory Location : /u01/app/oracle/Middleware/gc_inst/em/EMGC_OMS1/sysman/logOMS is not configured with SLB or virtual hostnameAgent Upload is unlocked.OMS Console is unlocked.Active CA ID: 2Console URL: https://omshost.example.com:7802/emUpload URL: https://omshost.example.com:4899/empbs/uploadWLS Domain InformationDomain Name : GCDomain
  • 27. Manageability27 Session # 864Admin Server Host: omshost.example.comManaged Server InformationManaged Server Instance Name: EMGC_OMS1Managed Server Instance Host: omshost.example.comWebTier is UpOracle Management Server is UpGo the the Console URL shown in the output and login as an AdministratorFigure 25 – OEM 12c ConsoleYou are greeted with the License Agreement. Please Read and Accept the agreement to continue.Figure 26 – License Agreement
  • 28. Manageability28 Session # 864Choose your default Home Page.Figure 27 – Default Home Page Selection
  • 29. Manageability29 Session # 864You can preview home page before selecting it. This can be changed later under Username menu -> Select My Home.Figure 28 – Default Home Page Preview
  • 30. Manageability30 Session # 864Go to Pre-Upgrade Console in old EM to create a link between the old and new EM repository as shown in figure 29. Theconnect descriptor can be found by looking at Connect descriptor found inMW_HOME/gc_inst/em/EMGC_OMS1/emgc.propertiesThe link between the two repositories allows operations performed on the old repository to be propagated to the newrepository.Figure 29 – Create Repository LinkAgent DeploymentIn order for the targets to be monitored in the new environment it is required that the EM12c agents be deployed andconfigured to the targets. After that is done we will need to generate and sign off on health check reports before switchingover the agents to the new EM System. While this is being done all agents are still monitored up until the point of switcher.This stops the 10g agents and starts the 12c agent causing minimal disruption.From the Upgrade Console Home page click on the name of the phase to Generate Health Report of Deployed Agents if theagents have already been deployed. If not, click on the Deploy and Configure Agents link to first deploy the agent.Figure 120 – Agent Deployment
  • 31. Manageability31 Session # 864Follow the steps in the workflow to Generate Health Reports. Select agents, which have been deployed by either loading fromprevious operation or by searching. Next select the checkboxes for the agents and provide the software owner username andpassword as shown in figure 31 then click the submit button to create the HealthCheck job.Figure 31 – Generate Health Reports
  • 32. Manageability32 Session # 864Once submitted, you can click on the job name to view its status (see figure 32).Figure 32 – Health Report Job Status
  • 33. Manageability33 Session # 864Figure 33 – Health Report Job CompletedAfter job completes successfully check and sign off on health reports. Select agents that had the health checks job wascompleted (Health Check Status should be Pending Verification Report) then click on the “View and Verify Health CheckReports” button as shown in figure 34 below.Figure 34 – Health Check Report Verification
  • 34. Manageability34 Session # 864Check that the Ping Test is passed and that Broken Targets is zero. There should also be enough free space in the statedirectory. To view detailed information such as metrics and target properties, select the agent and click on the View DetailedReport button.Note: You can only view the detailed report of a single agent at a time.Figure 35 – Sign off Health ReportSelect the targets and click on the Verify and Sign Off button. Once done the User Verified column will contain green checksas shown below in figure 36.Figure 36 – Verify and Sign OffSwitch Agents.Before agent switchover, log into Enterprise Manager 12c Console and verify that the targets are in Pending Activation state asshown in figure 37 below.During switchover, the pre-12c agents will be shutdown and the 12c agents will be started.
  • 35. Manageability35 Session # 864Figure 37 – Targets in Pending Activation State in EM 12c Console
  • 36. Manageability36 Session # 864From the Upgrade Console in the pre-12c OEM, add the targets that you want to switch over. You can either add targetsmanually or load targets from a previous operation.Figure 38 – Agent SwitchoverSelect the targets and click on the Submit button to submit the agent switchover job (see figure 39).Note: If you have an environment with many agents (greater than 100) you may want to consider doing the switchover inbatches. For example, you could switchover non-production agents first and validate that they are working correctly firstbefore doing production agents.
  • 37. Manageability37 Session # 864Figure 39 – Agent Switchover Job SubmittedClicking on the job name will allow you to view the status of the job.Figure 40 – Switchover Job Activity
  • 38. Manageability38 Session # 864Switched over agents now appear up and running in the OEM 12c Console as seen in figure 41.Figure 41 – Switched Over TargetsThese now appear in 10g EM as unreachable.Figure 42 – Targets Unreachable in Pre-12c OEM ConsolePost UpgradeStop the OCM Scheduler configured in the OMS home.oemhost1[emrep]-/home/oracle >export ORACLE_HOME=$OMS_HOMEoemhost1[emrep]-/home/oracle >$ORACLE_HOME/ccr/bin/emCCR stopOracle Configuration Manager - Release: 10.3.7.0.0 - Production
  • 39. Manageability39 Session # 864Copyright (c) 2005, 2012, Oracle and/or its affiliates. All rights reserved.------------------------------------------------------------------Oracle Configuration Manager Stopped...Delete Obsolete TargetsThe following targets need to be deleted manually.• EM Website• EM Website System• Oracle Application Server target of 10g OMS ORACLE HOME consisting of:• Oracle Application Server• OC4J• Oracle HTTP Server• Web CacheGo to the All Targets page, right-click on the target name, select Target Setup -> Remove Target. Repeat the process for eachttarget to be removed.Figure 43 – Delete Obsolete TargetsBy default Enterprise Manager 12c enables default incident Rule Sets. These may generate a lot of unnecessary alerts in yourenvironment. Disable the default Incident Rulesets by clicking on Setup -> Incidents -> Incident Rules.Figure 44 – Incident Rule Sets
  • 40. Manageability40 Session # 864Select the Incident management Ruleset for all targets. Click on Actions and choose Disable from the drop-down menu asshown in figure 46.Figure 46 – Disable Default Incident RulesYou may get a pop-up message such as shown in figure 47. Click OK. The Ruleset will be disabled.Figure 47 – Information Pop-up After Disabling default Incident management Ruleset
  • 41. Manageability41 Session # 864Verify that the Enabled column has been changed to “No”.Perform Post-Upgrade Tasks from within the OEM 12c Console. Go to Setup -> Manage Cloud Control ->Post UpgradeTasks.Figure 48 – Post Upgrade ConsoleDeferred Data Migration• Data is migrated from the old EM system format the 12c format. A job is automatically submitted that runs in thebackground after the EM system is up and running.• The time taken to migrate data depends on the amount of data available in your old EM. Critical data is migrated first.• Historical data is migrated after EM Cloud control is functioning.Figure 49 – Deferred Data Migration JobsAccrued Data MigrationAccrued Data is data that has been collected on the agents between the repository backup and agent switchover. To enablethis data to be migrated, the ADMP jobs will automatically run if not disabled. You can also manually submit the ADMP joband track its status from the screen as shown in figure 50 below.
  • 42. Manageability42 Session # 864Figure 50 – Accrued Data Migration JobsView Diff ReportsIf any agents are added or removed from the old EM they will be shown in the Diff Report as shown in figure 51. Also anyadded jobs or Software Library entities will be displayed.Figure 51 – Diff ReportsOnce agents have been successfully migrated and validated, they can be removed by using the Sign Off tab in the PostUpgrade Console.All jobs, reports, user-defined metrics (metric extensions) remained in tact. Also notifications, rules, and monitoring templatescontinued to work in the new environment.Figure 52 below compares the custom reports in the EM 12c environment on the left with the EM 10g environment on theright.
  • 43. Manageability43 Session # 864Figure 52 – Reports Comparison in OEM 10g and OEM 12cSummaryWe have seen how to perform a step-by-step migration and upgrade of Enterprise Manager Grid Control 10g environment toEnterprise Manager Cloud Control 12c environment involving a database upgrade and platform migration. The EnterpriseManager Console provides the workflow to accomplish this, which resulted in near zero downtime. During the entireworkflow, all targets were still being managed and monitored by either the old EM before switchover or the new EM after theswitchover.
  • 44. Manageability44 Session # 864AppendicesAppendix A – Repository Backup using Data Pump1. Copy emkey to repository before taking backupa. $OMS_HOME/bin/emctl config emkey -copy_to_repos -sysman_pwd <password>Oracle Enterprise Manager 10g Release 5 Grid ControlCopyright (c) 1996, 2009 Oracle Corporation. All rights reserved.The Em Key is already present in the Management Repository.b. Verify using emctl status emkey[oemhost1]-/u02/orastage/em12c >$OMS_HOME/bin/emctl status emkeyOracle Enterprise Manager 10g Release 5 Grid ControlCopyright (c) 1996, 2009 Oracle Corporation. All rights reserved.Please enter repository password:The Em Key is configured properly, but is not secure. Secure the Em Key by running "emctl config emkey -remove_from_repos".To verify if the emkey is copied properly, log in to the repository as sys user and run the following sql command:SQL> select count(*) from MGMT_REPOS_TIME_COEFFICIENT;COUNT(*)----------1(If the count is 1, then the emkey is copied.)2. Use Datapump export/import method to migrate repository from 11gR1 database on AIX to 11gR2 database on RHEL 5as described in MOS note: 388090.13. Remove EM Grid Control or DB Control repository from new target repository database if one exists.To remove an existing EM Grid Control repository from the target database use RepManager utility to remove the objects fromthe database and drop the repository.$oemhost01>-$OMS_HOME/sysman/admin/emdrep/bin/RepManager dbhost1 1521 emrep -sys_password password-action dropEnter repository user name : sysmanGetting temporary tablespace from database...Found temporary tablespace: TEMPChecking SYS Credentials ... rem error switchOK.rem error switchDropping the repository..Checking for Repos User ... Exists.Repos User exists..Clearing EM Contexts ... OK.Dropping EM users ...
  • 45. Manageability45 Session # 864Done.Dropping Repos User ... Done.Dropping Roles/Synonymns/Tablespaces ... Done.Dropped Repository Successfully.The output of the SQL commands below when run in the target repository as a DBA user should not return any rows. If so,you may need to contact Oracle Support.select username,account_status from dba_users where username in (SYSMAN,SYSMAN_MDS,MGMT_VIEW,SYSMAN_BIP,SYSMAN_APM,BIP,SYSMAN_OPSS,SYSMAN_RO) ;select owner,synonym_name from dba_synonyms where table_owner in (SYSMAN,SYSMAN_MDS,MGMT_VIEW,SYSMAN_BIP,SYSMAN_APM,BIP,SYSMAN_OPSS,SYSMAN_RO) ;select tablespace_name from dba_tablespaces where tablespace_name like MGMT%;select comp_name from SCHEMA_VERSION_REGISTRY;NOTE: Not all objects dropped:See MOS NOTE: 12c Cloud Control Repository: RepManager Dropall Command Fails To Drop all the RepositoryObjects [ID 1365820.1]To remove DB Control, use the emca utility from the database home.Appendix B – EM Prerequisite Kithttp://docs.oracle.com/cd/E24628_01/install.121/e22624/appdx_about_emprereqkit.htm#sthref430The Enterprise Manager installer runs pre-requisite checks on the repository automatically during installation or upgrade. Itcan also fix some pre-requisites checks that fail before running the installer and revert changes afterwards. E.g.job_queue_process will be changed to 0 before installation/upgrade and reset back to original value after installation.You can manually run the pre-requisite checks using the empreqkit command line.[oracle@oemhost1 12.1.0.2]$ install/requisites/bin/emprereqkit -executionType upgrade -prerequisiteXMLLoc/orasource/Linux/EM/12.1.0.2/install/requisites/list -connectString"(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=dbrephost1)(PORT=1521)))(CONNECT_DATA=(SID=emrep1)))" -dbUser SYS -dbPassword password -dbRole sysdba -showPrereqsChecking Temp space: must be greater than 400 MB. Actual 1922 MB PassedChecking swap space: must be greater than 150 MB. Actual 3287 MB PassedPreparing to Bootstrap Please wait ...BootStrap To /tmp/emprereqkit_091712161748_BS CompletedOracle Enterprise Manager Cloud Control 12c Release 12.1.0.2.0Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.Running EMPrereqKit ............Result of prerequisite list, for scenario upgrade :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------Prerequisite Name | Status | Corrective Action Status | PostCorrective Action Status--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
  • 46. Manageability46 Session # 864Check for invalid objects in the EM repository | NE | NA | NA|Check the CBO stats gathering job | NE | NE | NE|Check nls_length_semantics parameter | NE | NA | NA|Check for the EM Target policy | NE | NA | NA|Check for automatic UNDO management | NE | NA | NA|Ensure that the undo tablespace has at least one dataf| NE | NA | NA|Check for a DBA policy on SYSMAN | NE | NA | NA|Check DBA jobs running | NE | NA | NA|Ensure that PK, FK constraints are not disabled | NE | NA | NA|Ensure that all EM AQ queue tables are enabled for enq| NE | NA | NA|Ensure that EM triggers are not disabled | NE | NA | NA|Ensure that the SYSTEM tablespace has at least one dat| NE | NA | NA|Ensure that the EM tablespace has at least one datafil| NE | NA | NA|Ensure that the Oracle partitioning option is installe| NE | NA | NA|Check remote_login_passwordfile parameter | NE | NA | NA|Check emkey is copied to the repository | NE | NA | NA|Check policies for MGMT_JOB table | NE | NA | NA|Check EM_USER_CONTEXT is present in the repository | NE | NA | NA|Check Abnormal condition in the Audit Master Table | NE | NA | NA|Check EXEMPT ACCESS POLICY is grants | NE | NA | NA|Check max_enabled_roles init parameter | NE | NA | NA|Check execute privilege on DBMS_RANDOM | NE | NA | NA|Check that no PAF executions are scheduled or running.| NE | NA | NA|Check if all Agents are secured with latest CA | NE | NA | NA|Check for the global stale percent | NE | NA | NA|Check if SYSMAN account is locked | NE | NA | NA|Check if MGMT_VIEW account is locked | NE | NA | NA|Check if ORACLE_OCM account is locked | NE | NA | NA|Check if SYSMAN schema is present for upgrade | NE | NA | NA|
  • 47. Manageability47 Session # 864Check Policies for MGMT_CORRECTIVE_ACTION table | NE | NA | NA|Check Fine-grained access control option | NE | NA | NA|Check the Connector Config Table | NE | NA | NA|Check if Snapshot logs are created on EM tables | NE | NA | NA|Check if required DBMS packages are valid | NE | NA | NA|Check the global_name when global_names enabled | NE | NA | NA|Check the global_name when global_names disabled | NE | NA | NA|Check the existence of current availability indexes | NE | NA | NA|Check optimizer sql plan baseline capture. | NE | NA | NA|Check if temporary tablespace group TEMP exist | NE | NA | NA|Check for job type uniqueness in MGMT_JOB_TYPE_INFO. | NE | NA | NA|Check the processes instance parameter value | NE | NA | NA|Check the memory_target instance parameter value. | NE | NA | NA|Check the workarea_size_policy instance parameter valu| NE | NA | NA|Check the session_cached_cursors instance parameter va| NE | NA | NA|Check the job_queue_processes instance parameter value| NE | NE | NE|Check the open_cursors instance parameter value. | NE | NA | NA|Check the log_buffer instance parameter value. | NE | NA | NA|Check the shared_pool_size instance parameter value. | NE | NA | NA|Check the db_cache_size instance parameter value. | NE | NA | NA|Check the large_pool_size instance parameter value. | NE | NA | NA|Check the java_pool_size instance parameter value. | NE | NA | NA|Check the streams_pool_size instance parameter value. | NE | NA | NA|Check the timed_statistics instance parameter value. | NE | NA | NA|Check the statistics_level instance parameter value. | NE | NA | NA|Check the redo log size. | NE | NA | NA|Check the compatible instance parameter value. | NE | NA | NA|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------NE = Not Executed NA = Not Applicable--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
  • 48. Manageability48 Session # 864For more details, check the log file at /orasource/Linux/EM/12.1.0.2/prerequisiteResults/log//LATEST/Run and Execute prerequisites.[oracle@oemhost1 12.1.0.2]$ install/requisites/bin/emprereqkit -executionType upgrade -prerequisiteXMLLoc/orasource/Linux/EM/12.1.0.2/install/requisites/list -connectString"(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=dbrephost1)(PORT=1521)))(CONNECT_DATA=(SID=emrep1)))" -dbUser SYS -dbPassword password -dbRole sysdba -runPrerequisitesChecking Temp space: must be greater than 400 MB. Actual 1922 MB PassedChecking swap space: must be greater than 150 MB. Actual 3287 MB PassedPreparing to Bootstrap Please wait ...BootStrap To /tmp/emprereqkit_091712162201_BS CompletedOracle Enterprise Manager Cloud Control 12c Release 12.1.0.2.0Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.Running EMPrereqKit ............Result of prerequisite-check , for scenario upgrade :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------Prerequisite Name | Status | Corrective Action |Recommendation--------------------------------------------------------------------------------------------------------------------------------------------------------------------------Check for invalid objects in the EM repository | Fail | MANUAL |Compile all invalid objects in the EM reposiCheck the CBO stats gathering job | Fail | disable_stats_gather_job |Disable the stats gathering jobCheck nls_length_semantics parameter | Pass | NA |NACheck for the EM Target policy | Pass | NA |NACheck for automatic UNDO management | Pass | NA |NAEnsure that the undo tablespace has at least one dataf| Pass | NA |NACheck for a DBA policy on SYSMAN | Pass | NA |NACheck DBA jobs running | Pass | NA |NAEnsure that PK, FK constraints are not disabled | Pass | NA |NAEnsure that all EM AQ queue tables are enabled for enq| Fail | MANUAL |Enable all EM AQ queue tables for both enqueEnsure that EM triggers are not disabled | Pass | NA |NAEnsure that the SYSTEM tablespace has at least one dat| Pass | NA |NAEnsure that the EM tablespace has at least one datafil| Pass | NA |NAEnsure that the Oracle partitioning option is installe| Pass | NA |NACheck remote_login_passwordfile parameter | Pass | NA |NA
  • 49. Manageability49 Session # 864Check emkey is copied to the repository | Pass | NA |NACheck policies for MGMT_JOB table | Pass | NA |NACheck EM_USER_CONTEXT is present in the repository | Pass | NA |NACheck Abnormal condition in the Audit Master Table | Pass | NA |NACheck EXEMPT ACCESS POLICY is grants | Pass | NA |NACheck max_enabled_roles init parameter | Pass | NA |NACheck execute privilege on DBMS_RANDOM | Pass | NA |NACheck that no PAF executions are scheduled or running.| Pass | NA |NACheck if all Agents are secured with latest CA | Pass | NA |NACheck for the global stale percent | Pass | NA |NACheck if SYSMAN account is locked | Pass | NA |NACheck if MGMT_VIEW account is locked | Pass | NA |NACheck if ORACLE_OCM account is locked | Fail | MANUAL |ORACLE_OCM account should be unlocked and unCheck if SYSMAN schema is present for upgrade | Pass | NA |NACheck Policies for MGMT_CORRECTIVE_ACTION table | Pass | NA |NACheck Fine-grained access control option | Pass | NA |NACheck the Connector Config Table | Pass | NA |NACheck if Snapshot logs are created on EM tables | Pass | NA |NACheck if required DBMS packages are valid | Pass | NA |NACheck the global_name when global_names enabled | Pass | NA |NACheck the global_name when global_names disabled | Pass | NA |NACheck the existence of current availability indexes | Pass | NA |NACheck optimizer sql plan baseline capture. | Pass | NA |NACheck if temporary tablespace group TEMP exist | Pass | NA |NACheck for job type uniqueness in MGMT_JOB_TYPE_INFO. | Pass | NA |NACheck the processes instance parameter value | Fail | MANUAL |The processes instance parameter needs to beCheck the memory_target instance parameter value. | Pass | NA |NACheck the workarea_size_policy instance parameter valu| Pass | NA |NACheck the session_cached_cursors instance parameter va| Pass | NA |NA
  • 50. Manageability50 Session # 864Check the job_queue_processes instance parameter value| Pass | NA |NACheck the open_cursors instance parameter value. | Pass | NA |NACheck the log_buffer instance parameter value. | Pass | NA |NACheck the shared_pool_size instance parameter value. | Pass | NA |NACheck the db_cache_size instance parameter value. | Pass | NA |NACheck the large_pool_size instance parameter value. | Pass | NA |NACheck the java_pool_size instance parameter value. | Pass | NA |NACheck the streams_pool_size instance parameter value. | Pass | NA |NACheck the timed_statistics instance parameter value. | Pass | NA |NACheck the statistics_level instance parameter value. | Pass | NA |NACheck the redo log size. | Fail | MANUAL |The size of the EM database instance shouldCheck the compatible instance parameter value. | Pass | NA |NA--------------------------------------------------------------------------------------------------------------------------------------------------------------------------NE = Not Executed NA = Not Applicable--------------------------------------------------------------------------------------------------------------------------------------------------------------------------For more details, check the log file at /orasource/Linux/EM/12.1.0.2/prerequisiteResults/log//LATEST/ReferencesOTN Enterprise Manager PageAnnouncing Enterprise Manager Cloud Control 12c Release 12.1.0.1 Bundle Patch 1(BP1) and 12.1.0.2 Plug-ins [ID1395505.1]Upgrade Advisor: Enterprise Manager 2-System Upgrade from 10.2.0.5 or from 11.1.0.1 to 12.1.0.1 [ID 327.1]EM 12c: Upgrading to Enterprise Manager Cloud Control 12.1.0.1 on Linux x86_64 with the 2-System Method [ID1367919.1]Grid Control Repository: Steps for Cross Platform Migration of the 10g Grid Control Repository [ID 388090.1]EM12c R2: How to Upgrade to EM 12c R2 - Two System Method [ID 1363162.1]EM 12c R2: How to Apply Upgrade Console Patch for Upgrading to EM 12.1.0.2 [ID 1362537.1]Grid Control Repository: How to Recompile Invalid SYSMAN Objects? [ID 372706.1]

×