Skip Headers
Oracle® Enterprise Manager Cloud Control Upgrade Guide
12c Release 2 (12.1.0.2)
E22625-16
  Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
 
Next
Next
 

4 Upgrading OMS and Management Repository

This chapter describes the different ways of upgrading Oracle Management Service 12c Release 1 (12.1.0.1) [with or without Bundle Patch 1] and Oracle Management Repository 12c Release 1 (12.1.0.1). Select the one that best suits your requirement, and follow the instructions outlined in the respective section.

This chapter describes the following:


Note:

Oracle Management Agent (Management Agent) that was installed with the Oracle Management Service (OMS) is not upgraded by default. You must upgrade it (along with other Management Agents) using the Upgrade Agents Console. This is an expected behavior. For instructions to use the Upgrade Agents Console to upgrade Management Agents, see Chapter 5.


WARNING:

Do not upgrade Enterprise Manager Cloud Control 12c Release 1 (12.1.0.1) while it is undergoing a 2-system upgrade from its earlier release. Wait until the upgrade completes fully because there might be some standalone Management Agents in status pending state while the upgrade is in progress.


Upgrading OMS and Management Repository in Graphical Mode

To upgrade your Oracle Management Service 12c Release 1 (12.1.0.1) [with or without Bundle Patch 1] and Oracle Management Repository 12c Release 1 (12.1.0.1) in graphical mode, follow these steps:


WARNING:

Do not upgrade Enterprise Manager Cloud Control 12c Release 1 (12.1.0.1) while it is undergoing a 2-system upgrade from its earlier release. Wait until the upgrade completes fully because there might be some standalone Management Agents in status pending state while the upgrade is in progress.



Note:

While upgrading, you might see an error message stating that some Management Agents are still in Activation Pending state, or that the Deferred Data Migration Process (DDMP) or Accrued Data Migration Process (ADMP) is not complete. This indicates that the earlier release of the Enterprise Manager system is still undergoing a 2-system upgrade to 12c Release 1 (12.1.0.1).

To resolve this issue, wait until the DDMP and ADMP jobs are complete, and all Management Agents are switched over from the earlier release to 12c Release 1 (12.1.0.1). Then upgrade 12c Release 1 (12.1.0.1) to 12c Release 2 (12.1.0.2).

If you are sure you do not want to switch over some Management Agents from the earlier release to 12c Release 1 (12.1.0.1), then delete such unwanted Management Agents as described in Deleting Unwanted Management Agents, before you start the upgrade process.



Note:

After upgrading, if you want to delete the old OMS home, then follow the instructions outlined in Appendix L.


Note:

If you see an error message stating that you have not copied the emkey, run the following command.

$<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>] -emkey_file <OMS_HOME>/sysman/config/emkey.ora

(Here, the Management Repository details are details of the existing or old Management Repository. And when you run this command, you might be prompted for the admin server password.)



Caution:

Ensure that you use VNC Server to connect to the remote host while upgrading the OMS and the Management Repository. Other tools, such as cygwin, putty, and so on, sometimes time out or do not allow new Xdisplay connections, thus resulting in upgrade failures.

  1. Invoke the Enterprise Manager Cloud Control Installation Wizard on the host where your existing OMS is running.

    <Software_Location>/runInstaller [-invPtrLoc <absolute_path_to_oraInst.loc>]

    In this command, <Software_Location> refers to the location where you have extracted the software kit.


    Note:

    • For information about the additional, advanced options you can pass while invoking the installer, refer to Advanced Installer Options for Graphical Mode.

    • To invoke the installation wizard on UNIX platforms, run runInstaller. To invoke on Microsoft Windows platforms, run setup.exe.

    • When you invoke runInstaller or setup.exe, if the Enterprise Manager Cloud Control Installation Wizard does not appear, then it is possible that you do not have access to the /stage directory.

      There is a classpath variable that the installation wizard computes for OPatch as ../stage/Components/, and when the TEMP variable is set to /tmp, the installation wizard tries to look for the opatch JAR file in the /tmp/../stage directory, which is equivalent to /stage. However, if you do not have the permission on /stage, then the installation wizard can hang. Under such circumstances, verify if you have access to the /stage directory. If you do not have access to it, then set the TEMP variable to a location where the install user has access, and then relaunch the installation wizard.


  2. (Optional) On the My Oracle Support Details screen, enter your My Oracle Support credentials to enable Oracle Configuration Manager. If you do not want to enable Oracle Configuration Manager now, go to Step (3).

    If the host from where you are running the installation wizard does not have a connection to the Internet, then enter only the e-mail address and leave the other fields blank. After you complete the installation, manually collect the configuration information and upload it to My Oracle Support.

  3. Click Next.

  4. On the Software Updates screen, select one of the following sources from where the software updates can be installed while the Enterprise Manager system gets upgraded. If you do not want to apply them now, then select Skip.

    • (Recommended) Select Search for Updates, and then, select Local Directory if you have already manually downloaded the software updates to an accessible local or remote location.

      Enter the location where the updates are available, and click Search for Updates. To search the computer and select the location, click Browse. Once the search results appear with patch numbers and their details, click the patch number to view the ReadMe associated with that patch.


      Important:

      Make sure you apply patch 15951627. This patch fixes some critical, upgrade-related issues. If you do not have this patch, then manually download it from My Oracle Support using another host that has Internet connectivity, and transfer it to the local directory on this host where you are performing the installation.

      • If the updates have been downloaded to the default location, then select or enter the full path to the scratch path location. For example, if the scratch path location is /scratch/OracleHomes and if the software updates are available in /scratch/OracleHomes/Updates, then enter /scratch/OracleHomes/Updates.

      • If the software updates have been downloaded to a custom location, then select or enter the full path to the custom location. For example, if the custom location is /home/john and if the software updates are available in /home/john/Updates, then enter /home/john/Updates.

    • Select Search for Updates, and then, select My Oracle Support if you want the installer to connect to My Oracle Support and automatically download the updates from there.

      Enter the My Oracle Support account user name and password, and click Search for Updates. Once the search results appear with patch numbers and their details, click the patch number to view the ReadMe associated with that patch.


      Important:

      Make sure you apply patch 15951627. This patch fixes some critical, upgrade-related issues. If you do not have this patch, then manually download it from My Oracle Support using another host that has Internet connectivity, and transfer it to the local directory on this host where you are performing the installation.


    Note:

    If you choose to skip installing the software updates during installation by not providing the My Oracle Support credentials, you can always register the credentials later using the Enterprise Manager Cloud Control console and view the recommended security patches. To do so, log in to Enterprise Manager Cloud Control, and from the Setup menu, select My Oracle Support, and then, click Set Credentials. On the My Oracle Support Preferred Credentials page, enter the credentials and click Apply.

  5. Click Next.

  6. On the Prerequisite Checks screen, check the status of the prerequisite checks run by the installation wizard, and verify whether your environment meets all the minimum requirements for a successful upgrade.

    The installation wizard runs the prerequisite checks automatically when you come to this screen. It checks for the required operating system patches, operating system packages, and so on.

    The status of the prerequisite check can be either Warning, Failed, or Succeeded.

    If some checks result in Warning or Failed status, then investigate and correct the problems before you proceed with the upgrade. The screen provides details on why the prerequisites failed and how you can resolve them. After you correct the problems, return to this screen and click Rerun to check the prerequisites again.

    If you prefer to hide the successful checks and view only the ones with Warning or Failed status, then click Hide Successful Checks.

  7. Click Next.

  8. On the Installation Types screen, select Upgrade an Existing Enterprise Manager System, then select One System Upgrade. Then, select the OMS home you want to upgrade.

  9. Click Next.

  10. On the Installation Details screen, do the following:

    1. Enter or validate the Middleware home.


      Note:

      • Upgrade to 12c Release 2 (12.1.0.2) is an out-of-place upgrade, therefore you must either select an existing middleware home (where Enterprise Manager is not already installed) or enter a new middleware home where Oracle WebLogic Server and Java Development Kit are installed.

      • If you do not have Oracle WebLogic Server 11g Release 1 (10.3.5) and Java Development Kit 1.6 v24+ installed, then enter the absolute path to a directory where you want the installer to install them. For example, /oracle/software/. Ensure that the directory you enter does not contain any files or subdirectories.

      • If you have Oracle WebLogic Server and JDK already installed, then ensure that they are of the supported releases—Oracle WebLogic Server 11g Release 1 (10.3.5) and JDK 1.6 v24+. In this case, the installer detects them and displays the Middleware home where they are installed. Validate the path to this Middleware home. The installer detects and displays only those Middleware homes where Enterprise Manager is not already configured.


    2. Validate the host name. By default, the host name is the name of the host where the existing, earlier release of Enterprise Manager was installed. This is a non-editable field.

  11. Click Next.

  12. On the Database Connection Details screen, enter the passwords for the SYS and SYSMAN user accounts of the database that houses the Management Repository for the selected OMS.


    Note:

    • If a prerequisite check fails stating that you must check if there are any outstanding database service instance creation requests or cleanup executions, follow these steps:

      1. In Cloud Control, from the Enterprise menu, select Infrastructure Cloud, then select Self Service Portal.

      2. On the Infrastructure Cloud Self Service Portal page, right under the page title, select My Databases to view only database requests.

      3. In the Requests table, for requests that are in progress, allow them to complete. For requests that are scheduled, suspend them.

        To suspend the scheduled requests, click the request name. Click the Deployment tab. Click the deployment procedure listed there, and suspend it.

    • Before you proceed to the next screen, stop all the associated OMS instances.

      First, on the OMS you are upgrading, run the following command to . This command stops only the OMS, and not the Admin Server or any of its associated components. The Admin Server and other associated components must be running so that the credentials collected in Step (18) can be validated.

      $<OMS_HOME>/bin/emctl stop oms

      Then, on all other additional OMS instances, run the following command. This command stops the OMS and other components such as the node manager, which must be down for the upgrade to end successfully.

      $<OMS_HOME>/bin/emctl stop oms -all


  13. Click Next.


    Note:

    If you encounter a Provisioning Archive Framework (PAF) prerequisite check error, then exit the installer, stop all the running and scheduled deployment procedures in your existing Enterprise Manager system, invoke the installer all over again, and retry the upgrade process.

  14. On the Plug-In Upgrade screen, review the plug-ins that will be automatically:

    • Upgraded when newer versions exist

    • Migrated when newer versions do not exist

    • Deployed when the plug-ins being upgraded have new dependencies

    Here, newer versions refer to the newer versions of plug-ins available in the Enterprise Manager software (DVD, or downloaded software) that you are using to install.


    Note:

    If the newer versions do not exist in the Enterprise Manager software that you are using, but exist on Oracle Technology Network (OTN), then you can choose to manually download them from OTN and upgrade your existing plug-ins, instead of having them automatically migrated by default. To do so, follow these steps:
    1. Manually download the plug-ins from the Enterprise Manager download page on OTN, and store them in an accessible location.

      http://www.oracle.com/technetwork/oem/grid-control/downloads/oem-upgrade-console-502238.html

    2. Invoke the installer with the following option, and pass the location where the plug-ins you downloaded are available:

      ./runInstaller -pluginLocation <absolute_path_to_plugin_software_location>

    Once the newer versions of the plug-ins are made available, this screen lists those plug-ins as plug-ins that will automatically be upgraded.


  15. Click Next.

  16. On the Plug-In Deployment screen, select the optional plug-ins you want to deploy in addition to the plug-ins that will automatically be upgraded while upgrading the OMS.


    Note:

    If you want to install some plug-ins that are not listed on this screen, then follow these steps:
    1. Manually download the plug-ins from the Enterprise Manager download page on OTN, and store them in an accessible location.

      http://www.oracle.com/technetwork/oem/grid-control/downloads/oem-upgrade-console-502238.html

    2. Invoke the installer with the following option, and pass the location where the plug-ins you downloaded are available:

      ./runInstaller -pluginLocation <absolute_path_to_plugin_software_location>


  17. Click Next.

  18. On the Extend WebLogic Server Domain screen, do the following to create a new WebLogic domain and a new OMS instance base directory for the upgraded OMS:

    • Validate the AdminServer host name and its port, and the WebLogic user name, and enter the WebLogic user account password. This is required to create a new WebLogic domain (GCDomain) on the same port and host name as the AdminServer used by the earlier release of the OMS you are upgrading.


      Note:

      If you are upgrading an additional OMS, then enter the host name and port of the AdminServer configured for the first OMS that you have already upgraded, and then, enter the credentials for the existing WebLogic Server user account.

      The host name is the name of the host where the first OMS is running. To identify the port, check the value set to the parameter AS_HTTPS_PORT in the following file:

      <ORACLE_HOME>/gc_inst/em/EMGC_OMS<n>/emgc.properties


    • Enter the absolute path to the new OMS instance base directory (gc_inst), which will be created for storing the configuration information related to the upgraded OMS. Make sure the path you enter leads up to the instance base directory. You can maintain this directory inside or outside the middleware home. However, Oracle recommends that you maintain this directory inside the middleware home.

      For example, /u01/app/Oracle/Middleware/gc_inst.

  19. Click Next.

  20. On the Review screen, review the details you have provided for the upgrade.

    1. If you want to change the details, click Back repeatedly until you reach the screen where you want to make the changes.

    2. After you verify the details, if you are satisfied, click Install to begin the upgrade.

  21. On the Install Progress screen, view the overall progress (in percentage) of the upgrade operation and the status of each of the Configuration Assistants.


    Note:

    If a Configuration Assistant fails, the installer stops and none of the subsequent Configuration Assistants are run until the issue related to the failed Configuration Assistant is resolved. In this case, diagnose the issue, resolve it, and then, click Retry on the Install Progress screen to rerun the Configuration Assistants starting from the Configuration Assistant that failed.

    However, if you accidently exit the installer before clicking Retry, then do NOT restart the installer to reach the same screen; instead, invoke the runConfig.sh script from the OMS home to rerun the Configuration Assistant in silent mode:

    $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<absolute_path_to_OMS_home> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

    If the runConfig.sh script fails, raise a service request and contact Oracle Support.


  22. Once the software binaries are copied and configured, you are prompted to run the allroot.sh script. Open another window, log in as root, and manually run the scripts.

    If you are installing on Microsoft Windows operating system, then you will NOT be prompted to run this script.

  23. On the Finish screen, you should see information pertaining to the upgrade of Enterprise Manager. Review the information and click Close to exit the wizard.

  24. If you upgraded an additional OMS (12.1.0.1), then note that the OMS name changes and the configuration changes are made to the Oracle WebLogic domain that hosts Enterprise Manager. However, these configuration changes are not reflected in the Enterprise Manager Cloud Control Console until you refresh the WebLogic domain configuration within the console.

    To refresh the WebLogic domain, follow these steps:

    1. Navigate to the home page of the Oracle WebLogic domain that hosts Enterprise Manager.

    2. From the WebLogic Domain menu, select Refresh WebLogic Domain. The Refresh WebLogic Domain page appears.

    3. Follow the instructions on the Refresh WebLogic Domain page to refresh the WebLogic domain.


    WARNING:

    If you do not refresh the WebLogic domain, you will see the old OMS target on the WebLogic domain home page.

    If you have a JVM Agent deployed, then you will see the old OMS target even on the Deploy/Upgrade Diagnostic Agent : Select Targets page while upgrading the JVM Agent.

    Visible OMS Target Without Refreshing the WLS Domain

    Make sure you follow this step to clear the old OMS target from the Enterprise Manager Cloud Control Console.



    Caution:

    If you have any JVM targets associated with the old OMS, then even after you refresh the WebLogic domain, on the WebLogic domain home page, you will continue see the JVM target that was associated with the old OMS. This is an expected behavior. Surrounding text describes visible_jvm_target.gif.

    If you choose to either retain it for viewing historical data or delete it. To delete it, right-click the orphaned JVM target, and select Remove Target.


  25. Rename the following directories in the old OMS home (12.1.0.1 OMS home):


    Caution:

    Perform this step only if you had not applied patch 15951627 using the Software Updates screen, or if the patch had failed for some reason, as described in Step (4).

    • Rename the omsstup directory to omsstup_old in the following location:

      $<OLD_OMS_HOME>/install/unix/scripts/

    • Rename the bin directory to bin_old in the following location:

      $<OLD_OMS_HOME>/

    • Rename the wlserver_10.3 directory to wlserver_10.3_old in the following location:

      $<OLD_MW_HOME>

    If you do not rename the directories, then when you restart the upgraded OMS host, the Admin Server configured with the 12.1.0.1 OMS home starts, but neither the 12.1.0.1 OMS nor the upgraded 12.1.0.2 OMS run. This is more serious in a multi-OMS environment because the additional OMS instances continue to contact the Admin Server configured with the 12.1.0.1 OMS home instead of the 12.1.0.2 OMS home, and as a result, corrupt the OMS configuration.

  26. Ensure that you upgrade the Management Agent that was installed with the old OMS (that is, central agent) immediately after upgrading the old OMS. For more information, refer to Chapter 5.

    The agent base directory of the central agent resides within the Oracle Middleware home. For information on moving the agent base directory of the central agent outside the old Oracle Middleware home, refer the My Oracle Support note 1520010.1 available at the following URL:

    https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1520010.1

  27. (Optional) After upgrading, if you want to delete the old OMS home, then follow the instructions outlined in Appendix L

Advanced Installer Options for Graphical Mode

The following are some additional, advanced options you can pass while invoking the installer in graphical mode:

  • (Applicable only for when you upgrade 10.2.0.5), When you upgrade 10g Release 5 (10.2.0.5), a new WebLogic domain named GCDomain is created by default. If you want to override this with a custom name, then invoke the installer with the WLS_DOMAIN_NAME option, and enter a unique custom name.

    For example, if you want to use the custom name EMDomain, then run the following command:

    ./runInstaller WLS_DOMAIN_NAME=EMDomain

  • By default, a Provisioning Advisor Framework (PAF) staging directory is created for copying the Software Library entities related to the deployment procedures. By default, this location is the scratch path location (/tmp). The location is used only for provisioning activities—entities are copied for a deployment procedure, and then, deleted once the deployment procedure ends.

    If you want to override this location with a custom location, then invoke the installer with the EM_STAGE_DIR option, and enter a unique custom location.

    For example,

    ./runInstaller EM_STAGE_DIR=/home/john/software/oracle/pafdir

  • During upgrade, if you want to install some plug-ins that are not in the software kit (DVD, downloaded software), then follow these steps:

    1. Manually download the plug-ins from the following URL, and store them in an accessible location.

      http://www.oracle.com/technetwork/oem/grid-control/downloads/oem-upgrade-console-502238.html

    2. Invoke the installer with the following option, and pass the location where the plug-ins you want to install are available:

      ./runInstaller -pluginLocation <absolute_path_to_plugin_software_location>

      This displays a list of plug-ins available in the software kit (DVD, downloaded software) as well as the plug-ins available in this custom location. You can choose the ones you want to install.

  • After the upgrade operation ends successfully, the OMS and the Management Agent start automatically. If you do not want them to start automatically, then invoke the installer with START_OMS and b_startAgent options, and set them to true or false depending on what you want to control.

    For example, if you do not want the Management Agent to start automatically, then run the following command:

    ./runInstaller START_OMS=true b_startAgent=false

    To understand the limitations involved with this advanced option, see Limitations.

Limitations

When you use START_OMS and b_startAgent as advanced options to control the way the OMS and the Management Agent start up automatically, sometimes the Management Agent and the host on which it was installed do not appear as targets in the Cloud Control console.

Table 4-1 lists the different combinations of these advanced options, and describes the workaround to be followed for each combination:

Table 4-1 Advanced Options and Workarounds

Advanced Option Workaround

START_OMS=false

b_startAgent=false

  1. Start the OMS:

    $<OMS_HOME>/bin/emctl start oms

  2. Secure the Management Agent:

    $<AGENT_HOME>/bin/emctl secure agent

  3. Start the Management Agent:

    $<AGENT_HOME>/bin/emctl start agent

  4. Add the targets:

    $<AGENT_HOME>/bin/emctl config agent addinternaltargets

  5. Upload the targets:

    $<AGENT_HOME>/bin/emctl upload agent

  6. Manually configure the EM CLI tool in the $<ORACLE_HOME>/bin directory. To do so, refer to the Oracle Enterprise Manager Command Line Interface Guide.

START_OMS=true

b_startAgent=false

Start the Management Agent:

$<AGENT_HOME>/bin/emctl start agent

START_OMS=false

b_startAgent=true

  1. Start the OMS:

    $<OMS_HOME>/bin/emctl start oms

  2. Secure the Management Agent:

    $<AGENT_HOME>/bin/emctl secure agent

  3. Add the targets:

    $<AGENT_HOME>/bin/emctl config agent addinternaltargets

  4. Upload the targets:

    $<AGENT_HOME>/bin/emctl upload agent

  5. Manually configure the EM CLI tool in the $<ORACLE_HOME>/bin directory. To do so, refer to the Oracle Enterprise Manager Command Line Interface Guide.


Deleting Unwanted Management Agents

While upgrading, you might see an error message stating that some Management Agents are still in Activation Pending state, or that the Deferred Data Migration Process (DDMP) or Accrued Data Migration Process (ADMP) is not complete. This indicates that the earlier release of the Enterprise Manager system is still undergoing a 2-system upgrade to 12c Release 1 (12.1.0.1).

To resolve this issue, wait until the DDMP and ADMP jobs are complete, and all Management Agents are switched over from the earlier release to 12c Release 1 (12.1.0.1). Then upgrade 12c Release 1 (12.1.0.1) to 12c Release 2 (12.1.0.2).

If you are sure you do not want to switch over some Management Agents from the earlier release to 12c Release 1 (12.1.0.1), then delete such unwanted Management Agents before you start the upgrade process.

To delete these unwanted Management Agents, follow these steps:

  1. Identify the unwanted Management Agents, which you have not switched over, by running the following query:

    select mt.target_name from sysman.mgmt_targets mt, sysman.em_current_availability eca, sysman.PRE_UPGC_AGT_STAT_MGMT puasm
    where mt.target_guid = eca.target_guid
    and eca.current_status = 4
    and eca.current_sub_status = 1
    and mt.target_type='oracle_emd'
    and puasm.target_guid = mt.target_guid and puasm.UPGRADE_STATUS != 'IGNORE_UPGRADE'
    and mt.emd_url not in (select emd_url from PRE_UPGC_TGT_SW where target_type='oracle_emrep')
    and mt.emd_url not in (select emd_url from mgmt_targets where target_name in(select value from mgmt_oms_parameters where name = 'HOST_NAME'))
    and mt.emd_url not in (select distinct emd_url from mgmt_targets where target_name like 'EnterpriseManager%home' or target_name like '%GCD omain_EMGC_OMS%')
    
  2. Delete the unwanted Management Agents:

    1. On the upgrade OMS host, from the OMS home, log in to the EM CLI client. EM CLI Client is available by default with every OMS installation, so you need not install the client separately.

      $<OMS_HOME>/bin/emcli login -username=SYSMAN -password=<sysman-passwd>

    2. Synchronize EM CLI:

      $<OMS_HOME>/bin/emcli sync

    3. Delete the unwanted Management Agents. Here, agentName is the name of the Management Agent you want to delete.

      $<OMS_HOME>/bin/emcli delete_target -name = <agentName> -type=oracle_emd -delete_monitored_targets

  3. Proceed with the upgrade to 12c Release 2 (12.1.0.2).


Note:

If, for some reason, you are unable to delete the unwanted Management Agents, then turn off the sanity check that checks for Managements Agents with Activation Pending state. This enables you to proceed with the upgrade process without encountering any such warning. To turn off the sanity check, run the query as described in Appendix K.

Upgrading OMS and Management Repository in Silent Mode

To upgrade your Oracle Management Service 12c Release 1 (12.1.0.1) [with or without Bundle Patch 1] and Oracle Management Repository 12c Release 1 (12.1.0.1) in silent mode, follow these steps:


WARNING:

Do not upgrade Enterprise Manager Cloud Control 12c Release 1 (12.1.0.1) while it is undergoing a 2-system upgrade from its earlier release. Wait until the upgrade completes fully because there might be some standalone Management Agents in status pending state while the upgrade is in progress.



Note:

While upgrading, you might see an error message stating that some Management Agents are still in Activation Pending state, or that the Deferred Data Migration Process (DDMP) or Accrued Data Migration Process (ADMP) is not complete. This indicates that the earlier release of the Enterprise Manager system is still undergoing a 2-system upgrade to 12c Release 1 (12.1.0.1).

To resolve this issue, wait until the DDMP and ADMP jobs are complete, and all Management Agents are switched over from the earlier release to 12c Release 1 (12.1.0.1). Then upgrade 12c Release 1 (12.1.0.1) to 12c Release 2 (12.1.0.2).

If you are sure you do not want to switch over some Management Agents from the earlier release to 12c Release 1 (12.1.0.1), then delete such unwanted Management Agents as described in Deleting Unwanted Management Agents, before you start the upgrade process.



Note:

After upgrading, if you want to delete the old OMS home, then follow the instructions outlined in Appendix L.


Note:

If you see an error message stating that you have not copied the emkey, run the following command.

$<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>] -emkey_file <OMS_HOME>/sysman/config/emkey.ora

(Here, the Management Repository details are details of the existing or old Management Repository. And when you run this command, you might be prompted for the admin server password.)



Caution:

Ensure that you use VNC Server to connect to the remote host while upgrading the OMS and the Management Repository. Other tools, such as cygwin, putty, and so on, sometimes time out or do not allow new Xdisplay connections, thus resulting in upgrade failures.

  1. Copy the following response file to an accessible location on your local host:

    <Software_Location>/response/upgrade.rsp

    In this command, <Software_Location> refers to the location where you have extracted the software kit (DVD, or downloaded software).

  2. Edit the response file and enter appropriate values for the variables described in Appendix A.

  3. Invoke the installer:

    ./runInstaller -silent -responseFile <absolute_path>/upgrade.rsp


    Note:

    • To invoke the installation wizard on UNIX platforms, run runInstaller. To invoke on Microsoft Windows platforms, run setup.exe.

    • For information about the additional, advanced options you can pass while invoking the installer, refer to Advanced Installer Options for Silent Mode.


  4. If you upgraded an additional OMS (11.1.0.1 or 12.1.0.1), then note that the OMS name changes and the configuration changes are made to the Oracle WebLogic domain that hosts Enterprise Manager. However, these configuration changes are not reflected in the Enterprise Manager Cloud Control Console until you refresh the WebLogic domain configuration within the console.

    To refresh the WebLogic domain, follow these steps:

    1. Navigate to the home page of the Oracle WebLogic domain that hosts Enterprise Manager.

    2. From the WebLogic Domain menu, select Refresh WebLogic Domain. The Refresh WebLogic Domain page appears.

    3. Follow the instructions on the Refresh WebLogic Domain page to refresh the WebLogic domain.


    WARNING:

    If you do not refresh the WebLogic domain, you will see the old OMS target on the WebLogic domain home page.

    (Applicable only for 12.1.01 to 12.1.0.2 Upgrade) If you have a JVM Agent deployed, then you will see the old OMS target even on the Deploy/Upgrade Diagnostic Agent : Select Targets page while upgrading the JVM Agent.

    Visible OMS Target Without Refreshing the WLS Domain

    Make sure you follow this step to clear the old OMS target from the Enterprise Manager Cloud Control Console.



    Caution:

    (Applicable only for 12.1.01 to 12.1.0.2 Upgrade) If you have any JVM targets associated with the old OMS, then even after you refresh the WebLogic domain, on the WebLogic domain home page, you will continue see the JVM target that was associated with the old OMS. This is an expected behavior. Surrounding text describes visible_jvm_target.gif.

    If you choose to either retain it for viewing historical data or delete it. To delete it, right-click the orphaned JVM target, and select Remove Target.


  5. Rename the following directories in the old OMS home (12.1.0.1 OMS home):


    Caution:

    Perform this step only if you had not applied patch 15951627, or if the patch had failed for some reason, as described for the INSTALL_UPDATES_SELECTION parameter in Table A-1.

    • Rename the omsstup directory to omsstup_old in the following location:

      $<OLD_OMS_HOME>/install/unix/scripts/

    • Rename the bin directory to bin_old in the following location:

      $<OLD_OMS_HOME>/

    • Rename the wlserver_10.3 directory to wlserver_10.3_old in the following location:

      $<OLD_MW_HOME>

    If you do not rename the directories, then when you restart the upgraded OMS host, the Admin Server configured with the 12.1.0.1 OMS home starts, but neither the 12.1.0.1 OMS nor the upgraded 12.1.0.2 OMS run. This is more serious in a multi-OMS environment because the additional OMS instances continue to contact the Admin Server configured with the 12.1.0.1 OMS home instead of the 12.1.0.2 OMS home, and as a result, corrupt the OMS configuration.

  6. Ensure that you upgrade the Management Agent that was installed with the old OMS (that is, central agent) immediately after upgrading the old OMS. For more information, refer to Chapter 5.

    The agent base directory of the central agent resides within the Oracle Middleware home. For information on moving the agent base directory of the central agent outside the old Oracle Middleware home, refer the My Oracle Support note 1520010.1 available at the following URL:

    https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1520010.1

  7. (Optional) After upgrading, if you want to delete the old OMS home, then follow the instructions outlined in Appendix L

Advanced Installer Options for Silent Mode

The following are some additional, advanced options you can pass while invoking the installer in silent mode:

  • (Applicable only for 2-system upgrade from 10.2.0.5 or 11.1.0.1) If you are upgrading on a host that has multiple host names (for examle, virtual host), then pass the fully qualified host name using the ORACLE_HOSTNAME argument while invoking the installer.

    For example:

    ./runInstaller ORACLE_HOSTNAME=example.com -silent -responseFile <absolute_path>/upgrade.rsp

  • After the installation ends successfully, the OMS and the Management Agent start automatically. If you do not want them to start automatically, then invoke the installer with START_OMS and b_startAgent options, and set them to true or false depending on what you want to control.

    For example, if you do not want the Management Agent to start automatically, then run the following command:

    ./runInstaller START_OMS=true b_startAgent=false -silent -responseFile <absolute_path>/upgrade.rsp

    To understand the limitations involved with this advanced option, see Limitations.

Installing Software Now and Upgrading Later in Graphical Mode

This section describes how you can install only the software binaries of Enterprise Manager 12c Cloud Control in graphical mode at one point, and upgrade them at a later point. In particular, this section covers the following:


WARNING:

Do not upgrade Enterprise Manager Cloud Control 12c Release 1 (12.1.0.1) while it is undergoing a 2-system upgrade from its earlier release. Wait until the upgrade completes fully because there might be some standalone Management Agents in status pending state while the upgrade is in progress.



Note:

While upgrading, you might see an error message stating that some Management Agents are still in Activation Pending state, or that the Deferred Data Migration Process (DDMP) or Accrued Data Migration Process (ADMP) is not complete. This indicates that the earlier release of the Enterprise Manager system is still undergoing a 2-system upgrade to 12c Release 1 (12.1.0.1).

To resolve this issue, wait until the DDMP and ADMP jobs are complete, and all Management Agents are switched over from the earlier release to 12c Release 1 (12.1.0.1). Then upgrade 12c Release 1 (12.1.0.1) to 12c Release 2 (12.1.0.2).

If you are sure you do not want to switch over some Management Agents from the earlier release to 12c Release 1 (12.1.0.1), then delete such unwanted Management Agents as described in Deleting Unwanted Management Agents, before you start the upgrade process.



Note:

After upgrading, if you want to delete the old OMS home, then follow the instructions outlined in Appendix L.


Note:

If you see an error message stating that you have not copied the emkey, run the following command.

$<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>] -emkey_file <OMS_HOME>/sysman/config/emkey.ora

(Here, the Management Repository details are details of the existing or old Management Repository. And when you run this command, you might be prompted for the admin server password.)



Caution:

Ensure that you use VNC Server to connect to the remote host while upgrading the OMS and the Management Repository. Other tools, such as cygwin, putty, and so on, sometimes time out or do not allow new Xdisplay connections, thus resulting in upgrade failures.

Installing Software Binaries

To install the software binaries of Enterprise Manager Cloud Control, follow these steps:

  1. Invoke the Enterprise Manager Cloud Control Installation Wizard on the host where your existing OMS is running.

    <Software_Location>/runInstaller [-invPtrLoc <absolute_path_to_oraInst.loc>]


    Note:

    • In this command, <Software_Location> refers to the location where you have extracted the software kit.

    • To invoke the installation wizard on UNIX platforms, run runInstaller. To invoke on Microsoft Windows platforms, run setup.exe.

    • The central inventory location you enter must NOT be on a shared file system.



    Note:

    When you invoke runInstaller or setup.exe, if the Enterprise Manager Cloud Control Installation Wizard does not appear, then it is possible that you do not have access to the /stage directory.

    There is a classpath variable that the installation wizard computes for OPatch as ../stage/Components/, and when the TEMP variable is set to /tmp, the installation wizard tries to look for the opatch JAR file in the /tmp/../stage directory, which is equivalent to /stage. However, if you do not have the permission on /stage, then the installation wizard can hang. Under such circumstances, verify if you have access to the /stage directory. If you do not have access to it, then set the TEMP variable to a location where the install user has access, and then relaunch the installation wizard.


  2. (Optional) On the My Oracle Support Details screen, enter your My Oracle Support credentials to enable Oracle Configuration Manager. If you do not want to enable Oracle Configuration Manager now, go to Step (3).

    If the host from where you are running the installation wizard does not have a connection to the Internet, then enter only the e-mail address and leave the other fields blank. After you complete the installation, manually collect the configuration information and upload it to My Oracle Support.

  3. Click Next.

  4. On the Software Updates screen, select one of the following sources from where the software updates can be installed while the Enterprise Manager system gets upgraded. If you do not want to apply them now, then select Skip.

    • (Recommended) Select Search for Updates, and then, select Local Directory if you have already manually downloaded the software updates to an accessible local or remote location.

      Enter the location where the updates are available, and click Search for Updates. To search the computer and select the location, click Browse. Once the search results appear with patch numbers and their details, click the patch number to view the ReadMe associated with that patch.


      Important:

      Make sure you apply patch 15951627. This patch fixes some critical, upgrade-related issues. If you do not have this patch, then manually download it from My Oracle Support using another host that has Internet connectivity, and transfer it to the local directory on this host where you are performing the installation.

      • If the updates have been downloaded to the default location, then select or enter the full path to the scratch path location. For example, if the scratch path location is /scratch/OracleHomes and if the software updates are available in /scratch/OracleHomes/Updates, then enter /scratch/OracleHomes/Updates.

      • If the software updates have been downloaded to a custom location, then select or enter the full path to the custom location. For example, if the custom location is /home/john and if the software updates are available in /home/john/Updates, then enter /home/john/Updates.

    • Select Search for Updates, and then, select My Oracle Support if you want the installer to connect to My Oracle Support and automatically download the updates from there.

      Enter the My Oracle Support account user name and password, and click Search for Updates. Once the search results appear with patch numbers and their details, click the patch number to view the ReadMe associated with that patch.


      Important:

      Make sure you apply patch 15951627. This patch fixes some critical, upgrade-related issues. If you do not have this patch, then manually download it from My Oracle Support using another host that has Internet connectivity, and transfer it to the local directory on this host where you are performing the installation.


    Note:

    If you choose to skip installing the software updates during installation by not providing the My Oracle Support credentials, you can always register the credentials later using the Enterprise Manager Cloud Control console and view the recommended security patches. To do so, log in to Enterprise Manager Cloud Control, and from the Setup menu, select My Oracle Support, and then, click Set Credentials. On the My Oracle Support Preferred Credentials page, enter the credentials and click Apply.

  5. Click Next.

  6. On the Prerequisite Checks screen, check the status of the prerequisite checks run by the installation wizard, and verify whether your environment meets all the minimum requirements for a successful upgrade.

    The installation wizard runs the prerequisite checks automatically when you come to this screen. It checks for the required operating system patches, operating system packages, and so on.

    The status of the prerequisite check can be either Warning, Failed, or Succeeded.

    If some checks result in Warning or Failed status, then investigate and correct the problems before you proceed with the upgrade. The screen provides details on why the prerequisites failed and how you can resolve them. After you correct the problems, return to this screen and click Rerun to check the prerequisites again.

    If you prefer to hide the successful checks and view only the ones with Warning or Failed status, then click Hide Successful Checks.

  7. Click Next.

  8. On the Installation Types screen, select Install software only.

  9. Click Next.

  10. On the Installation Details screen, do the following:

    1. Enter or validate or enter the Middleware home.


      Note:

      • Upgrade to 12c Release 2 (12.1.0.2) is an out-of-place upgrade, therefore you must either select an existing middleware home or enter a new middleware home where Oracle WebLogic Server and Java Development Kit are installed.

      • If you do not have Oracle WebLogic Server 11g Release 1 (10.3.5) and Java Development Kit 1.6 v24+ installed, then enter the absolute path to a directory where you want the installer to install them. For example, /oracle/software/. Ensure that the directory you enter does not contain any files or subdirectories.

      • If you have Oracle WebLogic Server and JDK already installed, then ensure that they are of the supported releases—Oracle WebLogic Server 11g Release 1 (10.3.5) and JDK 1.6 v24+. In this case, the installer detects them and displays the Middleware home where they are installed. Validate the path to this Middleware home. The installer detects and displays only those Middleware homes where Enterprise Manager is not already configured.


    2. Enter the absolute path to the agent base directory, a location outside the Oracle Middleware home where the Management Agent can be installed. For example, /oracle/agent. Ensure that this location is empty and has write permission. Also ensure that it is always maintained outside the Oracle Middleware home.


      Note:

      This is a mandatory field although the Management Agent installed with the OMS is not required, and must be deinstalled as described in Step (15).

    3. Validate the host name. By default, the host name is the name of the host where the existing, earlier release of Enterprise Manager was installed. This is a non-editable field.

  11. Click Next.

  12. On the Review screen, review the details you provided for the selected installation type.

    • If you want to change the details, click Back repeatedly until you reach the screen where you want to make the changes.

    • After you verify the details, if you are satisfied, click Install to begin the installation process.

  13. On the Install Progress screen, view the overall progress (in percentage) of the installation.

  14. On the Finish screen, you should see information pertaining to the installation of Enterprise Manager. Review the information and click Close to exit the installation wizard.

  15. Deinstall the Management Agent. For instructions, refer to the chapter on deinstalling a Management Agent in the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.


    Note:

    The Management Agent installed with the OMS is a fresh installation, and therefore is not required.
    • If you are upgrading from 12c Release 1 (12.1.0.1), then you must upgrade your Management Agent using the Upgrade Agents Console. For instructions to use the Upgrade Agents Console to upgrade Management Agents, see Chapter 5 .

    • If you are upgrading 10g Release 5 (10.2.0.5) or 11g Release 1 (11.1.0.1), then you already have the Management Agent predeployed by the Preupgrade Console.


Running allroot.sh Script

(For UNIX Only) After you install the software binaries, log in as a root user in a new terminal and run the allroot.sh script from the OMS home:

$<OMS_HOME>/allroot.sh

Configuring and Upgrading

To configure the software binaries of Enterprise Manager Cloud Control, follow these steps:

  1. Invoke the installation wizard by running the following script:

    $<MIDDLEWARE_HOME>/oms/sysman/install/ConfigureGC.sh [-invPtrLoc <absolute_path_to_oraInst.loc>]


    Note:


  2. On the Install Types screen, do the following:

    1. Select Upgrade an Existing Enterprise Manager System, and then, select One System Upgrade.

    2. Select the OMS home you want to upgrade.

  3. Click Next.

  4. On the Database Connection Details screen, enter the passwords for the SYS and SYSMAN user accounts of the database that houses the Management Repository for the selected OMS.


    Note:

    • If a prerequisite check fails stating that you must check if there are any outstanding database service instance creation requests or cleanup executions, follow these steps:

      1. In Cloud Control, from the Enterprise menu, select Infrastructure Cloud, then select Self Service Portal.

      2. On the Infrastructure Cloud Self Service Portal page, right under the page title, select My Databases to view only database requests.

      3. In the Requests table, for requests that are in progress, allow them to complete. For requests that are scheduled, suspend them.

        To suspend the scheduled requests, click the request name. Click the Deployment tab. Click the deployment procedure listed there, and suspend it.

    • Before you proceed to the next screen, stop all the associated OMS instances.

      First, on the OMS you are upgrading, run the following command to . This command stops only the OMS, and not the Admin Server or any of its associated components. The Admin Server and other associated components must be running so that the credentials collected in Step (10) can be validated.

      $<OMS_HOME>/bin/emctl stop oms

      Then, on all other additional OMS instances, run the following command. This command stops the OMS and other components such as the node manager, which must be down for the upgrade to end successfully.

      $<OMS_HOME>/bin/emctl stop oms -all


  5. Click Next.


    Note:

    If you see an error about missing plug-ins, then do the following:
    1. Make a note of the plug-in version and plug-in update as shown in the missing plug-ins error message. The plug-ins displayed in the error message have the following format:

      PluginID:PluginVersion:PluginUpdate

    2. Manually download the same plug-in version and the same or higher plug-in update as shown in the missing plug-ins error message, from the following URL.

      http://www.oracle.com/technetwork/oem/grid-control/downloads/oem-upgrade-console-502238.html

      Store the plug-ins in an accessible location, and ensure that the location is meant only for these missing plug-ins.

    3. Invoke the ConfigureGC.sh script in the following way to install the downloaded plug-ins:

      <OMS_HOME>/sysman/install/ConfigureGC.sh -pluginLocation <absolute_path_to_plugin_sw>

    Proceed to the next step only after you have installed these missing plug-ins.


  6. On the Plug-In Upgrade screen, review the plug-ins that will be automatically:

    • Upgraded when newer versions exist

    • Migrated when newer versions do not exist

    • Deployed when the plug-ins being upgraded have new dependencies

    Here, newer versions refer to the newer versions of plug-ins available in the Enterprise Manager software (DVD, or downloaded software) that you are using to install.


    Note:

    If the newer versions do not exist in the Enterprise Manager software that you are using, but exist on OTN, then you can choose to manually download them from OTN and upgrade your existing plug-ins, instead of having them automatically migrated by default. To do so, follow these steps:
    1. Manually download the plug-ins from the Enterprise Manager download page on OTN, and store them in an accessible location.

      http://www.oracle.com/technetwork/oem/grid-control/downloads/oem-upgrade-console-502238.html

    2. Invoke the installer with the following option, and pass the location where the plug-ins you downloaded are available:

      $<MIDDLEWARE_HOME>/oms/sysman/install/ConfigureGC.sh -pluginLocation <absolute_path_to_plugin_software_location>

    Once the newer versions of the plug-ins are made available, this screen lists those plug-ins as plug-ins that will automatically be upgraded.


  7. Click Next.

  8. On the Plug-In Deployment screen, select the optional plug-ins you want to deploy in addition to the plug-ins that will automatically be upgraded while upgrading the OMS.


    Note:

    If you want to install any additional plug-ins that are not listed on this screen, then follow these steps:
    1. Manually download the plug-ins from the Enterprise Manager download page on OTN, and store them in an accessible location.

      http://www.oracle.com/technetwork/oem/grid-control/downloads/oem-upgrade-console-502238.html

    2. Invoke the installer with the following option, and pass the location where the plug-ins you downloaded are available:

      $<MIDDLEWARE_HOME>/oms/sysman/install/ConfigureGC.sh -pluginLocation <absolute_path_to_plugin_software_location>


  9. Click Next.

  10. On the Extend WebLogic Server Domain screen, do the following to create a new WebLogic domain and a new OMS instance base directory for the upgraded OMS:

    • Validate the AdminServer host name and its port, and the WebLogic user name, and enter the WebLogic user account password. This is required to create a new WebLogic domain (GCDomain) on the same port and host name as the AdminServer used by the earlier release of the OMS you are upgrading.


      Note:

      If you are upgrading an additional OMS, then enter the host name and port of the AdminServer configured for the first OMS that you have already upgraded, and then, enter the credentials for the existing WebLogic Server user account.

      The host name is the name of the host where the first OMS is running. To identify the port, check the value set to the parameter AS_HTTPS_PORT in the following file:

      <ORACLE_HOME>/gc_inst/em/EMGC_OMS<n>/emgc.properties


    • Enter the absolute path to the new OMS instance base directory (gc_inst), which will be created for storing the configuration information related to the upgraded OMS. Make sure the path you enter leads up to the instance base directory. You can maintain this directory inside or outside the middleware home. However, Oracle recommends that you maintain this directory inside the middleware home.

      For example, /u01/app/Oracle/Middleware/gc_inst.

  11. Click Next.

  12. On the Review screen, review the details you provided for the selected installation type.

    • If you want to change the details, click Back repeatedly until you reach the screen where you want to make the changes.

    • After you verify the details, if you are satisfied, click Configure to begin the installation process.

  13. On the Install Progress screen, view the overall progress (in percentage) of the installation.


    Note:

    If a Configuration Assistant fails, the installer stops and none of the subsequent Configuration Assistants are run until the issue related to the failed Configuration Assistant is resolved. In this case, diagnose the issue, resolve it, and then, click Retry on the Install Progress screen to rerun the Configuration Assistants starting from the Configuration Assistant that failed.

    However, if you accidentally exit the installer before clicking Retry, then do NOT restart the installer to reach the same screen; instead, invoke the runConfig.sh script from the OMS home to rerun the Configuration Assistant in silent mode:

    $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<absolute_path_to_OMS_home> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

    If the runConfig.sh script fails, raise a service request and contact Oracle Support.


  14. On the Finish screen, you should see information pertaining to the installation of Enterprise Manager. Review the information and click Close to exit the installation wizard.

  15. If you upgraded an additional OMS (11.1.0.1 or 12.1.0.1), then note that the OMS name changes and the configuration changes are made to the Oracle WebLogic domain that hosts Enterprise Manager. However, these configuration changes are not reflected in the Enterprise Manager Cloud Control Console until you refresh the WebLogic domain configuration within the console.

    To refresh the WebLogic domain, follow these steps:

    1. Navigate to the home page of the Oracle WebLogic domain that hosts Enterprise Manager.

    2. From the WebLogic Domain menu, select Refresh WebLogic Domain. The Refresh WebLogic Domain page appears.

    3. Follow the instructions on the Refresh WebLogic Domain page to refresh the WebLogic domain.


    WARNING:

    If you do not refresh the WebLogic domain, you will see the old OMS target on the WebLogic domain home page.

    If you have a JVM Agent deployed, then you will see the old OMS target even on the Deploy/Upgrade Diagnostic Agent : Select Targets page while upgrading the JVM Agent.

    Visible OMS Target Without Refreshing the WLS Domain

    Make sure you follow this step to clear the old OMS target from the Enterprise Manager Cloud Control Console.



    Caution:

    If you have any JVM targets associated with the old OMS, then even after you refresh the WebLogic domain, on the WebLogic domain home page, you will continue see the JVM target that was associated with the old OMS. This is an expected behavior. Surrounding text describes visible_jvm_target.gif.

    If you choose to either retain it for viewing historical data or delete it. To delete it, right-click the orphaned JVM target, and select Remove Target.


  16. Rename the following directories in the old OMS home (12.1.0.1 OMS home):


    Caution:

    Perform this step only if you had not applied patch 15951627 using the Software Updates screen, or if the patch had failed for some reason, as described in Step (4) of Installing Software Binaries.

    • Rename the omsstup directory to omsstup_old in the following location:

      $<OLD_OMS_HOME>/install/unix/scripts/

    • Rename the bin directory to bin_old in the following location:

      $<OLD_OMS_HOME>/

    • Rename the wlserver_10.3 directory to wlserver_10.3_old in the following location:

      $<OLD_MW_HOME>

    If you do not rename the directories, then when you restart the upgraded OMS host, the Admin Server configured with the 12.1.0.1 OMS home starts, but neither the 12.1.0.1 OMS nor the upgraded 12.1.0.2 OMS run. This is more serious in a multi-OMS environment because the additional OMS instances continue to contact the Admin Server configured with the 12.1.0.1 OMS home instead of the 12.1.0.2 OMS home, and as a result, corrupt the OMS configuration.

  17. Upgrade the Management Agent that was installed with the old OMS (that is, central agent) immediately after upgrading the old OMS. For more information, refer to Chapter 5.

  18. (Optional) After upgrading, if you want to delete the old OMS home, then follow the instructions outlined in Appendix L

Advanced Script Options for Software-Only Mode

The following are some additional, advanced options you can pass while invoking the configureGC.sh script:

  • By default, GCDomain is the default name used for creating the WebLogic Domain. To override this and use a custom WebLogic Domain name, invoke the script with the WLS_DOMAIN_NAME option, and enter a unique custom name.

    For example, if you want to use the custom name EMDomain, then run the following command:

    $<MIDDLEWARE_HOME>/oms/sysman/install/ConfigureGC.sh WLS_DOMAIN_NAME=EMDomain

  • After the configuration ends successfully, the OMS and the Management Agent start automatically. If you do not want them to start automatically, then invoke the script with START_OMS and b_startAgent options, and set them to true or false depending on what you want to control.

    For example, if you do not want the Management Agent to start automatically, then run the following command:

    $<MIDDLEWARE_HOME>/oms/sysman/install/ConfigureGC.sh START_OMS=true b_startAgent=false

    To understand the limitations involved with this advanced option, see Limitations.

Installing Software Now and Upgrading Later in Silent Mode

This section explains how you can install only the software binaries of Enterprise Manager 12c Cloud Control in silent mode at one point, and upgrade them at a later point:


WARNING:

Do not upgrade Enterprise Manager Cloud Control 12c Release 1 (12.1.0.1) while it is undergoing a 2-system upgrade from its earlier release. Wait until the upgrade completes fully because there might be some standalone Management Agents in status pending state while the upgrade is in progress.



Note:

While upgrading, you might see an error message stating that some Management Agents are still in Activation Pending state, or that the Deferred Data Migration Process (DDMP) or Accrued Data Migration Process (ADMP) is not complete. This indicates that the earlier release of the Enterprise Manager system is still undergoing a 2-system upgrade to 12c Release 1 (12.1.0.1).

To resolve this issue, wait until the DDMP and ADMP jobs are complete, and all Management Agents are switched over from the earlier release to 12c Release 1 (12.1.0.1). Then upgrade 12c Release 1 (12.1.0.1) to 12c Release 2 (12.1.0.2).

If you are sure you do not want to switch over some Management Agents from the earlier release to 12c Release 1 (12.1.0.1), then delete such unwanted Management Agents as described in Deleting Unwanted Management Agents, before you start the upgrade process.



Note:

After upgrading, if you want to delete the old OMS home, then follow the instructions outlined in Appendix L.


Note:

If you see an error message stating that you have not copied the emkey, run the following command.

$<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>] -emkey_file <OMS_HOME>/sysman/config/emkey.ora

(Here, the Management Repository details are details of the existing or old Management Repository. And when you run this command, you might be prompted for the admin server password.)



Caution:

Ensure that you use VNC Server to connect to the remote host while upgrading the OMS and the Management Repository. Other tools, such as cygwin, putty, and so on, sometimes time out or do not allow new Xdisplay connections, thus resulting in upgrade failures.

Installing Software Binaries

To install the software binaries of Enterprise Manager 12c Cloud Control, follow these steps:

  1. Copy the following response file to an accessible location on your local host:

    <Software_Location>/response/software_only.rsp

    In this command, <Software_Location> refers to the location where you have extracted the software kit.

  2. Edit the response file and enter appropriate values for the variables described in Table 4-2.

  3. Invoke the installer:

    ./runInstaller -silent -responseFile <absolute_path>/software_only.rsp [-invPtrLoc <absolute_path_to_oraInst.loc>]


    Note:

    • To invoke the installation wizard on UNIX platforms, run runInstaller. To invoke on Microsoft Windows platforms, run setup.exe.

    • For information about the additional, advanced options you can pass while invoking the installer, refer to Advanced Installer Options for Silent Mode.

    • The central inventory location you enter must NOT be on a shared file system.


  4. Deinstall the Management Agent. For instructions, refer to the chapter on deinstalling a Management Agent in the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.


    Note:

    The Management Agent installed with the OMS is a fresh installation, and therefore is not required.
    • If you are upgrading from 12c Release 1 (12.1.0.1), then you must upgrade your Management Agent using the Upgrade Agents Console. For instructions to use the Upgrade Agents Console to upgrade Management Agents, see Chapter 5 .

    • If you are upgrading 10g Release 5 (10.2.0.5) or 11g Release 1 (11.1.0.1), then you already have the Management Agent predeployed by the Preupgrade Console.


Editing Response File for Installing Software Binaries

Table 4-2 describes what variables you must edit and how you must edit them in the software_only.rsp response file for installing the software binaries of Enterprise Manager Cloud Control.

Table 4-2 Editing Response File for Installing Software Binaries

Parameter Description

INSTALL_UPDATES_SELECTION

By default, this variable is set to "skip" indicating that the software updates will not be installed during installation.

  • If you want to install the software updates from My Oracle Support, then set this variable to "download". Then, enter the credentials for the following variables:

    MYORACLESUPPORT_USERNAME_FOR_SOFTWAREUPDATES

    MYORACLESUPPORT_PASSWORD_FOR_SOFTWAREUPDATES

  • If you want to install the software updates from a staged location, then set this variable to "staged". Then, for the STAGE_LOCATION parameter, enter the absolute path, which leads to the Updates directory, where the software updates are available.

Important: Make sure you apply patch 15951627. This patch fixes some critical, upgrade-related issues. If you do not have this patch, then manually download it from My Oracle Support using another host that has Internet connectivity, and transfer it to the local directory on this host where you are performing the installation.

ORACLE_MIDDLEWARE_HOME_LOCATION

Upgrade to 12c Release 2 (12.1.0.2) is an out-of-place upgrade, therefore you must specify an existing middleware home or enter a new middleware home where Oracle WebLogic Server and Java Development Kit are installed.

Enter the location where you have installed Oracle WebLogic Server 11g Release 1 (10.3.5) and Java Development Kit 1.6 v24. If you do not already have them installed, then enter the location where you want the installer to install them.

For example, u01/app/Oracle/Middleware.

Ensure that the middleware location has write permission to create the Oracle homes for OMS and Management Agent.

Note: Ensure that the Middleware home you enter here is used only for Enterprise Manager Cloud Control. Ensure that no other Oracle Fusion Middleware products or components are installed in the same Middleware home.

ORACLE_HOSTNAME

(Applicable only for 2-system upgrade of 10.2.0.5 or 11.1.0.1)

By default, the fully qualified name of the host on which you have invoked the installer, is considered.

  • To accept the default value, leave it blank.

  • To install with a different host name, then enter another host name.

AGENT_BASE_DIR

Enter the absolute path to the agent base directory, a location outside the Oracle Middleware home where the Management Agent can be installed.

For example, u01/app/Oracle/Middleware/agent. Ensure that this location is empty and has write permission. Also ensure that it is always maintained outside the Oracle Middleware home.


After You Install

(For UNIX Only) After you install the software binaries, log in as a root user in a new terminal and run the allroot.sh script from the OMS home:

$<OMS_HOME>/allroot.sh

Configuring and Upgrading

To configure the software binaries of Enterprise Manager Cloud Control, follow these steps:

  1. Copy the following response file to an accessible location on the host where you copied the software binaries of Enterprise Manager Cloud Control:

    <Software_Location>/response/upgrade.rsp

    In this command, <Software_Location> refers to the location where you have extracted the software kit.

  2. Edit the response file and enter appropriate values for the variables described in Appendix A.

  3. Configure the software binaries by invoking the ConfigureGC.sh script passing the response you edited in the previous step:

    $<MIDDLEWARE_HOME>/oms/sysman/install/ConfigureGC.sh -silent -responseFile <absolute_path>/upgrade.rsp [-invPtrLoc <absolute_path_to_oraInst.loc>]


    Note:



    Note:

    If you see an error about missing plug-ins, then do the following:
    1. Make a note of the plug-in version and plug-in update as shown in the missing plug-ins error message. The plug-ins displayed in the error message have the following format:

      PluginID:PluginVersion:PluginUpdate

    2. Manually download the same plug-in version and the same or higher plug-in update as shown in the missing plug-ins error message, from the following URL.

      http://www.oracle.com/technetwork/oem/grid-control/downloads/oem-upgrade-console-502238.html

      Store the plug-ins in an accessible location, and ensure that the location is meant only for these missing plug-ins.

    3. Invoke the ConfigureGC.sh script in the following way to install the downloaded plug-ins:

      <OMS_HOME>/sysman/install/ConfigureGC.sh -pluginLocation <absolute_path_to_plugin_sw>


  4. If you upgraded an additional OMS (11.1.0.1 or 12.1.0.1), then note that the OMS name changes and the configuration changes are made to the Oracle WebLogic domain that hosts Enterprise Manager. However, these configuration changes are not reflected in the Enterprise Manager Cloud Control Console until you refresh the WebLogic domain configuration within the console.

    To refresh the WebLogic domain, follow these steps:

    1. Navigate to the home page of the Oracle WebLogic domain that hosts Enterprise Manager.

    2. From the WebLogic Domain menu, select Refresh WebLogic Domain. The Refresh WebLogic Domain page appears.

    3. Follow the instructions on the Refresh WebLogic Domain page to refresh the WebLogic domain.


    WARNING:

    If you do not refresh the WebLogic domain, you will see the old OMS target on the WebLogic domain home page.

    (Applicable only for 12.1.01 to 12.1.0.2 Upgrade) If you have a JVM Agent deployed, then you will see the old OMS target even on the Deploy/Upgrade Diagnostic Agent : Select Targets page while upgrading the JVM Agent.

    Visible OMS Target Without Refreshing the WLS Domain

    Make sure you follow this step to clear the old OMS target from the Enterprise Manager Cloud Control Console.



    Caution:

    (Applicable only for 12.1.01 to 12.1.0.2 Upgrade) If you have any JVM targets associated with the old OMS, then even after you refresh the WebLogic domain, on the WebLogic domain home page, you will continue see the JVM target that was associated with the old OMS. This is an expected behavior. Surrounding text describes visible_jvm_target.gif.

    If you choose to either retain it for viewing historical data or delete it. To delete it, right-click the orphaned JVM target, and select Remove Target.


  5. Rename the following directories in the old OMS home (12.1.0.1 OMS home):


    Caution:

    Perform this step only if you had not applied patch 15951627, or if the patch had failed for some reason, as described for the INSTALL_UPDATES_SELECTION parameter in Table 4-2.

    • Rename the omsstup directory to omsstup_old in the following location:

      $<OLD_OMS_HOME>/install/unix/scripts/

    • Rename the bin directory to bin_old in the following location:

      $<OLD_OMS_HOME>/

    • Rename the wlserver_10.3 directory to wlserver_10.3_old in the following location:

      $<OLD_MW_HOME>

    If you do not rename the directories, then when you restart the upgraded OMS host, the Admin Server configured with the 12.1.0.1 OMS home starts, but neither the 12.1.0.1 OMS nor the upgraded 12.1.0.2 OMS run. This is more serious in a multi-OMS environment because the additional OMS instances continue to contact the Admin Server configured with the 12.1.0.1 OMS home instead of the 12.1.0.2 OMS home, and as a result, corrupt the OMS configuration.

  6. Upgrade the Management Agent that was installed with the old OMS (that is, central agent) immediately after upgrading the old OMS. For more information, refer to Chapter 5.

  7. (Optional) After upgrading, if you want to delete the old OMS home, then follow the instructions outlined in Appendix L

Upgrading Multi-OMS Environment

To upgrade an Enterprise Manager system of 12c Release 1 (12.1.0.1) that has multiple OMS, follow these steps:


WARNING:

Do not upgrade Enterprise Manager Cloud Control 12c Release 1 (12.1.0.1) while it is undergoing a 2-system upgrade from its earlier release. Wait until the upgrade completes fully because there might be some standalone Management Agents in status pending state while the upgrade is in progress.



Caution:

Ensure that you use VNC Server to connect to the remote host while upgrading the OMS and the Management Repository. Other tools, such as cygwin, putty, and so on, sometimes time out or do not allow new Xdisplay connections, thus resulting in upgrade failures.

  1. Upgrade the first OMS (where the Admin Server is running). You can use any of the upgrade approaches described in this guide — Upgrading OMS and Management Repository in Graphical Mode, Upgrading OMS and Management Repository in Silent Mode, Installing Software Now and Upgrading Later in Graphical Mode, or Installing Software Now and Upgrading Later in Silent Mode.


    Note:

    Always start the upgrade process with the first OMS, where the Admin Server is running, and not with any of the additional OMS instances.

    To identify the OMS where the Admin Server is running, run the following command on the OMS home and verify if the output displays the Admin Server details.

    $<OMS_HOME>/bin/emctl status oms -details

    You should see a similar output:

    Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.2.0 
    Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved
    Enter Enterprise Manager Root (SYSMAN) Password :
    Console Server Host : myhost.example.com
    .
    .
    .
    WLS Domain Information
    Domain Name : GCDomain
    Admin Server Host: myhost.example.com
    .
    .
    .
    

  2. After upgrading the first OMS in your system, on every other host where an additional OMS is running, invoke the Enterprise Manager Cloud Control Installation Wizard, and on the Installation Types screen, select Upgrade an Existing Enterprise Manager System, and then, select One System Upgrade. Then, select the additional OMS home you want to upgrade.