Upgrading using 1-system upgrade approach (on a different host)

Transcription

1 Upgrading using 1-system upgrade approach (on a different host) This approach enables to install Enterprise Manager Cloud Control on a host different from where the existing Enterprise Manager is running. It is similar to the 2-system upgrade approach, but unlike the 2-system upgrade approach, this approach upgrades the Management Repository in the existing database itself. Since only one Enterprise Manager System exists at any point, there is a reasonable downtime involved. Also this approach is useful to split the load of Oracle Management Server and Repository. Getting ready Before you start, ensure the server where previous version of OEM is running and is connected to the network and an SSH or telnet client is available. Also make sure you have access to the Unix server as root user, owner of Oracle repository database, and OEM. The following environment details are used to demonstrate 1-system upgrade approach in this example: ff Operating system: Oracle Enterprise Linux 5 Update 3 ff ff ff ff Repository Database 11g release 2 is installed at /dboracle/product/11.2.0/ dbhome_1 as a repository owner Oracle Grid Control 11g release 1 is installed at /u01/app/middleware/oms11g as an OEM owner Oracle Grid Control 11g Agent is installed at /u01/app/middleware/agent11g as an OEM owner Oracle Weblogic server is installed at /u01/app/middleware/ wlserver_10.3 as an OEM owner The following details are required to upgrade the host: ff Operating system: Oracle Enterprise Linux 5 Update 3

2 How to do it... To identify and provide information about the host where you plan to install Enterprise Manager Cloud Control, follow these steps: 1. Add target server host details in the /etc/hosts file of the existing OEM 11g server. *** xx servername.starfleet.com servername 2. Click on the Deployments tab in the grid control. 3. On the Deployments page, in the Upgrade section, click on the Enterprise Manager 12c Upgrade Console link. 2

3 4. On the Upgrade Console page, in the Select Upgrade Type section click on the 1-System on a Different Host option. Recipe_2 Enterprise Manager Grid Control refreshes the page and displays a table with a list of tasks required to perform for the 1-system upgrade on a different host approach. 5. In the Preupgrade Steps section from the table, click on Identify Host and Port for New Enterprise Manager System. 6. Enter details in the OMS HTTPS Upload Port and OMS HTTP upload port fields on the Identify Host and Port for New Enterprise Manager System screen. 7. Click on Save. Enterprise Manager Grid Control saves the information provided. 3

4 To Install plugins and Oracle Management Agent 12c using Manage Software option perform following steps: 1. Provide the location where the Agent software and the related plugin software are present, on the Upgrade console screen. The path shared in example is /u01/software/preupgrade/agentsplugin/. 2. Click on Validate. 3. Wait until the upload activities are completed. Every Oracle software product has an entry in the inventory.xml file, which is present in the orainventory directory. If a Management Agent is registered with the central inventory, then it is a Management Agent with valid inventory. To identify the Management Agent with a valid inventory, perform the following steps: 1. Click on the Deployments tab in the grid control. 2. Click on the Enterprise Manager 12c Upgrade Console link in the Upgrade section. 4

5 3. In the Agent Upgrade Status section, check the number displayed against Agents with Valid Inventory field. The agent with a valid inventory count in the current example is 1. There are no agents with an invalid inventory. To check the upgradability status of the Management Agents, perform the following steps: 1. Click on the Deployments tab in the grid control. 2. On the Deployments page, in the Upgrade section, click Enterprise Manager 12c Upgrade Console. 3. On the Upgrade Console page, in the Preupgrade Steps section, from the table, click on Manage Software. 4. On the Manage Software page, view the Agent Upgradability pie chart. The pie chart graphically shows the upgradeable agent count adjacent to Pie chart. In this example, there is one upgradebale agent and 13 upgrade targets. 5

6 To Deploy and configure the software binaries of Oracle Management Agent 12c perform following steps: 1. Click on the Deployments tab in the grid control. 2. Click on the Enterprise Manager 12c Upgrade Console link in the Upgrade section. 3. Select the 1-System on a Different Host option in the Select Upgrade Type section. 4. Click on Deploy and Configure Agents link. 5. Enter the distinct Operation Name. 6. In the Select Operation Type section, select the operation type. In this example, both the options Deploy Agent and Plug-In Software and Configure Agent and Plug-In Software are selected. 6

7 7. Select the Platform type as applicable in the Search Agents section, and click on Search, which will discover the Management Agent in the environment. 8. In the Select Agent section, review the Agent Base Directory and the Agent Instance Home path, and amend these settings if required. Select the required agent. 9. The Override Oracle Home Preferred Credentials option is chosen by default in the Agent Credentials section. Enter the user credentials, which can be used for all Oracle homes. 10. Click on Next. 7

8 11. Under the Root Credentials section of the Upgrade Console screen, provide the User Name and Password to allow execution of the root.sh Unix script at the end of the agent deployment. 12. Click on Submit. 13. Click on the Job Submitted hyperlink to view the progress of the agent's installation. It will take some time. 8

9 Newly deployed and configured Oracle Management Agent 12c, generates a report to check the health and readiness of the deployed management agents so that any issues with the deployment can be verified beforehand. To generate a health report of deployed Management Agents perform the following steps: 1. Click on the Deployments tab in the grid control. 2. Click on the Enterprise Manager 12c Upgrade Console link in the Upgrade section. 3. Click on the Generate Health Report of Deployed Agents link in the Agent Upgrade Steps section. 4. Enter the distinct Operation Name. 5. In the Search Agents section, select the Platform type as applicable and click on Search, which will discover the Management Agent in the environment. 6. In the Select Agent section, select the required Agent. 9

10 7. Override Oracle Home Preferred Credentials is chosen by default in the Agent Credentials section. Enter the user credentials, which can be used for all Oracle homes. 8. Click on Submit. 9. Click on the Job Submitted hyperlink to view the progress of the health check report generation job. 10

11 To verify and sign off the health report, perform follow these steps: 1. Click on the Deployments tab in the grid control. 2. Click on the Enterprise Manager 12c Upgrade Console link in the Upgrade section. 3. Click on the Sign Off Health Report for Deployed Agents link in the Agent Upgrade Steps section. 4. Select the Management Agent from the Sign Off Health Report of Deployed Agents page. 5. Click on the Verify and Sign Off Report button. The switch over of the existing earlier release Oracle Management Agent to the newly deployed Oracle Management Agents need to be performed sothat they can communicate with Enterprise manager 12c Clound Control. To switch over to Oracle Management Agent 12c perform the following steps: 1. Click on the Deployments tab on the Grid Control 11g screen. 2. Click on the Enterprise Manager 12c Upgrade Console link in the Upgrade section. 3. In the Agent Upgrade Steps section, click on the Switch Agents link. 4. Enter a distinct name for the Switch Agents operation in the Provide Inputs section. 5. In the Search Agents section, select a Platform type and click on Search. The search result discovered Management Agents in the environment. 6. Select the agent under the Select Agent section. 7. The Override Oracle Home Preferred Credentials option is chosen by default in the Agent Credentials section. Enter the user credentials, which can be used for all Oracle homes. 8. Click on Submit. 11

12 9. Click on the Job Submitted hyperlink to view the progress of switching agents from 11g to 12c. To Upgrade Oracle Management Service and Oracle Management Repository perform the following steps: 1. Ensure that the prerequisites of Oracle Enterprise Manager 12c are met. Refer to Chapter 1, Prerequisites of OEM 12c Installation for details. 2. Stop all of the scheduled deployment tasks that are running in the existing enterprise manager system. 3. Copy emkey from the OMS to the Management Repository. The following command needs to be used for upgrading from the Enterprise Manager 11g grid control: $<OMS_HOME>/bin/emctl config emkey -copy_to_repos_from_file -repos_host <repository_host> -repos_port <port> -repos_sid <sid> -repos_user <username> [-repos_pwd <pwd>] [-admin_pwd <pwd>] -emkey_file <OMS_HOME>/ sysman/config/emkey.ora $ export OMS_HOME=/u01/app/Middleware/oms11g $ $OMS_HOME/bin/emctl config emkey -copy_to_repos_from_file -repos_host oem_repository_server -repos_port repos_sid oem -repos_user sysman -repos_pwd xxxxx -emkey_file $OMS_HOME/sysman/ config/emkey.ora 12

13 To upgrade the existing Oracle Management Service (OMS) with 1-system on a different host approach, follow these steps: 1. On the remote host, install only the software binaries of Enterprise Manager Cloud Control. 2. Extract the following OEM 12c software on a staging directroy on the server to invoke runinstaller. The following example is referring to OEM 12c release 1 software. V zip V zip V zip 3. Invoke the Enterprise Manager Cloud Control Installation Wizard on the host using the following command: $ export TEMP=/u01/tmp $ runinstaller -pluginlocation /u01/software/preupgrade/ agentsplugin 4. Deselect I wish to receive security updates via My Oracle Support. 5. Click on Next. 6. Click on Yes on the You have not provided an address. Do you wish to remain uninformed of critical security issues in your configuration screen and then select Skip. 7. Click on Next. 8. Select Upgrade an existing Enterprise manager system. 9. Select Install Software only. 13

14 10. Enter the absolute path in the Middleware Home Location. 14

15 11. Click on Next. 12. Click on Next. 13. Review the information provided and Click on Install. 14. Execute the following script as root when prompted during the installation process: #. /u01/app/middleware/oms/allroot.sh 15. Click on OK and then click on Close. 15

16 To upgrade existing Oracle Management Repository (Management Repository) with 1-system upgrade on a different host approach, follow these steps: 1. On the host where your existing release of Enterprise Manager is running, stop the OMS. To do so, run the following command from the OMS home: $ /u01/app/middleware/oms11g/bin/emctl stop oms -all 2. On the remote host where you installed the software binaries of Enterprise Manager Cloud Control, set the environment variable: ORACLE_HOME to the OMS home, and MW_HOME to the middleware home. $ export ORACLE_HOME=/u01/app/Middleware/oms $ export MW_HOME=/u01/app/Middleware 3. Run the Management Repository related prerequisite checks to verify if the Oracle Management Repository (Management Repository) is ready for upgrade. $ORACLE_HOME/install/requisites/bin/emprereqkit -executiontype upgrade -prerequisitexmlloc <prereq_xml_location> -prereqresultloc <prereq_result_location> -connectstring "(DESCRIPTION=(ADDRESS_ LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=<REPOSITORY_HOST>) (PORT=<PORT>)))(CONNECT_DATA=(SID=<REPOSITORY_SID>)))" -dbuser SYS -dbpassword <db_password> -reposuser sysman -repospassword <repo_ user_password> -dbrole sysdba -runprerequisites $ mkdir -p /u01/app/middleware/oms/prerequisiteresults $ORACLE_HOME/install/requisites/bin/emprereqkit -executiontype upgrade -prerequisitexmlloc $ORACLE_HOME/install/requisites/ list -prereqresultloc $ORACLE_HOME/prerequisiteResults -connectstring "(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP) (HOST=nclvoem03.starfleet.com)(PORT=1521)))(CONNECT_ DATA=(SID=oem)))" -dbuser SYS -dbpassword xxxxx -reposuser sysman -repospassword xxxxx -dbrole sysdba -runprerequisites For more details, check the log file at /u01/app/middleware/oms/ prerequisiteresults/log//latest/. 16

17 4. Some of Management Repository related prerequisite checks fail, run post-corrective actions to automatically correct the issues: $ORACLE_HOME/install/requisites/bin/emprereqkit-executionType upgrade -prerequisitexmlloc <prereq_xml_location> -prereqresultloc <prereq_result_location>-connectstring "(DESCRIPTION=(ADDRESS_ LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=<REPOSITORY_HOST>) (PORT=<PORT>)))(CONNECT_DATA=(SID=<REPOSITORY_SID>)))" -dbuser SYS -dbpassword <db_password> -reposuser sysman -repospassword <repo_ user_password> -dbrole sysdba -usehistory runcorrectiveactions $ $ORACLE_HOME/install/requisites/bin/emprereqkit -executiontype upgrade -prerequisitexmlloc $ORACLE_HOME/install/requisites/ list -prereqresultloc $ORACLE_HOME/prerequisiteResults -connectstring "(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP) (HOST=nclvoem03.starfleet.com)(PORT=1521)))(CONNECT_ DATA=(SID=oem)))" -dbuser SYS -dbpassword xxxxxx -reposuser sysman -repospassword xxxxx -dbrole sysdba -usehistory -runcorrectiveactions For more details, check the log file at /u01/app/middleware/oms/ prerequisiteresults/log//latest/. 5. Connect to OEM repository rdbms database and run the following commands: SQL> grant execute on dbms_random to dbsnmp; Grant succeeded. SQL> grant execute on dbms_random to sysman; Grant succeeded. SQL> alter user ORACLE_OCM account unlock; User altered. 6. Run the plugin configuration assistant in the prerequisite mode: 7. Create an NFS mount of OMS 11g home, that is, /u01/app/middleware/oms11g to OMS 12c server so that OMS 11g home can be accessible to run the following command: $ORACLE_HOME/bin/pluginca -oraclehome $ORACLE_HOME -middlewarehome $MW_HOME -action prereqcheck -plugins <list_of_plugins> -oldoraclehome <old_oms_home> -installmode gcupgrade 17

18 8. List of plugins to be mentioned for the <pluginslist> argument is available in $ORACLE_HOME/sysman/install/plugins_installed.txt file. $ $ORACLE_HOME/bin/pluginca -oraclehome $ORACLE_HOME -middlewarehome $MW_HOME -action prereqcheck -plugins "oracle. sysman.db= ,oracle.sysman.xa= ,oracle. sysman.emas= ,oracle.sysman.mos= ,oracle. sysman.ssa= ,oracle.em.sehc= ,oracle.sysman. emfa= ,oracle.sysman.vt= " -oldoraclehome /u01/ app/middleware/oms11g -installmode gcupgrade pluginca - Plugin Configuration Tool Oracle Enterprise Manager 12c Release 1 Grid Control Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved. Completed Prereq check 9. Run the Management Repository related preupgrade checks. Execute the following command to perform preupgrade checks of Management Repository: $ORACLE_HOME/sysman/admin/emdrep/bin/RepManager connect "(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP) (HOST=<REPOSITORY_HOST> )(PORT=<PORT>)))(CONNECT_DATA=(SID=<REPOSITORY SID>)))" -action preupgrade -dbuser SYS dbpassword <db_password> -reposname sysman -repospassword < repo_user_password> mwhome $MW_HOME -mworahome $ORACLE_HOME -oraclehome $ORACLE_HOME $ORACLE_HOME/sysman/admin/emdrep/bin/RepManager -connect "(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP) (HOST=nclvoem03.starfleet.com )(PORT=1521)))(CONNECT_DATA=(SID=oem)))" -action preupgrade -dbuser SYS -dbpassword xxxxx -reposname sysman -repospassword xxxxx -mwhome $MW_HOME -mworahome $ORACLE_HOME -oraclehome $ORACLE_HOME Upgrade the Management Repository. Execute the following command to upgrade the Management Repository: $ORACLE_HOME/sysman/admin/emdrep/bin/RepManager connect "(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP) (HOST=<REPOSITORY_HOST> 18

19 )(PORT=<PORT>)))(CONNECT_DATA=(SID=<REPOSITORY SID>)))" -action upgrade -dbuser SYS dbpassword <db_password> -reposname sysman -repospassword < repo_user_password> -mwhome $MW_HOME -mworahome $ORACLE_HOME -oraclehome $ORACLE_HOME $ORACLE_HOME/sysman/admin/emdrep/bin/RepManager connect "(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP) (HOST=nclvoem03.starfleet.com )(PORT=1521)))(CONNECT_DATA=(SID=oem)))" -action upgrade -dbuser SYS -dbpassword next0ne2 -reposname sysman -repospassword sysman11 -mwhome $MW_HOME -mworahome $ORACLE_HOME -oraclehome $ORACLE_HOME Percent Complete: 100. EM Repository Upgrade Configuration Success Repository Creation Utility - Create : Operation Completed Completed... exiting the thread... [Initializing the EM RCU Runner, Running the Schema Action, Schema Action Completed Successfully] 11. Revert the corrective actions that were automatically taken in the previous step. Execute the following command to revert the corrective actions taken before repository upgrade in the previous step: $ORACLE_HOME/install/requisites/bin/emprereqkit -executiontype upgrade -prerequisitexmlloc <prereq_xm_location> -prereqresultloc <prereq_result_location> -connectstring "(DESCRIPTION=(ADDRESS_ LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=<REPOSITORY_HOST> )(PORT=<PORT>)))(CONNECT_DATA=(SID=<REPOSITORY_SID>)))" -dbuser SYS -dbpassword <db_password> -reposuser sysman -repospassword <repo_user_password> -dbrole sysdba -usehistory runpostcorrectiveactions 19

20 $ $ORACLE_HOME/install/requisites/bin/emprereqkit -executiontype upgrade -prerequisitexmlloc $ORACLE_HOME/install/requisites/ list -prereqresultloc $ORACLE_HOME/prerequisiteResults -connectstring "(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP) (HOST=nclvoem03.starfleet.com)(PORT=1521)))(CONNECT_ DATA=(SID=oem)))" -dbuser SYS -dbpassword xxxxx -reposuser sysman -repospassword xxxxxx -dbrole sysdba -usehistory -runpostcorrectiveactions Oracle Enterprise Manager Cloud Control 12c Release Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved. 12. Create MDS schema in the Management Repository. Execute the following command to create MDS schema in the Management Repository: $ORACLE_HOME/perl/bin/perl $ORACLE_HOME/sysman/admin/emdrep/bin/ mdsschemamanager.pl -action=-createrepository -connectstring=<repository_ HOST>:<PORT>:<REPOSITORY_SID> -dbuser=sys -dbpassword=<db_ password> -mdspassword=<new_mds_user_password> -mwhome=$mw_home $ $ORACLE_HOME/perl/bin/perl $ORACLE_HOME/sysman/admin/ emdrep/bin/mdsschemamanager.pl -action=-createrepository -connectstring=nclvoem03.starfleet.com:1521:oem -dbuser=sys -dbpassword=xxxx -mdspassword=xxxxxx -mwhome=$mw_home 13. Create OPS schema in the Management Repository. Execute the following command to create OPS schema in the Management Repository: $ORACLE_HOME/sysman/admin/emdrep/bin/SecurityRepManager -action createrepository connectstring '(DESCRIPTION=(ADDRESS_ LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=<REPOSITORY_HOST>) (PORT=<PORT>)))(CONNECT_DATA=(SID=<REPOSITORY_SID>)))' -dbuser SYS -dbpassword <db_password> -schemaprefix sysman -schemapassword <sysman_user_password> -component opss $ $ORACLE_HOME/sysman/admin/emdrep/bin/SecurityRepManager -action createrepository -connectstring '(DESCRIPTION=(ADDRESS_ LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=nclvoem03.starfleet.com) (PORT=1521)))(CONNECT_DATA=(SID=oem)))' -dbuser SYS -dbpassword xxxxx -schemaprefix sysman -schemapassword xxxxxx -component opss Successfully created schema 20

21 14. Configure the OMS. 15. Create a response file with the following details: -AS_HOST=<hostname> -AS_USERNAME=<admin serverr username> -AS_HTTPS_PORT=<admin server https port> -MSPORT=<managed server http port> -MS_HTTPS_PORT=<managed server https port> -EM_INSTANCE_HOME=<MW_HOME/gc_inst by default> -EM_NODEMGR_PORT=<node manager https port> 16. Upgrade the OMS and Repository for 1-system on a different host approach. -WEBTIER_ORACLE_HOME=<MW_HOME/Oracle_WT> -REP_USER=SYSMAN -REP_CONN_STR=<connection string> -NM_USER=<node manager username> -EM_DOMAIN_NAME=<domain name> -EM_INSTANCE_HOST=<hostname where the instance home will reside> -EM_UPLOAD_PORT=<upload http port> -EM_UPLOAD_HTTPS_PORT=<upload https port> -EM_CONSOLE_PORT=<console http port> -EM_CONSOLE_HTTPS_PORT=<console https port> $ cat /u01/app/middleware/oms/configure_oms.rsp -AS_HOST=nclvoem04.starfleet.com -AS_USERNAME=weblogic -AS_HTTPS_PORT=7101 -MSPORT=7201 -MS_HTTPS_PORT=7301 -EM_INSTANCE_HOME=/u01/app/Middleware/gc_inst -EM_NODEMGR_PORT=7401 -WEBTIER_ORACLE_HOME=/u01/app/Middleware/Oracle_WT -REP_USER=SYSMAN -REP_CONN_STR=(DESCRIPTION\=(ADDRESS_ LIST\=(ADDRESS\=(PROTOCOL\=TCP)(HOST\=nclvoem03.starfleet.com) (PORT\=1521)))(CONNECT_DATA\=(SID\=oem))) -NM_USER=nodemanager -EM_DOMAIN_NAME=GCDomain -EM_INSTANCE_HOST=nclvoem04.starfleet.com -EM_UPLOAD_PORT=4889 -EM_UPLOAD_HTTPS_PORT=1159 -EM_CONSOLE_PORT=7788 -EM_CONSOLE_HTTPS_PORT=

22 17. Execute the following command to configure OMS: $ORACLE_HOME/bin/omsca NEW -RESPONSE_FILE <absolute_location_to_ response_file> -lock_console -lock_upload -CONFIGURE_REPEATER true nostart $ $ORACLE_HOME/bin/omsca NEW -RESPONSE_FILE /u01/app/middleware/ oms/configure_oms.rsp -lock_console -lock_upload -CONFIGURE_ REPEATER true -nostart Oracle Enterprise Manager 11g Release 1 Grid Control Copyright (c) 2009, 2010, Oracle. All rights reserved. Enter Admin Server user password: Confirm Password: Enter Node Manager Password: Confirm Password: Enter Repository database user password: Enter Agent Registration password: Confirm Password:. EM configuration completed successfully. EM URL is: 18. Configure the plugins. Verify list of Plug-ins to configure from $ORACLE_HOME/sysman/install/plugins_installed.txt Ensure OMS11G is accessible thorough NFS mount point. Execute below command to configure listed plug-ins $ORACLE_HOME/bin/pluginca -oraclehome $ORACLE_HOME -middlewarehome $MW_HOME -action deploy plugins <pluginlist> -oldoraclehome <old_ oms_home> -installmode gcupgrade $ more $ORACLE_HOME/sysman/install/plugins_installed.txt $ $ORACLE_HOME/bin/pluginca -oraclehome $ORACLE_HOME -middlewarehome $MW_HOME -action deploy -plugins "oracle. sysman.db= ,oracle.sysman.xa= ,oracle. sysman.emas= ,oracle.sysman.mos= ,oracle. sysman.ssa= ,oracle.em.sehc= ,oracle.sysman. emfa= ,oracle.sysman.vt= " -oldoraclehome /u01/ app/middleware/oms11g -installmode gcupgrade 22

23 pluginca - Plugin Configuration Tool Oracle Enterprise Manager 12c Release 1 Grid Control Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved. 19. Migrate the plugin inventory from old tables to the new Plugin Lifecycle Application (PLA) inventory table. 20. To do so, log in to the upgraded Management Repository as SYSMAN user and run the following SQL query: SET SERVEROUTPUT ON SIZE DECLARE PLUGIN_BITS_TYPE CONSTANT NUMBER := 1; DISCOVERY_BITS_TYPE CONSTANT NUMBER := 2; AGENT_DEST_TYPE CONSTANT NUMBER := 3; err_num NUMBER; err_msg VARCHAR2(100); BEGIN FOR rec in ( select plugin_id, plugin_version, target_guid, plugin_home, plugin_type from PRE_UPGC_DEP_PLUGINS ) LOOP BEGIN IF rec.plugin_type = 'discoveryplugin' THEN EM_PLUGIN_INVENTORY.add_to_plugin_inventory(rec.plugin_id, rec. plugin_version, DISCOVERY_BITS_TYPE, AGENT_DEST_TYPE, rec.target_guid, rec.plugin_ home); ELSE EM_PLUGIN_INVENTORY.add_to_plugin_inventory(rec.plugin_id, rec. plugin_version, PLUGIN_BITS_TYPE, AGENT_DEST_TYPE, rec.target_guid, rec.plugin_ home); END IF; EXCEPTION WHEN DUP_VAL_ON_INDEX THEN -- ALTER SESSION CLOSE DATABASE LINK PREUPGTO_NG_LINK; DBMS_OUTPUT.PUT_LINE('Records already exists.'); WHEN OTHERS THEN -- ALTER SESSION CLOSE DATABASE LINK PREUPGTO_NG_LINK; err_num := SQLCODE; err_msg := SUBSTR(SQLERRM, 1, 100); 23

24 DBMS_OUTPUT.PUT_LINE('Found exception Error Message :' err_msg ' Error Number ;' err_num); END; END LOOP; commit; END; / Records already exists. Records already exists. Records already exists. Records already exists. PL/SQL procedure successfully completed 21. Start the OMS. 22. Execute the following command to start OMS. $ORACLE_HOME/bin/emctl start oms [oraoem@nclvoem04 omsca]$ $ORACLE_HOME/bin/emctl start oms Oracle Enterprise Manager Cloud Control 12c Release Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved. Starting WebTier... WebTier Successfully Started Starting Oracle Management Server... Oracle Management Server Successfully Started Oracle Management Server is Up 23. Configure the Management Agent. To do so, run the following command from the Management Agent home: <ORACLE_HOME>/sysman/install/agentDeploy.sh AGENT_BASE_ DIR=<absolute_path_to_agentbasedir> OMS_HOST=<oms_host> EM_ UPLOAD_PORT=<secure_oms_upload_port> AGENT_REGISTRATION_ PASSWORD=<agent_reg_password> -configonly export ORACLE_HOME=/u01/app/Middleware/agent/core/

25 $ORACLE_HOME/sysman/install/agentDeploy.sh AGENT_BASE_DIR=/u01/ app/middleware/agent OMS_HOST=nclvoem04.starfleet.com EM_UPLOAD_ PORT=1159 AGENT_REGISTRATION_PASSWORD=xxxxx configonly Agent deployment completed successfully. 24. Connect as a root user and execute the root.sh script. #. /u01/app/middleware/agent/core/ /root.sh Finished product-specific root actions. /etc exist How it works... This recipe describes the 1-system upgrade approach on a different host. This approach enables to install Enterprise Manager Cloud Control on a host different from where the existing Enterprise Manager is running. There's more... The preceding steps are valid for Oracle Enterprise Linux and will vary depending on the operating system being used. These steps will remain identical for the upgrade of OEM from Version to OEM 12c. 25

26