4 Upgrading Oracle Management Service and Oracle Management Repository to 13c Release 4

This chapter describes the different ways of upgrading your Oracle Management Service (OMS) and Oracle Management Repository (Management Repository) to 13c Release 4. Select the one that best suits your requirement, and follow the instructions outlined in the respective section. The upgrade instructions apply to single-OMS as well as multi-OMS environments.

This chapter describes the following:

Note:

  • If you have Oracle Management Service 12c Release 1 (12.1.0.1) [with or without Bundle Patch 1], 12c Release 2 (12.1.0.2), 12c Release 3 (12.1.0.3) or any pre-12c release such as 10g or 11g, then you need to first upgrade to 12c Release 5 (12.1.0.5) and 13c Release 2. After that, you can upgrade it to 13c Release 4.

  • The Oracle Management Agent releases that are supported for Enterprise Manager Cloud Control 13c Release 4 are 13c Release 4, 13c Release 3 and 13c Release 2. Therefore, if you have any earlier releases of Oracle Management Agent, before upgrading the Oracle Management Service to 13c Release 4, make sure you to upgrade your Oracle Management Agent to either 13c Release 2(13.2.0.0) or 13c Release 3(13.3.0.0) using the Agent Upgrade Console present within the Enterprise Manager Cloud Control Console.

  • If you are upgrading a multi-OMS environment, then Oracle recommends that you use the software-only upgrade approach as described in Upgrading the OMS and the Management Repository to 13c Release 4 Using the Software-Only Method in Graphical Mode or Upgrading the OMS and the Management Repository to 13c Release 4 Using the Software-Only Method in Silent Mode, as this approach minimizes the downtime of the OMS instances.

  • 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 Agent Upgrade Console. This is an expected behavior. For instructions to use the Agent Upgrade Console to upgrade Management Agents, see Upgrading Oracle Management Agents.

WARNING:

Do not install Enterprise Manager Cloud Control 13c on servers of SPARC series: T1000, T2000, T5xx0, and T3-*. For more information, see My Oracle Support note 1590556.1.

Upgrading the OMS and the Management Repository in Graphical Mode

Follow the steps below to upgrade your OMS and Management Repository to version 13c Release 4 using the graphical mode:

Note:

If you see an error message stating that you have not copied the emkey, do the following:

  • If your OMR is configured with a service name, then run the following command on the OMS you are about to upgrade. Here, <ORACLE_HOME> is the Oracle home of the OMS.

    <ORACLE_HOME>/bin/emctl config emkey -copy_to_repos_from_file -repos_conndesc '"(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=<>)(PORT=<>)))(CONNECT_DATA=(SERVICE_NAME=<>)))"' -repos_user SYSMAN [-repos_pwd <pwd> ] [-admin_pwd <pwd>] -emkey_file <oracle_home>/sysman/config/emkey.ora

  • If your OMR is not configured with a service name, then run the following command on the OMS you are about to upgrade. Here, <ORACLE_HOME> is the Oracle home of the OMS.

    <ORACLE_HOME>/bin/emctl config emkey -copy_to_repos_from_file -repos_host <host> -repos_port <port> -repos_sid <sid> -repos_user SYSMAN [-repos_pwd <pwd> ] [-admin_pwd <pwd>] -emkey_file <oracle_home>/sysman/config/emkey.ora

Here, the Management Repository details are details of the existing or old Management Repository. You will be prompted for the administration server password and the repository password if you do not explicitly specify them in the command line.

Note:

If you are upgrading a multi-OMS environment, 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 you are about to upgrade, and verify if the output displays the Admin Server details. Here, <ORACLE_HOME> is the Oracle home of the OMS.

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

You should see a similar output:

Oracle Enterprise Manager Cloud Control 13c Release 3
Copyright (c) 1996, 2018 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
.
.
.

Invoking the Enterprise Manager Cloud Control Installer in GUI Mode

Oracle strongly recommends that you back up the Management Repository, the OMS, the inventory, the Software Library, and other components that are critical to the functioning of Enterprise Manager. This will enable you to revert to the original contents if the upgrade fails.

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

./em13400_<platform>.bin [-invPtrLoc <absolute_path_to_oraInst.loc>]

Note:

  • For information about the additional, advanced options you can pass while invoking the installer, refer to Advanced Installer Options Supported for Installing an Enterprise Manager System in Graphical Mode.

  • To invoke the installation wizard on UNIX platforms, run ./em13400_<platform>.bin. To invoke on Microsoft Windows platforms, run setup_em13400_win64.exe.

  • While invoking the installer, ensure that you pass the invPtrLoc argument if the OMS you are upgrading was installed using the invPtrLoc argument.

  • The installer requires about 14 GB of hard disk space in the temporary directory. If your temporary directory does not have this space, then pass the -J-Djava.io.tmpdir parameter and provide an alternative directory where there is 14 GB of space.

    The directory specified by this parameter will also be used as the location for the Provisioning Advisor Framework (PAF) staging directory, which is used for copying the Software Library entities related to the deployment procedures. The PAF staging directory is used only for provisioning activities — entities are copied for a deployment procedure, and then, deleted once the deployment procedure ends.

    For example,

    ./em13400_linux64.bin -J-Djava.io.tmpdir=/u01/software/em13c/stage/

  • While upgrading on IBM AIX, if you see an error message stating that your JDK version in the middleware home is not of a supported version, then make sure you install the supported version mentioned in the message, and then invoke the installer passing the -skipJDKValidation argument.

    For example,

    ./em13400_<platform>.bin -skipJDKValidation

  • -invPtrLoc is not supported on Microsoft Windows.

Advanced Installer Options Supported for Installing an Enterprise Manager System in Graphical Mode

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

  • 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 -J-Djava.io.tmpdir option, and enter a unique custom location.

    For example,

    ./em13400_linux64.bin -J-Djava.io.tmpdir=/u01/install/em/STAGE/

    Note:

    /u01/install/em/STAGE/ directory should exists while using this option, else it will re-direct the tmp location to /var/tmp.
  • 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 required plug-ins from Plug-in Update.

      In addition, plug-ins produced by partners or customers are available for download from Enterprise Manager Extensibility Exchange .

    2. Invoke the installer with the following option and pass the location where the additional plug-ins have been downloaded:

      On UNIX platforms:

      ./em13400_<platform>.bin PLUGIN_LOCATION=<absolute_path_to_plugin_software_location>

      On Microsoft Windows platforms:

      setup_em13400_win64.exe PLUGIN_LOCATION=<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 starts automatically. You must start central agent manually after OMS upgrade is completed. If you do not want OMS to start automatically, then invoke the installer with START_OMS 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:

    ./em13400_<platform>.bin START_OMS=true START_AGENT=false

    To understand the limitations involved with this advanced option, see Limitations with the Advanced Installer Options Supported for Installing an Enterprise Manager System in Graphical Mode.

Limitations with the Advanced Installer Options Supported for Installing an Enterprise Manager System in Graphical Mode

When you use START_OMS and START_AGENT 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

START_AGENT=false

  1. Start the OMS:

    $<ORACLE_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 bin directory of the Oracle home of the OMS. For more information, see Downloading and Deploying the EM CLI Client in the Oracle Enterprise Manager Command Line Interface Guide.

START_OMS=true

START_AGENT=false

Start the Management Agent:

$<AGENT_HOME>/bin/emctl start agent

START_OMS=false

START_AGENT=true

  1. Start the OMS:

    $<ORACLE_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 bin directory of the Oracle home of the OMS. For more information, see Downloading and Deploying the EM CLI Client in the Oracle Enterprise Manager Command Line Interface Guide.

Enabling Oracle Configuration Manager

(Optional) On the My Oracle Support Details screen, enter your My Oracle Support credentials to enable Oracle Configuration Manager, and click Next. If you do not want to enable Oracle Configuration Manager now, click Next without entering any details, and go to Applying the Latest Software Updates.

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. For instructions, see Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.

Applying the Latest Software Updates

On the Software Updates screen, apply the latest software updates, including the latest PSU patches, click Next.

You can download the software updates in offline mode (if you do not have Internet connectivity) or online mode (if you have Internet connectivity). For instructions, see Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.

Running the Prerequisite Checks and Validating the Environment

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. Then click Next.

The installation wizard runs the prerequisite checks automatically when you come to this screen. The status of the prerequisite check can be either Warning, Failed, Succeeded, Not Executed, In Progress, or Pending.

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.

Selecting the Installation Type

On the Installation Types screen, select Upgrade an existing Enterprise Manager system. Select the OMS you want to upgrade, and click Next.

The installer performs only the software install with plug-ins and this step is part of the process. There is no actual upgrade in progress.

Configuring a Middleware Home and Validating the Host Name

On the Installation Details screen, do the following, and click Next.

  • Enter a new middleware home where the installer can automatically install Oracle WebLogic Server 12c Release 2 (12.2.1.3.0) and Java Development Kit 1.8.0_231 for you.

    For example, /u01/software/em13c/oraclehome

    Note:

    Ensure that the Middleware home you enter or validate 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.

  • 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.

Providing Database Connection Details

On the Database Connection Details screen, do the following, and click Next.

The installer performs only the software install with plug-ins and this step is part of the process. There is no actual upgrade in progress.

  • Enter the passwords for the SYS and SYSMAN user accounts of the database that houses the Management Repository for the selected OMS.

    Note:

    • The SYSMAN password must begin with a letter, contain at least 8 characters, one numeric value and may contain the following characters: $ # _ 

    • To change the password ,run <OMSORACLE_HOME>/bin/emctl config oms -change_repos_pwd -old_pwd <old_pwd> -new_pwd <new_pwd> on one of the OMSs.

    • After the upgrade you may run the same command to change the sysman password, to a password of your choice.

  • Confirm that you have backed up the Management Repository (although the installer checks only if you have backed up the Management Repository, Oracle strongly recommends that you back up the OMS, the inventory, the Software Library, and other components that are critical to the functioning of Enterprise Manager. This will enable you to revert to the original contents if the upgrade fails). As a prerequisite, you must back up the Management Repository before starting the upgrade process. If you have not already taken a backup, then do so immediately, and then return to the installer to continue with the upgrade.

  • If you have to stop the Enterprise Manager system for postupgrade maintenance, then select Disable DDMP Jobs to disable the DDMP jobs. If you do not plan to stop the Enterprise Manager system for postupgrade maintenance, and hence do not want to disable the DDMP jobs, then do not select the option.

    Deferred Data Migration (DDMP) is a post-upgrade activity to migrate the format of the data stored in an earlier release of Enterprise Manager to the format compatible with the upgraded Enterprise Manager system. The migration activity is essentially a job in Enterprise Manager that is submitted when the Oracle Management Repository gets upgraded, and is scheduled to run in the background when the upgraded Enterprise Manager system starts functioning.

    The time taken to migrate the data format depends on the volume of data available in your earlier release of Enterprise Manager. Therefore, if you have a large amount of data, then it takes longer to migrate.

    If you have to stop the Enterprise Manager system for postupgrade maintenance, then you can choose to disable the DDMP jobs now and run them later from the postupgrade console after the maintenance period ends and after the Enterprise Manager system becomes operational.

    To run the DDMP jobs later from the Post Upgrade Console, in the Enterprise Manager Cloud Control Console, from the Setup menu, select Manage Cloud Control, then select Post Upgrade Tasks.

Note:

If the installer finds that some plug-ins deployed in the previous release of Enterprise Manager are obsolete and are not supported in 13c Release 4, then you are prompted to first remove those plug-ins from the previous release. You can return to the installer and proceed with the upgrade only after removing those obsolete plug-ins.

To remove the obsolete plug-ins, follow these steps:

  1. Undeploy the obsolete plug-ins from the Management Agents. Next, undeploy them from the OMS instances. For instructions, see the chapter on Undeploying Plug-Ins in Oracle Enterprise Manager Cloud Control Administrator's Guide.

  2. Optionally, remove the binaries of these obsolete plug-ins from the Self Update Console. For instructions, see the chapter on Updating Cloud Control in Oracle Enterprise Manager Cloud Control Administrator's Guide.

Note:

If you have any JVM Diagnostics Engines (JVMD Engines) or Application Dependency and Performance Engines (ADP Engines) configured in your environment, then check whether they are up and running. If they are, then check whether the Admin Server is up and stop the JVMD Engines and the ADP Engines. Once the upgrade is successful, the JVMD Engines start automatically.

To check whether the Admin Server is running, run the following command from the OMS you are upgrading. Here, <ORACLE_HOME> is the Oracle home of the OMS.

<ORACLE_HOME>/bin/emctl status oms -details.

To stop the engines, on each OMS instance, run the following command from the OMS you are upgrading. Here, <ORACLE_HOME> is the Oracle home of the OMS.

<ORACLE_HOME>/bin/emctl extended oms adp stop -all.

Note:

For information about the various prerequisite checks that are run on the database at this point and how to fix them if they fail, see Prerequisites for Upgrading to Enterprise Manager Cloud Control 13c Release 4.

Upgrading or Migrating Plug-ins, or Deploying Dependent Plug-ins

On the Plug-In Upgrade screen, review the plug-ins that will experience one of the following effects, and click Next.

  • Upgraded when newer versions exist

  • Migrated when newer versions do not exist

  • Deployed when the plug-ins being upgraded have new dependencies, or when there are any new default plug-ins introduced with a release.

    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:

You might have a deprecated plug-in in your environment that can be upgraded to a plug-in version that is supported only in 13c Release 4, but not in any of the future releases. If such a deprecated plug-in is selected by default in this screen for upgrade, then you are prompted to evaluate your selection and decide whether or not you want to proceed with the upgrade of such plug-ins.

Note:

Before you proceed to the next screen, run the following command to stop all the associated OMS instances. Here, <ORACLE_HOME> is the Oracle home of the OMS.

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

Note:

  • If the newer versions do not exist in the Enterprise Manager software that you are using, but exist on Oracle Software Downloads, then you can choose to manually download them from Oracle Software Downloads and upgrade your existing plug-ins, instead of having them automatically migrated by default. To do so, follow these steps:

    1. Manually download the required plug-ins.

    2. Invoke the installer with the following option and pass the location where the additional plug-ins have been downloaded:

      On UNIX platforms:

      ./em13400_<platform>.bin PLUGIN_LOCATION=<absolute_path_to_plugin_software_location>

      On Microsoft Windows platforms:

      setup_em13400_win64.exe PLUGIN_LOCATION=<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.

    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.

  • If you see a message stating that you have unsupported plug-ins on the OMS or on some of the Management Agents, then follow the instructions outlined in the message to upgrade the plug-ins, and then retry upgrading the OMS.

Deploying Additional Plug-ins

On the Select Plug-ins 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, and click Next.

Note:

If you select a deprecated plug-in that is supported only in 13c Release 4, but not in any of the future releases, then you are prompted to evaluate your selection and decide whether or not you want to proceed with the deployment of such plug-ins.

Note:

If you want to install some plug-ins that are not listed on this screen, then follow these steps:

  1. Manually download the required plug-ins.

  2. Invoke the installer with the following option and pass the location where the additional plug-ins have been downloaded:

    On UNIX platforms:

    em13400_<platform>.bin INSTALL_SWONLY_WITH_PLUGINS=true PLUGIN_LOCATION=<absolute_path_to_plugin_software_location>

    On Microsoft Windows platforms:

    setup_em13400_win64.exe INSTALL_SWONLY_WITH_PLUGINS=true PLUGIN_LOCATION=<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.

Extending the Existing WebLogic Server Domain

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, and click Next.

The installer performs only the software install with plug-ins and this step is part of the process. There is no actual upgrade in progress.

  • Validate the Admin Server Host name, the Admin Server Port value and the WebLogic User Name, and enter the WebLogic user account password under WebLogic Password. This is required to create a new WebLogic domain (GCDomain) on the same port and host name as the Admin Server used by the earlier release of the OMS you are upgrading.

    Note:

    If you are upgrading an additional OMS, then the host name and port of the Admin Server configured for the first OMS that you have already upgraded, and also, the user name for the existing WebLogic user account will be populated automatically. You need to validate them, and then enter the password for the WebLogic 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:

    <OMS_INSTANCE_HOME>/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. This gc_inst directory must not be your old gc_inst directory of 13c Release 3 or 13c Release 2, therefore you need to enter a new directory location. If you enter the old gc_inst directory, then the installer will display a warning that the directory is not empty.

    For example, /u01/app/oracle/em13c/gc_instr2

    Make sure the path you enter leads up to the instance base directory, and is maintained outside the middleware home.

    Note:

    If you are installing on an NFS-mounted drive and creating the OMS instance base directory (gc_inst) on that NFS-mounted drive, then after you install, move the lock files from the NFS-mounted drive to a local file system location. Modify the lock file location in the httpd.conf file to map to a location on a local file system. For instructions, refer to Moving Lock Files from an NFS-Mounted Drive to a Local File System Location.

Moving Lock Files from an NFS-Mounted Drive to a Local File System Location
  1. If you installed on an NFS-mounted drive and created the OMS instance base directory (gc_inst) on that NFS-mounted drive, then move the lock files from the NFS-mounted drive to a local file system location. To do so, modify the lock files location in the httpd.conf file to map to a location on a local file system.
    1. Stop the OMS:

      <ORACLE_HOME>/bin/emctl stop oms

    2. Open the following file in the staging directory:

      Note:

      Oracle recommends you to take a backup of this file before editing it.

      <WEBTIER_INSTANCE_HOME>/user_projects/domains/GCDomain/config/fmwconfig/components/OHS/ohs<#>/httpd.conf

      For example,

      /u01/software/em13c/gc_inst/user_projects/domains/GCDomain/config/fmwconfig/components/OHS/ohs1/httpd.conf

    3. Search for sections related to the modules mpm_prefork_module and mpm_worker_module. In both these sections, modify the value for the LockFile parameter so that the path leads to a location on the local file system. If the directory does not already exist, then create it first, and then provide the path to that directory.
      <IfModule mpm_prefork_module>
      StartServers 5
      MinSpareServers 5
      MaxSpareServers 10
      MaxClients 150
      MaxRequestsPerChild 0
      AcceptMutex fcntl
      LockFile /u01/em/ohs_locks/http_lock
      </IfModule>
      ....
      <IfModule mpm_worker_module>
      StartServers 2
      MaxClients 150
      MinSpareThreads 25
      MaxSpareThreads 75
      ThreadsPerChild 25
      MaxRequestsPerChild 0
      AcceptMutex fcntl
      LockFile /u01/em/ohs_locks/http_lock
      </IfModule>b
      
    4. Save the changes.
    5. Copy the httpd.conf file from the staging directory to the runtime directory:

      cp <WEBTIER_INSTANCE_HOME>/user_projects/domains/GCDomain/config/fmwconfig/components/OHS/ohs<#>/httpd.conf <WEBTIER_INSTANCE_HOME>/user_projects/domains/GCDomain/config/fmwconfig/components/OHS/instances/ohs<#>/httpd.conf

      For example,

      cp /u01/software/em13c/gc_inst/user_projects/domains/GCDomain/config/fmwconfig/components/OHS/ohs1/httpd.conf /u01/software/em13c/gc_inst/user_projects/domains/GCDomain/config/fmwconfig/components/OHS/instances/ohs1/httpd.conf

    6. Start the OMS:

      <ORACLE_HOME>/bin/emctl start oms

For more information on upgrading additional Oracle management services, see step 4 in section Performing Postinstallation Tasks After Adding an Additional Oracle Management Service of the Oracle Enterprise Manager Cloud Control Basic Installation Guide.

Configuring the Shared Locations for Oracle BI Publisher

On the Enterprise Manager Shared Location Details screen, do the following, and click Next.

  • If you are upgrading an OMS that already has Oracle BI Publisher installed and configured in a shared location, then the fields for configuring Oracle BI Publisher are prefilled and grayed out. You can leave them as they are and proceed to the other sections of this screen.

    However, if you are upgrading an OMS that does not already have Oracle BI Publisher installed, or if you are upgrading an OMS that has Oracle BI Publisher installed but not configured in a shared location, then do the following:

    (i) Identify a shared location that you can use for Oracle BI Publisher.

    The existing shared location is auto populated. If you do not have an existing shared location, create a new one and ensure that it is visible on the host where you are installing the first OMS and also on other hosts where you plan to install additional OMS instances.

    At install time, for the installation to be successful, you can reserve approximately 400 MB of hard disk space for the shared directory. However, Oracle recommends that you scale it to at least 10 GB eventually, and ensure that it can be extended further in the future because the space utilization increases over a period of time as you install additional plug-ins and create more reports.

    Caution:

    If you already have a shared location that you were using for the Software Library or for staging gold images in the previous release of Enterprise Manager, then you can choose to use the same location. However, ensure that the directories within the shared location are unique for Oracle BI Publisher, Software Library, and staged gold images. For example, if you already are using the shared location /u01/software/examplehost/shrd/ where the Software Library is configured in /u01/software/examplehost/shrd/SW, then you can use the same location, but make sure the directory within this shared location for Oracle BI Publisher is /u01/software/examplehost/shrd/BIP.

    (ii) On this screen, select Configure a Shared Location for Oracle BI Publisher. Enter the following directory paths. Ensure that the user account that you are using to install the first OMS has read and write permission on these paths.

    Note:

    When you invoke the installer on Microsoft Windows, the Enterprise Manager Shared Location Details screen does not show the Config Volume and Cluster Volume options. This is an expected behavior.

    For Config Volume, enter the path leading up to the /config directory on the shared storage location where Oracle BI Publisher repository and configuration files can be stored. For example, /u01/software/examplehost/shrd/BIP/config

    For Cluster Volume, enter the path leading up to the /cluster directory on the shared storage location where Oracle BI Publisher scheduler storage can be maintained for Oracle BI Publisher to operate in a high-availability environment. For example, /u01/software/examplehost/shrd/BIP/cluster

    WARNING:

    Do not delete these directories after the installation. The directories are required for proper functioning of Oracle BI Publisher, and therefore will still be required after the installation.

  • Enable or disable the installed and configured Oracle BI Publisher. Enabling Oracle BI Publisher starts the software and keeps it ready for use within the Enterprise Manager system. Disabling Oracle BI Publisher leaves the software as it is without starting it.

    To enable Oracle BI Publisher, select Enable Oracle BI Publisher.

    Note:

    If you choose to disable Oracle BI Publisher during the installation, then you can enable it after the installation by running the following EM CTL command from the Oracle home of the upgraded OMS.

    $<ORACLE_HOME>/bin/emctl config oms -enable_bip

    For example,

    /u01/software/em13c/oraclehome/bin/emctl config oms -enable_bip

    The command only enables Oracle BI Publisher, but does not start it. To start it, run the following command from the Oracle home of the upgraded OMS.

    $<ORACLE_HOME>/bin/emctl start oms -bip_only

    /u01/software/em13c/oraclehome/bin/emctl start oms -bip_only

Configuring the Ports

On the Port Configuration Details screen, customize the ports to be used for the new components being added for this release, and click Next.

The ports for most components are automatically carried over from the previous release, and therefore, this screen lists only the ports for the new components being added for this release.

Note:

If all the ports on this screen appear as -1, then it indicates that the installer is unable to bind the ports on the host. To resolve this issue, exit the installer, verify the host name and the IP configuration of this host (ensure that the IP address of the host is not being used by another host), restart the installer, and try again.

You can enter a free custom port that is either within or outside the port range recommended by Oracle.

To verify if a port is free, run the following command:

  • On Unix:

    netstat -an | grep <port no>

  • On Microsoft Windows:

    netstat -an|findstr <port_no>

However, the custom port must be greater than 1024 and lesser than 65535. Alternatively, if you already have the ports predefined in a staticports.ini file and if you want to use those ports, then click Import staticports.ini file and select the file.

Note:

If the staticports.ini file is passed during installation, then by default, the ports defined in the staticports.ini file are displayed. Otherwise, the first available port from the recommended range is displayed.

The staticports.ini file is available in the following location:

<Software_Extracted_Location>/response

Reviewing the Upgrade Details

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

The installer performs only the software install with plug-ins and this step is part of the process. There is no actual upgrade in progress.

  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 Upgrade to begin the upgrade.

Note:

When performing an Upgrade and Transition to DR Readiness, ensure the Host Name displayed is the alias host name for OMS1. If it is not, navigate back to the Installation Details screen and ensure the Host Name is properly specified.

Monitoring the Upgrade Progress

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 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 Oracle home of the OMS to rerun the Configuration Assistant in silent mode. If the runConfig.sh script fails, raise a service request and contact Oracle Support.

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

    For example,

    /u01/software/em13c/oraclehome/oui/bin/runConfig.sh ORACLE_HOME=/u01/software/em13c/oraclehome 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.

  • If the Management Repository upgrade fails with the following error in the schemamanager logs, then restart the database, and then try the upgrade again.

    ORA-04020: deadlock detected while trying to lock object SYSMAN.MGMT_GLOBAL

Ending the Upgrade

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.

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.

Upgrading the Additional OMS Instances

If you have additional OMS instances, then start upgrading each of them sequentially by following Invoking the Enterprise Manager Cloud Control Installer in GUI Mode to Ending the Upgrade.

Upgrading the Management Agents

After upgrading all the OMS instances, upgrade the Management Agents, including the one that was installed with the first, old OMS (that is, central agent). For more information, refer to Upgrading Oracle Management Agents.

Note:

  • Oracle recommends that you upgrade your central agent immediately after upgrading your OMS instances. However, for some reason if you are unable to upgrade your central agent immediately after upgrading the OMS instances, then ensure that at least you apply the JDK 1.7u111 patch on your central agent. Otherwise, the targets of the GC WLS domain will not be monitored in the Enterprise Manager Cloud Control Console. This issue will not occur once the central agent is upgraded.

  • After upgrading the central agent, if you find the agent base directory of the upgraded central agent in the old Oracle Middleware home, and if you want to move it outside that old Oracle Middleware home, then follow the instructions outlined in Moving the Central Agent Base Directory Outside Oracle Middleware Home.

Upgrading the OMS and the Management Repository to 13c Release 4 in Silent Mode

Follow the steps below to upgrade your OMS and Management Repository to version 13c Release 4 using silent mode:

Note:

If you see an error message stating that you have not copied the emkey, do the following:

  • If your OMR is configured with a service name, then run the following command on the OMS you are about to upgrade. Here, <ORACLE_HOME> is the Oracle home of the OMS.

    <ORACLE_HOME>/bin/emctl config emkey -copy_to_repos_from_file -repos_conndesc '"(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=<>)(PORT=<>)))(CONNECT_DATA=(SERVICE_NAME=<>)))"' -repos_user <> [-repos_pwd <pwd> ] [-admin_pwd <pwd>] -emkey_file <oracle_home>/sysman/config/emkey.ora

  • If your OMR is not configured with a service name, then run the following command on the OMS you are about to upgrade. Here, <ORACLE_HOME> is the Oracle home of the OMS.

    <ORACLE_HOME>/bin/emctl config emkey -copy_to_repos_from_file -repos_host <host> -repos_port <port> -repos_sid <sid> -repos_user <username> [-repos_pwd <pwd> ] [-admin_pwd <pwd>] -emkey_file <oracle_home>/sysman/config/emkey.ora

Here, the Management Repository details are details of the existing or old Management Repository. You will be prompted for the administration server password and the repository password if you do not explicitly specify them in the command line.

Note:

If you are upgrading a multi-OMS environment, 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 you are about to upgrade, and verify if the output displays the Admin Server details. Here, <ORACLE_HOME> is the Oracle home of the OMS.

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

You should see a similar output:

Oracle Enterprise Manager Cloud Control 13c Release 3
Copyright (c) 1996, 2018 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
.
.
.

Note:

If the Management Repository upgrade fails with the following error in the schemamanager logs, then restart the database, and then try the upgrade again.

ORA-04020: deadlock detected while trying to lock object SYSMAN.MGMT_GLOBAL

Generating the Response File for Silent Installation

Invoke the installer and generate the response file you need to use for performing a silent upgrade:

./em13400_<platform>.bin -getResponseFileTemplates -outputLoc <absolute_path_to_a_directory_to_store_the_generated_response_file>

Note:

The command generates three response files. You must use only the upgrade.rsp file for this silent installation.

Editing the Response File for Silent Installation

Edit the upgrade.rsp response file and enter appropriate values for the parameters described in Editing the Response File for Upgrading Oracle Management Service and Oracle Management Repository in Silent Mode.

Note:

If you have any plug-ins that are obsolete and are not supported in 13c Release 4, then you must first remove those plug-ins from the previous release. You can proceed with the upgrade only after removing those obsolete plug-ins.

To remove the obsolete plug-ins, follow these steps:

  1. First, undeploy the obsolete plug-ins from the Management Agents. Next, undeploy them from the OMS instances. For instructions, see the chapter on managing plug-ins in Oracle Enterprise Manager Cloud Control Administrator's Guide.

  2. Finally, remove the binaries of these obsolete plug-ins from the Self Update Console. For instructions, see the chapter on updating cloud control in Oracle Enterprise Manager Cloud Control Administrator's Guide.

Invoking the Enterprise Manager Cloud Control Installer in Silent Mode

Invoke the installer in silent mode and pass the updated response file:

./em13400_<platform>.bin -silent -responseFile <absolute_path_to_the_directory_where_the_generated_and_updated_response_file_is_stored>/upgrade.rsp

Note:

  • To invoke the installation wizard on UNIX platforms, run ./em13400_<platform>.bin. To invoke on Microsoft Windows platforms, run setup_em13400_win64.exe.

  • For information about the additional, advanced options you can pass while invoking the installer, refer to Advanced Installer Options Supported for Installing an Enterprise Manager System in Silent Mode.

  • The installer requires about 14 GB of hard disk space in the temporary directory. If your temporary directory does not have this space, then pass the -J-Djava.io.tmpdir parameter and provide an alternative directory where there is 14 GB of space.

    The directory specified by this parameter will also be used as the location for the Provisioning Advisor Framework (PAF) staging directory, which is used for copying the Software Library entities related to the deployment procedures. The PAF staging directory is used only for provisioning activities — entities are copied for a deployment procedure, and then, deleted once the deployment procedure ends.

    For example,

    ./em13400_linux64.bin -J-Djava.io.tmpdir=/u01/software/em13c/stage/

  • While upgrading on IBM AIX, if you see an error message stating that your JDK version in the middleware home is not of a supported version, then make sure you install the supported version mentioned in the message, and then invoke the installer passing the -skipJDKValidation argument.

    For example,

    ./em13400_<platform>.bin -skipJDKValidation

  • If a prerequisite check fails reporting a missing package, then make sure you install the required package, and retry the installation. The installer validates the package name as well as the version, so make sure you install the packages of the minimum versions mentioned in Oracle Enterprise Manager Cloud Control Basic Installation Guide. To understand the logic the installer uses to verify these packages, see Oracle Enterprise Manager Cloud Control Basic Installation Guide.

Advanced Installer Options Supported for Installing an Enterprise Manager System in Silent Mode

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 START_AGENT 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:

./em13400_<platform>.bin START_OMS=true START_AGENT=false -silent -responseFile <absolute_path>/upgrade.rsp

To understand the limitations involved with this advanced option, see Limitations with the Advanced Installer Options Supported for Installing an Enterprise Manager System in Graphical Mode.

Upgrading the Additional OMS Instances

If you have additional OMS instances, then start upgrading each of them sequentially by following Step (1) to Step (3) as outlined in Upgrading the OMS and the Management Repository to 13c Release 4 in Silent Mode (this section.)

Upgrading the Management Agents

After upgrading all the OMS instances, upgrade the Management Agents, including the one that was installed with the first, old OMS (that is, central agent). For more information, refer to Upgrading Oracle Management Agents.

Note:

  • Oracle recommends that you upgrade your central agent immediately after upgrading your OMS instances. However, for some reason if you are unable to upgrade your central agent immediately after upgrading the OMS instances, then ensure that at least you apply the JDK 1.7u111 patch on your central agent. Otherwise, the targets of the GC WLS domain will not be monitored in the Enterprise Manager Cloud Control Console. This issue will not occur once the central agent is upgraded.

  • After upgrading the central agent, if you find the agent base directory of the upgraded central agent in the old Oracle Middleware home, and if you want to move it outside that old Oracle Middleware home, then follow the instructions outlined in Moving the Central Agent Base Directory Outside Oracle Middleware Home.

Upgrading the OMS and the Management Repository to 13c Release 4 Using the Software-Only Method in Graphical Mode Along With Plug-ins

This section explains how you can upgrade your OMS and Management Repository to version 13c Release 4 using the software-only method in graphical mode along with plug-ins.

Note:

  • This is the Oracle recommended approach for upgrade.

  • Upgrading the OMS and the Management Repository to 13c Release 4 using the Software-Only Method along with Plug-ins is not supported in Silent mode.

Using the software-only method, you essentially install the software binaries of Enterprise Manager Cloud Control 13c Release 4 at one point, and upgrade the earlier release of Enterprise Manager to the newly installed 13c Release 4 software binaries at a later point.

This upgrade approach is best suited for multi-OMS environments, as it minimizes the downtime of the OMS instances. This approach consists of three parts, mainly copying the software binaries, running the root.sh script, and configuring the software binaries. You can copy the software binaries on all the OMS hosts in parallel without shutting down the OMS instances. This not only saves time but also enables the earlier release of the OMS instances to remain up and running at this point. Once the software binaries are copied, you can shut down all the OMS instances, and configure the software binaries to upgrade the OMS instances, one after the other. Therefore, the downtime begins only when you start configuring the OMS instances, and not while copying the software binaries to the host.

In particular, this section covers the following:

Note:

If you see an error message stating that you have not copied the emkey, do the following:

  • If your OMR is configured with a service name, then run the following command on the OMS you are about to upgrade. Here, <ORACLE_HOME> is the Oracle home of the OMS.

    <ORACLE_HOME>/bin/emctl config emkey -copy_to_repos_from_file -repos_conndesc '"(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=<>)(PORT=<>)))(CONNECT_DATA=(SERVICE_NAME=<>)))"' -repos_user <> [-repos_pwd <pwd> ] [-admin_pwd <pwd>] -emkey_file <oracle_home>/sysman/config/emkey.ora

  • If your OMR is not configured with a service name, then run the following command on the OMS you are about to upgrade. Here, <ORACLE_HOME> is the Oracle home of the OMS.

    <ORACLE_HOME>/bin/emctl config emkey -copy_to_repos_from_file -repos_host <host> -repos_port <port> -repos_sid <sid> -repos_user <username> [-repos_pwd <pwd> ] [-admin_pwd <pwd>] -emkey_file <oracle_home>/sysman/config/emkey.ora

Here, the Management Repository details are details of the existing or old Management Repository. You will be prompted for the administration server password and the repository password if you do not explicitly specify them in the command line.

Note:

If you are upgrading a multi-OMS environment, 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 you are about to upgrade, and verify if the output displays the Admin Server details. Here, <ORACLE_HOME> is the Oracle home of the OMS.

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

You should see a similar output:

Oracle Enterprise Manager Cloud Control 13c Release 4
Copyright (c) 1996, 2019 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
[..]

Installing the Enterprise Manager Cloud Control 13c Release 4 Software Binaries in Graphical Mode Along with Plug-ins

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

Invoking the Enterprise Manager Cloud Control Installer for Installing Only the Software Binaries in GUI Mode Along with Plug-ins

Oracle strongly recommends that you back up the Management Repository, the OMS, the inventory, the Software Library, and other components that are critical to the functioning of Enterprise Manager. This will enable you to revert to the original contents if the upgrade fails. This will install software bits of the Enterprise Manager along with the applicable plugins.

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

./em13400_<platform>.bin INSTALL_SWONLY_WITH_PLUGINS=true[-invPtrLoc <absolute_path_to_oraInst.loc>]

Note:

  • The -invPtrLoc parameter is an optional parameter.

  • For information about the additional, advanced options you can pass while invoking the installer, refer to Advanced Installer Options Supported for Installing an Enterprise Manager System in Graphical Mode.

  • To invoke the installation wizard on UNIX platforms, run ./em13400_<platform>.bin

    For example:

    ./em13400_<platform>.bin INSTALL_SWONLY_WITH_PLUGINS=true[-invPtrLoc <absolute_path_to_oraInst.loc>]

    To invoke on Microsoft Windows platforms, run setup_em13400_win64.exe

    For example:

    setup_em13400_win64.exe INSTALL_SWONLY_WITH_PLUGINS=true

  • While invoking the installer, ensure that you pass the invPtrLoc argument if the OMS you are upgrading was installed using the invPtrLoc argument.

  • The installer requires about 14 GB of hard disk space in the temporary directory. If your temporary directory does not have this space, then pass the -J-Djava.io.tmpdir parameter and provide an alternative directory where there is 14 GB of space.

    The directory specified by this parameter will also be used as the location for the Provisioning Advisor Framework (PAF) staging directory, which is used for copying the Software Library entities related to the deployment procedures. The PAF staging directory is used only for provisioning activities — entities are copied for a deployment procedure, and then, deleted once the deployment procedure ends.

    For example,

    ./em13400_linux64.bin -J-Djava.io.tmpdir=/u01/software/em13c/stage/

  • While upgrading on IBM AIX, if you see an error message stating that your JDK version in the middleware home is not of a supported version, then make sure you install the supported version mentioned in the message, and then invoke the installer passing the -skipJDKValidation argument.

    For example,

    ./em13400_<platform>.bin INSTALL_SWONLY_WITH_PLUGINS=true -skipJDKValidation

Enabling Oracle Configuration Manager

(Optional) On the My Oracle Support Details screen, enter your My Oracle Support credentials to enable Oracle Configuration Manager, and click Next. If you do not want to enable Oracle Configuration Manager now, click Next without entering any details, and go to Applying the Latest Software Updates.

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. For instructions, see Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.

Applying the Latest Software Updates

On the Software Updates screen, apply the latest software updates, including the latest PSU patches, and click Next.

You can download the software updates in offline mode (if you do not have Internet connectivity) or online mode (if you have Internet connectivity). For instructions, see Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.

Running the Prerequisite Checks and Validating the Environment

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. Then click Next.

The installation wizard runs the prerequisite checks automatically when you come to this screen.

The status of the prerequisite check can be either Warning, Failed, Succeeded, Not Executed, In Progress, or Pending.

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.

Note:

If a prerequisite check fails reporting a missing package, then make sure you install the required package, and click Rerun. The installation wizard validates the package name as well as the version, so make sure you install the packages of the minimum versions mentioned in Oracle Enterprise Manager Cloud Control Basic Installation Guide. To understand the logic the installation wizard uses to verify these packages, see Oracle Enterprise Manager Cloud Control Basic Installation Guide.

Selecting the Installation Type

On the Installation Types screen, select Upgrade an existing Enterprise Manager system. Select the OMS you want to upgrade, and click Next.

The installer performs only the software install with plug-ins and this step is part of the process. There is no actual upgrade in progress.

Configuring a Middleware Home and Validating the Host Name

On the Installation Details screen, do the following, and click Next.

  • Enter a new middleware home where the installer can automatically install Oracle WebLogic Server 12c Release 2 (12.2.1.3.0) and Java Development Kit 1.8.0_231 for you.

    For example, /u01/software/em13c/oraclehome

    Note:

    Ensure that the Middleware home you enter or validate 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.

  • 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.

Providing Database Connection Details

On the Database Connection Details screen, do the following, and click Next.

The installer performs only the software install with plug-ins and this step is part of the process. There is no actual upgrade in progress.

  • Enter the passwords for the SYS and SYSMAN user accounts of the database that houses the Management Repository for the selected OMS.

    Note:

    • The SYSMAN password must begin with a letter, contain at least 8 characters, one numeric value and may contain the following characters: $ # _ 

    • To change the password ,run <OMSORACLE_HOME>/bin/emctl config oms -change_repos_pwd -old_pwd <old_pwd> -new_pwd <new_pwd> on one of the OMSs.

    • After the upgrade you may run the same command to change the sysman password, to a password of your choice.

  • Confirm that you have backed up the Management Repository (although the installer checks only if you have backed up the Management Repository, Oracle strongly recommends that you back up the OMS, the inventory, the Software Library, and other components that are critical to the functioning of Enterprise Manager. This will enable you to revert to the original contents if the upgrade fails). As a prerequisite, you must back up the Management Repository before starting the upgrade process. If you have not already taken a backup, then do so immediately, and then return to the installer to continue with the upgrade.

  • If you have to stop the Enterprise Manager system for postupgrade maintenance, then select Disable DDMP Jobs to disable the DDMP jobs. If you do not plan to stop the Enterprise Manager system for postupgrade maintenance, and hence do not want to disable the DDMP jobs, then do not select the option.

    Deferred Data Migration (DDMP) is a post-upgrade activity to migrate the format of the data stored in an earlier release of Enterprise Manager to the format compatible with the upgraded Enterprise Manager system. The migration activity is essentially a job in Enterprise Manager that is submitted when the Oracle Management Repository gets upgraded, and is scheduled to run in the background when the upgraded Enterprise Manager system starts functioning.

    The time taken to migrate the data format depends on the volume of data available in your earlier release of Enterprise Manager. Therefore, if you have a large amount of data, then it takes longer to migrate.

    If you have to stop the Enterprise Manager system for postupgrade maintenance, then you can choose to disable the DDMP jobs now and run them later from the postupgrade console after the maintenance period ends and after the Enterprise Manager system becomes operational.

    To run the DDMP jobs later from the Post Upgrade Console, in the Enterprise Manager Cloud Control Console, from the Setup menu, select Manage Cloud Control, then select Post Upgrade Tasks.

Note:

If the installer finds that some plug-ins deployed in the previous release of Enterprise Manager are obsolete and are not supported in 13c Release 4, then you are prompted to first remove those plug-ins from the previous release. You can return to the installer and proceed with the upgrade only after removing those obsolete plug-ins.

To remove the obsolete plug-ins, follow these steps:

  1. Undeploy the obsolete plug-ins from the Management Agents. Next, undeploy them from the OMS instances. For instructions, see the chapter on Undeploying Plug-Ins in Oracle Enterprise Manager Cloud Control Administrator's Guide.

  2. Optionally, remove the binaries of these obsolete plug-ins from the Self Update Console. For instructions, see the chapter on Updating Cloud Control in Oracle Enterprise Manager Cloud Control Administrator's Guide.

Note:

If you have any JVM Diagnostics Engines (JVMD Engines) or Application Dependency and Performance Engines (ADP Engines) configured in your environment, then check whether they are up and running. If they are, then check whether the Admin Server is up and stop the JVMD Engines and the ADP Engines. Once the upgrade is successful, the JVMD Engines start automatically.

To check whether the Admin Server is running, run the following command from the OMS you are upgrading. Here, <ORACLE_HOME> is the Oracle home of the OMS.

<ORACLE_HOME>/bin/emctl status oms -details.

To stop the engines, on each OMS instance, run the following command from the OMS you are upgrading. Here, <ORACLE_HOME> is the Oracle home of the OMS.

<ORACLE_HOME>/bin/emctl extended oms adp stop -all.

Note:

For information about the various prerequisite checks that are run on the database at this point and how to fix them if they fail, see Prerequisites for Upgrading to Enterprise Manager Cloud Control 13c Release 4.

Upgrading or Migrating Plug-ins, or Deploying Dependent Plug-ins

On the Plug-In Upgrade screen, review the plug-ins that will experience one of the following effects, and click Next.

  • Upgraded when newer versions exist

  • Migrated when newer versions do not exist

  • Deployed when the plug-ins being upgraded have new dependencies, or when there are any new default plug-ins introduced with a release.

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.

The installer performs only the software install with plug-ins and this step is part of the process. There is no actual upgrade in progress.

Note:

You might have a deprecated plug-in in your environment that can be upgraded to a plug-in version that is supported only in 13c Release 4, but not in any of the future releases. If such a deprecated plug-in is selected by default in this screen for upgrade, then you are prompted to evaluate your selection and decide whether or not you want to proceed with the upgrade of such plug-ins.

Note:

  • If the newer versions do not exist in the Enterprise Manager software that you are using, but exist on Oracle Software Downloads, then you can choose to manually download them from there and upgrade your existing plug-ins, instead of having them automatically migrated by default. To do so, follow these steps:

    1. Manually download the required plug-ins from Plug-in Update.

      In addition, plug-ins produced by partners or customers are available for download from Enterprise Manager Extensibility Exchange.

    2. Invoke the installer with the following option and pass the location where the additional plug-ins have been downloaded:

      On UNIX platforms:

      em13400_<platform>.bin INSTALL_SWONLY_WITH_PLUGINS=true PLUGIN_LOCATION=<absolute_path_to_plugin_software_location>

      On Microsoft Windows platforms:

      setup_em13400_win64.exe INSTALL_SWONLY_WITH_PLUGINS=true PLUGIN_LOCATION=<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.

    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.

  • If you see a message stating that you have unsupported plug-ins on the OMS or on some of the Management Agents, then follow the instructions outlined in the message to upgrade the plug-ins, and then retry upgrading the OMS.

Deploying Additional Plug-ins

On the Select Plug-ins 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, and click Next.

Note:

If you select a deprecated plug-in that is supported only in 13c Release 4, but not in any of the future releases, then you are prompted to evaluate your selection and decide whether or not you want to proceed with the deployment of such plug-ins.

Note:

If you want to install some plug-ins that are not listed on this screen, then follow these steps:

  1. Manually download the required plug-ins.

  2. Invoke the installer with the following option and pass the location where the additional plug-ins have been downloaded:

    On UNIX platforms:

    em13400_<platform>.bin INSTALL_SWONLY_WITH_PLUGINS=true PLUGIN_LOCATION=<absolute_path_to_plugin_software_location>

    On Microsoft Windows platforms:

    setup_em13400_win64.exe INSTALL_SWONLY_WITH_PLUGINS=true PLUGIN_LOCATION=<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.

Extending the Existing WebLogic Server Domain

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, and click Next.

The installer performs only the software install with plug-ins and this step is part of the process. There is no actual upgrade in progress.

  • Validate the Admin Server Host name, the Admin Server Port value and the WebLogic User Name, and enter the WebLogic user account password under WebLogic Password. This is required to create a new WebLogic domain (GCDomain) on the same port and host name as the Admin Server used by the earlier release of the OMS you are upgrading.

    Note:

    If you are upgrading an additional OMS, then the host name and port of the Admin Server configured for the first OMS that you have already upgraded, and also, the user name for the existing WebLogic user account will be populated automatically. You need to validate them, and then enter the password for the WebLogic 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:

    <OMS_INSTANCE_HOME>/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. This gc_inst directory must not be your old gc_inst directory of 13c Release 3 or 13c Release 2, therefore you need to enter a new directory location. If you enter the old gc_inst directory, then the installer will display a warning that the directory is not empty.

    For example, /u01/app/oracle/em13c/gc_instr2

    Make sure the path you enter leads up to the instance base directory, and is maintained outside the middleware home.

    Note:

    If you are installing on an NFS-mounted drive and creating the OMS instance base directory (gc_inst) on that NFS-mounted drive, then after you install, move the lock files from the NFS-mounted drive to a local file system location. Modify the lock file location in the httpd.conf file to map to a location on a local file system. For instructions, refer to Moving Lock Files from an NFS-Mounted Drive to a Local File System Location.

Moving Lock Files from an NFS-Mounted Drive to a Local File System Location
  1. If you installed on an NFS-mounted drive and created the OMS instance base directory (gc_inst) on that NFS-mounted drive, then move the lock files from the NFS-mounted drive to a local file system location. To do so, modify the lock files location in the httpd.conf file to map to a location on a local file system.
    1. Stop the OMS:

      <ORACLE_HOME>/bin/emctl stop oms

    2. Open the following file in the staging directory:

      Note:

      Oracle recommends you to take a backup of this file before editing it.

      <WEBTIER_INSTANCE_HOME>/user_projects/domains/GCDomain/config/fmwconfig/components/OHS/ohs<#>/httpd.conf

      For example,

      /u01/software/em13c/gc_inst/user_projects/domains/GCDomain/config/fmwconfig/components/OHS/ohs1/httpd.conf

    3. Search for sections related to the modules mpm_prefork_module and mpm_worker_module. In both these sections, modify the value for the LockFile parameter so that the path leads to a location on the local file system. If the directory does not already exist, then create it first, and then provide the path to that directory.
      <IfModule mpm_prefork_module>
      StartServers 5
      MinSpareServers 5
      MaxSpareServers 10
      MaxClients 150
      MaxRequestsPerChild 0
      AcceptMutex fcntl
      LockFile /u01/em/ohs_locks/http_lock
      </IfModule>
      ....
      <IfModule mpm_worker_module>
      StartServers 2
      MaxClients 150
      MinSpareThreads 25
      MaxSpareThreads 75
      ThreadsPerChild 25
      MaxRequestsPerChild 0
      AcceptMutex fcntl
      LockFile /u01/em/ohs_locks/http_lock
      </IfModule>b
      
    4. Save the changes.
    5. Copy the httpd.conf file from the staging directory to the runtime directory:

      cp <WEBTIER_INSTANCE_HOME>/user_projects/domains/GCDomain/config/fmwconfig/components/OHS/ohs<#>/httpd.conf <WEBTIER_INSTANCE_HOME>/user_projects/domains/GCDomain/config/fmwconfig/components/OHS/instances/ohs<#>/httpd.conf

      For example,

      cp /u01/software/em13c/gc_inst/user_projects/domains/GCDomain/config/fmwconfig/components/OHS/ohs1/httpd.conf /u01/software/em13c/gc_inst/user_projects/domains/GCDomain/config/fmwconfig/components/OHS/instances/ohs1/httpd.conf

    6. Start the OMS:

      <ORACLE_HOME>/bin/emctl start oms

For more information on upgrading additional Oracle management services, see step 4 in section Performing Postinstallation Tasks After Adding an Additional Oracle Management Service of the Oracle Enterprise Manager Cloud Control Basic Installation Guide.

Configuring the Shared Locations for Oracle BI Publisher

On the Enterprise Manager Shared Location Details screen, do the following, and click Next.

  • If you are upgrading an OMS that already has Oracle BI Publisher installed and configured in a shared location, then the fields for configuring Oracle BI Publisher are prefilled and grayed out. You can leave them as they are and proceed to the other sections of this screen.

    However, if you are upgrading an OMS that does not already have Oracle BI Publisher installed, or if you are upgrading an OMS that has Oracle BI Publisher installed but not configured in a shared location, then do the following:

    (i) Identify a shared location that you can use for Oracle BI Publisher.

    The existing shared location is auto populated. If you do not have an existing shared location, create a new one and ensure that it is visible on the host where you are installing the first OMS and also on other hosts where you plan to install additional OMS instances.

    At install time, for the installation to be successful, you can reserve approximately 400 MB of hard disk space for the shared directory. However, Oracle recommends that you scale it to at least 10 GB eventually, and ensure that it can be extended further in the future because the space utilization increases over a period of time as you install additional plug-ins and create more reports.

    Caution:

    If you already have a shared location that you were using for the Software Library or for staging gold images in the previous release of Enterprise Manager, then you can choose to use the same location. However, ensure that the directories within the shared location are unique for Oracle BI Publisher, Software Library, and staged gold images. For example, if you already are using the shared location /u01/software/examplehost/shrd/ where the Software Library is configured in /u01/software/examplehost/shrd/SW, then you can use the same location, but make sure the directory within this shared location for Oracle BI Publisher is /u01/software/examplehost/shrd/BIP.

    (ii) On this screen, select Configure a Shared Location for Oracle BI Publisher. Enter the following directory paths. Ensure that the user account that you are using to install the first OMS has read and write permission on these paths.

    Note:

    When you invoke the installer on Microsoft Windows, the Enterprise Manager Shared Location Details screen does not show the Config Volume and Cluster Volume options. This is an expected behavior.

    For Config Volume, enter the path leading up to the /config directory on the shared storage location where Oracle BI Publisher repository and configuration files can be stored. For example, /u01/software/examplehost/shrd/BIP/config

    For Cluster Volume, enter the path leading up to the /cluster directory on the shared storage location where Oracle BI Publisher scheduler storage can be maintained for Oracle BI Publisher to operate in a high-availability environment. For example, /u01/software/examplehost/shrd/BIP/cluster

    WARNING:

    Do not delete these directories after the installation. The directories are required for proper functioning of Oracle BI Publisher, and therefore will still be required after the installation.

  • Enable or disable the installed and configured Oracle BI Publisher. Enabling Oracle BI Publisher starts the software and keeps it ready for use within the Enterprise Manager system. Disabling Oracle BI Publisher leaves the software as it is without starting it.

    To enable Oracle BI Publisher, select Enable Oracle BI Publisher.

    Note:

    If you choose to disable Oracle BI Publisher during the installation, then you can enable it after the installation by running the following EM CTL command from the Oracle home of the upgraded OMS.

    $<ORACLE_HOME>/bin/emctl config oms -enable_bip

    For example,

    /u01/software/em13c/oraclehome/bin/emctl config oms -enable_bip

    The command only enables Oracle BI Publisher, but does not start it. To start it, run the following command from the Oracle home of the upgraded OMS.

    $<ORACLE_HOME>/bin/emctl start oms -bip_only

    /u01/software/em13c/oraclehome/bin/emctl start oms -bip_only

Configuring the Ports

On the Port Configuration Details screen, customize the ports to be used for the new components being added for this release, and click Next.

The ports for most components are automatically carried over from the previous release, and therefore, this screen lists only the ports for the new components being added for this release.

Note:

If all the ports on this screen appear as -1, then it indicates that the installer is unable to bind the ports on the host. To resolve this issue, exit the installer, verify the host name and the IP configuration of this host (ensure that the IP address of the host is not being used by another host), restart the installer, and try again.

You can enter a free custom port that is either within or outside the port range recommended by Oracle.

To verify if a port is free, run the following command:

  • On Unix:

    netstat -an | grep <port no>

  • On Microsoft Windows:

    netstat -an|findstr <port_no>

However, the custom port must be greater than 1024 and lesser than 65535. Alternatively, if you already have the ports predefined in a staticports.ini file and if you want to use those ports, then click Import staticports.ini file and select the file.

Note:

If the staticports.ini file is passed during installation, then by default, the ports defined in the staticports.ini file are displayed. Otherwise, the first available port from the recommended range is displayed.

The staticports.ini file is available in the following location:

<Software_Extracted_Location>/response

Reviewing the Upgrade Details

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

The installer performs only the software install with plug-ins and this step is part of the process. There is no actual upgrade in progress.

  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 Upgrade to begin the upgrade.

Note:

When performing an Upgrade and Transition to DR Readiness, ensure the Host Name displayed is the alias host name for OMS1. If it is not, navigate back to the Installation Details screen and ensure the Host Name is properly specified.
Monitoring the Upgrade Progress

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

The installer performs only the software install with plug-ins and this step is part of the process. There is no actual upgrade in progress.

Running the 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 Oracle home of the OMS you installed in Installing the Enterprise Manager Cloud Control 13c Release 4 Software Binaries in Graphical Mode.

$<ORACLE_HOME>/allroot.sh

For example,

/u01/software/em13c/oraclehome/allroot.sh

If you have additional OMS instances, then run this script on those additional OMS hosts as well.

Note:

If you do not have the permission to run this script at this point, you can always run it after configuring the software binaries, but make sure you run it before you start upgrading the Management Agents.

Installing Additional Plug-ins

If you need to install additional plug-ins, then you can choose to manually download them from Plug-in Update . Pass the location of the downloaded additional plug-ins to the installer with the plugin_location parameter

Configuring the Enterprise Manager Cloud Control 13c Release 4 Software Binaries Along With Plug-ins

To configure the Enterprise Manager in upgrade mode:

  1. Stop the OMS from the old home, using emctl command.

    <OLD OMS home>/bin/emctl stop oms –all

    For example:

    u01/software/emoldoms/oraclehome/bin/emctl stop oms -all

  2. To Configure the Enterprise Manager, run the ConfigureGC from new 13c Release 4 middleware home using the command:

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

    For 13c Release 4 on Microsoft Windows platforms, run the ConfigureGC.bat script with INSTALL_SWONLY_WITH_PLUGINS=true.
    ConfigureGC.bat INSTALL_SWONLY_WITH_PLUGINS=true
    For any additional OMS upgrade on Microsoft Windows platform, use the following:
    ConfigureGC.bat INSTALL_SWONLY_WITH_PLUGINS=true CONFIGURE_BIP=false

    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 Oracle home of the OMS to rerun the Configuration Assistant in silent mode. If the runConfig.sh script fails, raise a service request and contact Oracle Support.

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

    For Example,

    /u01/software/em13c/oraclehome/oui/bin/runConfig.sh ORACLE_HOME=/u01/software/em13c/oraclehome 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.

    If the Management Repository upgrade fails with the following error in the schema manager logs, then restart the database, and then try the upgrade again.

    ORA-04020: deadlock detected while trying to lock object SYSMAN.MGMT_GLOBAL

Upgrading the OMS and the Management Repository to 13c Release 4 Using the Software-Only Method in Graphical Mode

This section explains how you can upgrade your OMS and Management Repository to version 13c Release 4 using the software-only method in graphical mode.

Using the software-only method, you essentially install the software binaries of Enterprise Manager Cloud Control 13c Release 4 at one point, and upgrade the earlier release of Enterprise Manager to the newly installed 13c Release 4 software binaries at a later point.

This upgrade approach is best suited for multi-OMS environments, as it minimizes the downtime of the OMS instances. This approach consists of three parts, mainly copying the software binaries, running the root.sh script, and configuring the software binaries. You can copy the software binaries on all the OMS hosts in parallel without shutting down the OMS instances. This not only saves time but also enables the earlier release of the OMS instances to remain up and running at this point. Once the software binaries are copied, you can shut down all the OMS instances, and configure the software binaries to upgrade the OMS instances, one after the other. Therefore, the downtime begins only when you start configuring the OMS instances, and not while copying the software binaries to the host.

In particular, this section covers the following:

Note:

If you see an error message stating that you have not copied the emkey, do the following:

  • If your OMR is configured with a service name, then run the following command on the OMS you are about to upgrade. Here, <ORACLE_HOME> is the Oracle home of the OMS.

    <ORACLE_HOME>/bin/emctl config emkey -copy_to_repos_from_file -repos_conndesc '"(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=<>)(PORT=<>)))(CONNECT_DATA=(SERVICE_NAME=<>)))"' -repos_user <> [-repos_pwd <pwd> ] [-admin_pwd <pwd>] -emkey_file <oracle_home>/sysman/config/emkey.ora

  • If your OMR is not configured with a service name, then run the following command on the OMS you are about to upgrade. Here, <ORACLE_HOME> is the Oracle home of the OMS.

    <ORACLE_HOME>/bin/emctl config emkey -copy_to_repos_from_file -repos_host <host> -repos_port <port> -repos_sid <sid> -repos_user <username> [-repos_pwd <pwd> ] [-admin_pwd <pwd>] -emkey_file <oracle_home>/sysman/config/emkey.ora

Here, the Management Repository details are details of the existing or old Management Repository. You will be prompted for the administration server password and the repository password if you do not explicitly specify them in the command line.

Note:

If you are upgrading a multi-OMS environment, 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 you are about to upgrade, and verify if the output displays the Admin Server details. Here, <ORACLE_HOME> is the Oracle home of the OMS.

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

You should see a similar output:

Oracle Enterprise Manager Cloud Control 13c Release 4
Copyright (c) 1996, 2019 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
[…]

Installing the Enterprise Manager Cloud Control 13c Release 4 Software Binaries in Graphical Mode

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

Invoking the Enterprise Manager Cloud Control Installer for Installing Only the Software Binaries in GUI Mode

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

./em13400_<platform>.bin [-invPtrLoc <absolute_path_to_oraInst.loc>]

Note:

  • To invoke the installation wizard on UNIX platforms, run ./em13400_<platform>.bin. To invoke on Microsoft Windows platforms, run setup_em13400_win64.exe.

  • While invoking the installer, ensure that you pass the invPtrLoc argument if the OMS you are upgrading was installed using the invPtrLoc argument.

  • -invPtrLoc is not supported on Microsoft Windows.

  • The installer requires about 14 GB of hard disk space in the temporary directory. If your temporary directory does not have this space, then pass the -J-Djava.io.tmpdir parameter and provide an alternative directory where there is 14 GB of space.

    The directory specified by this parameter will also be used as the location for the Provisioning Advisor Framework (PAF) staging directory, which is used for copying the Software Library entities related to the deployment procedures. The PAF staging directory is used only for provisioning activities — entities are copied for a deployment procedure, and then, deleted once the deployment procedure ends.

    For example,

    ./em13400_linux64.bin -J-Djava.io.tmpdir=/u01/software/em13c/stage/

Note:

While installing on IBM AIX, if you see an error message stating that your JDK version in the middleware home is not of a supported version, then make sure you install the supported version mentioned in the message, and then invoke the installer passing the -skipJDKValidation argument.

For example,

./em13400_<platform>.bin -skipJDKValidation

Enabling Oracle Configuration Manager

(Optional) On the My Oracle Support Details screen, enter your My Oracle Support credentials to enable Oracle Configuration Manager, and click Next. If you do not want to enable Oracle Configuration Manager now, click Next without entering any details, and go to Applying the Latest Software Updates.

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. For instructions, see Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.

Applying the Latest Software Updates

On the Software Updates screen, apply the latest software updates, including the latest PSU patches, and click Next.

You can download the software updates in offline mode (if you do not have Internet connectivity) or online mode (if you have Internet connectivity). For instructions, see Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.

Running the Prerequisite Checks and Validating the Environment

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. Then click Next.

The installation wizard runs the prerequisite checks automatically when you come to this screen.

The status of the prerequisite check can be either Warning, Failed, Succeeded, Not Executed, In Progress, or Pending.

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.

Note:

If a prerequisite check fails reporting a missing package, then make sure you install the required package, and click Rerun. The installation wizard validates the package name as well as the version, so make sure you install the packages of the minimum versions mentioned in Oracle Enterprise Manager Cloud Control Basic Installation Guide. To understand the logic the installation wizard uses to verify these packages, see Oracle Enterprise Manager Cloud Control Basic Installation Guide.

Selecting the Installation Type

On the Installation Types screen, select Install software only, and click Next.

Configuring a Middleware Home, Installing the Central Agent, and Validating the Host Name

On the Installation Details screen, do the following, and click Next.

  1. Enter a new middleware home where the installer can automatically install Oracle WebLogic Server 12c Release 2 (12.2.1.3.0) and Java Development Kit 1.8.0_231 for you.

    For example, /u01/software/em13c/oraclehome

    Note:

    Ensure that the Middleware home you enter or validate 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.

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

    For example, /u01/software/em13c/agentbasedir

    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.
Reviewing the Installation Details

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.

Monitoring the Installation Progress

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

Ending the Installation

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.

Deinstalling the Management Agent and Deleting the Agent Base Directory

Deinstall the Management Agent and delete the agent base directory you created in Step (2) of Configuring a Middleware Home, Installing the Central Agent, and Validating the Host Name. For instructions, see Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.

The Management Agent you installed and the agent base directory you created in Step 10 (b) is essentially for a fresh installation, and is not used while upgrading Management Agents using the Agent Upgrade Console.

Copying the Software Binaries to the Additional OMS Hosts in Silent Mode

If you have additional OMS instances, then copy the software binaries on those additional OMS hosts as well by following steps outlined in this section (Installing the Enterprise Manager Cloud Control 13c Release 4 Software Binaries in Graphical Mode).

Running the 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 Oracle home of the OMS you installed in Installing the Enterprise Manager Cloud Control 13c Release 4 Software Binaries in Graphical Mode.

$<ORACLE_HOME>/allroot.sh

For example,

/u01/software/em13c/oraclehome/allroot.sh

If you have additional OMS instances, then run this script on those additional OMS hosts as well.

Note:

If you do not have the permission to run this script at this point, you can always run it after configuring the software binaries, but make sure you run it before you start upgrading the Management Agents.

Configuring the Enterprise Manager Cloud Control 13c Release 4 Software Binaries in Graphical Mode

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

Invoking the Enterprise Manager Cloud Control Installer for Configuring the Software Binaries in GUI Mode

Invoke the installation wizard by running the following script from the Oracle home of the OMS you installed in Installing the Enterprise Manager Cloud Control 13c Release 4 Software Binaries in Graphical Mode.

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

Note:

Advanced Script Options Supported for Software-Only Upgrade to Enterprise Manager Cloud Control

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. Custom WebLogic Domain name is not supported.

  • 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 START_AGENT 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:

    $<ORACLE_HOME>/sysman/install/ConfigureGC.sh START_OMS=true START_AGENT=false

    For example,

    /u01/software/em13c/oraclehome/sysman/install/ConfigureGC.sh START_OMS=true START_AGENT=false

    To understand the limitations involved with this advanced option, see Limitations with the Advanced Installer Options Supported for Installing an Enterprise Manager System in Graphical Mode.

Selecting the Installation Type

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 you want to upgrade.
  3. Click Next.
Providing Database Connection Details

On the Database Connection Details screen, do the following, and click Next.

  • Enter the passwords for the SYS and SYSMAN user accounts of the database that houses the Management Repository for the selected OMS.

    Note:

    • The SYSMAN password must begin with a letter, contain at least 8 characters, one numeric value and may contain the following characters: $ # _ 

    • To change the password ,run <OMSORACLE_HOME>/bin/emctl config oms -change_repos_pwd -old_pwd <old_pwd> -new_pwd <new_pwd> on one of the OMSs.

    • After the upgrade you may run the same command to change the sysman password, to a password of your choice.

  • Confirm that you have backed up the Management Repository (although the installer checks only if you have backed up the Management Repository, Oracle strongly recommends that you back up the OMS, the inventory, the Software Library, and other components that are critical to the functioning of Enterprise Manager. This will enable you to revert to the original contents if the upgrade fails). As a prerequisite, you must back up the Management Repository before starting the upgrade process. If you have not already taken a backup, then do so immediately, and then return to the installer to continue with the upgrade.

  • If you have to stop the Enterprise Manager system for postupgrade maintenance, then select Disable DDMP Jobs to disable the DDMP jobs. If you do not plan to stop the Enterprise Manager system for postupgrade maintenance, and hence do not want to disable the DDMP jobs, then do not select the option.

    Deferred Data Migration (DDMP) is a post-upgrade activity to migrate the format of the data stored in an earlier release of Enterprise Manager to the format compatible with the upgraded Enterprise Manager system. The migration activity is essentially a job in Enterprise Manager that is submitted when the Oracle Management Repository gets upgraded, and is scheduled to run in the background when the upgraded Enterprise Manager system starts functioning.

    The time taken to migrate the data format depends on the volume of data available in your earlier release of Enterprise Manager. Therefore, if you have a large amount of data, then it takes longer to migrate.

    If you have to stop the Enterprise Manager system for postupgrade maintenance, then you can choose to disable the DDMP jobs now and run them later from the postupgrade console after the maintenance period ends and after the Enterprise Manager system becomes operational.

    To run the DDMP jobs later from the Post Upgrade Console, in the Enterprise Manager Cloud Control Console, from the Setup menu, select Manage Cloud Control, then select Post Upgrade Tasks.

Note:

If the installer finds that some plug-ins deployed in the previous release of Enterprise Manager are obsolete and are not supported in 13c Release 4, then you are prompted to first remove those plug-ins from the previous release. You can return to the installer and proceed with the upgrade only after removing those obsolete plug-ins.

To remove the obsolete plug-ins, follow these steps:

  1. Undeploy the obsolete plug-ins from the Management Agents. Next, undeploy them from the OMS instances. For instructions, see the chapter on Undeploying Plug-Ins in Oracle Enterprise Manager Cloud Control Administrator's Guide.

  2. Optionally, remove the binaries of these obsolete plug-ins from the Self Update Console. For instructions, see the chapter on Updating Cloud Control in Oracle Enterprise Manager Cloud Control Administrator's Guide.

Note:

If you have any JVM Diagnostics Engines (JVMD Engines) or Application Dependency and Performance Engines (ADP Engines) configured in your environment, then check whether they are up and running. If they are, then check whether the Admin Server is up and stop the JVMD Engines and the ADP Engines. Once the upgrade is successful, the JVMD Engines start automatically.

To check whether the Admin Server is running, run the following command from the OMS you are upgrading. Here, <ORACLE_HOME> is the Oracle home of the OMS.

<ORACLE_HOME>/bin/emctl status oms -details.

To stop the engines, on each OMS instance, run the following command from the OMS you are upgrading. Here, <ORACLE_HOME> is the Oracle home of the OMS.

<ORACLE_HOME>/bin/emctl extended oms adp stop -all.

Note:

For information about the various prerequisite checks that are run on the database at this point and how to fix them if they fail, see Prerequisites for Upgrading to Enterprise Manager Cloud Control 13c Release 4.

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 required plug-ins from Plug-in Update.

    In addition, plug-ins produced by any partners or customers are available for download from Enterprise Manager Extensibility Exchange.

  3. Invoke the ConfigureGC.sh script with the following parameter, and pass the location where the additional plug-ins have been downloaded. Here, <ORACLE_HOME> is the Oracle home of the OMS host you installed in Installing the Enterprise Manager Cloud Control 13c Release 4 Software Binaries in Graphical Mode (or the middleware home).

    <ORACLE_HOME>/sysman/install/ConfigureGC.sh PLUGIN_LOCATION=<absolute_path_to_plugin_sw>

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

Upgrading or Migrating Plug-ins, or Deploying Dependent Plug-ins

On the Plug-In Upgrade screen, review the plug-ins that will experience one of the following effects, and click Next.

  • Upgraded when newer versions exist

  • Migrated when newer versions do not exist

  • Deployed when the plug-ins being upgraded have new dependencies, or when there are any new default plug-ins introduced with a release.

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:

You might have a deprecated plug-in in your environment that can be upgraded to a plug-in version that is supported only in 13c Release 2 but not in any of the future releases. If such a deprecated plug-in is selected by default in this screen for upgrade, then you are prompted to evaluate your selection and decide whether or not you want to proceed with the upgrade of such plug-ins.

Important:

Before you proceed to the next screen, run the following command to stop all the associated OMS instances. Here, <ORACLE_HOME> is the Oracle home of the OMS.

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

Note:

  • If the newer versions do not exist in the Enterprise Manager software that you are using, but exist on Plug-in Update, then you can choose to manually download them from there and upgrade your existing plug-ins, instead of having them automatically migrated by default. To do so, follow these steps:

    1. Manually download the required plug-ins from Plug-in Update.

      In addition, if you want to download any partner or customer plug-ins, then download them from Enterprise Manager Extensibility Exchange.

    2. Invoke the ConfigureGC.sh script with the following parameter, and pass the location where the additional plug-ins have been downloaded. Here, <ORACLE_HOME> is the Oracle home of the OMS you installed in Installing the Enterprise Manager Cloud Control 13c Release 4 Software Binaries in Graphical Mode (or the middleware home).

      $<ORACLE_HOME>/sysman/install/ConfigureGC.sh PLUGIN_LOCATION=<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.

  • If you see a message stating that you have unsupported plug-ins on the OMS or on some of the Management Agents, then follow the instructions outlined in the message to upgrade the plug-ins, and then retry upgrading the OMS.

Deploying Additional Plug-ins

On the Select Plug-ins 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, and click Next.

Note:

If you select a deprecated plug-in that is supported only in 13c Release 4, but not in any of the future releases, then you are prompted to evaluate your selection and decide whether or not you want to proceed with the deployment of such plug-ins.

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 required plug-ins from Plug-in Update.

    In addition, if you want to download any partners or customers plug-ins, then download them from Enterprise Manager Extensibility Exchange.

  2. Invoke the installer with the following parameter, and pass the location where the plug-ins have been downloaded. Here, <ORACLE_HOME> is the Oracle home of the OMS you installed in Installing the Enterprise Manager Cloud Control 13c Release 4 Software Binaries in Graphical Mode.

    $<ORACLE_HOME>/sysman/install/ConfigureGC.sh PLUGIN_LOCATION=<absolute_path_to_plugin_software_location>

Extending the Existing WebLogic Server Domain

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, and click Next.

  • Validate the Admin Server Host name, the Admin Server Port value and the WebLogic User Name, and enter the WebLogic user account password under WebLogic Password. This is required to create a new WebLogic domain (GCDomain) on the same port and host name as the Admin Server used by the earlier release of the OMS you are upgrading.

    Note:

    If you are upgrading an additional OMS, then the host name and port of the Admin Server configured for the first OMS that you have already upgraded, and also, the user name for the existing WebLogic user account will be populated automatically. You need to validate them, and then enter the password for the WebLogic 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. This gc_inst directory must not be your old gc_inst directory of 13c Release 3 or 13c Release 2, therefore you need to enter a new directory location. If you enter the old gc_inst directory, then the installer will display a warning that the directory is not empty.

    For example, /u01/software/em13c/oraclehome

    Make sure the path you enter leads up to the instance base directory, and is maintained outside the middleware home.

    Note:

    If you are installing on an NFS-mounted drive and creating the OMS instance base directory (gc_inst) on that NFS-mounted drive, then after you install, move the lock files from the NFS-mounted drive to a local file system location. Modify the lock file location in the httpd.conf file to map to a location on a local file system. For instructions, refer to Moving Lock Files from an NFS-Mounted Drive to a Local File System Location.

    Note:

    If you want to change the Oracle WebLogic Server password or the Node Manager password, see My Oracle Support note 1450798.1.

Configuring the Shared Locations for Oracle BI Publisher

On the Enterprise Manager Shared Location Details screen, do the following:

  1. If you are upgrading an OMS that already has Oracle BI Publisher installed and configured in a shared location, then the fields for configuring Oracle BI Publisher are prefilled and grayed out. You can leave them as they are and proceed to the other sections of this screen.

    However, if you are upgrading an OMS that does not already have Oracle BI Publisher installed, or if you are upgrading an OMS that has Oracle BI Publisher installed but not configured in a shared location, then do the following:

    (i) Identify a shared location that you can use for Oracle BI Publisher.

    If you do not have an existing shared location, create a new one and ensure that it is visible on the host where you are installing the first OMS and also on other hosts where you plan to install additional OMS instances.

    At install time, for the installation to be successful, you can reserve approximately 400 MB of hard disk space for the shared directory. However, Oracle recommends that you scale it to at least 10 GB eventually, and ensure that it can be extended further in the future because the space utilization increases over a period of time as you install additional plug-ins and create more reports.

    Caution:

    If you already have a shared location that you were using for the Software Library or for staging gold images in the previous release of Enterprise Manager, then you can choose to use the same location. However, ensure that the directories within the shared location are unique for Oracle BI Publisher, Software Library, and staged gold images. For example, if you already are using the shared location /u01/software/examplehost/shrd/ where the Software Library is configured in /u01/software/examplehost/shrd/SW, then you can use the same location, but make sure the directory within this shared location for Oracle BI Publisher is /u01/software/examplehost/shrd/BIP.

    (ii) On this screen, select Configure a Shared Location for Oracle BI Publisher. Enter the following directory paths. Ensure that the user account that you are using to install the first OMS has read and write permission on these paths.

    Note:

    When you invoke the installer on Microsoft Windows, the Enterprise Manager Shared Location Details screen does not show the Config Volume and Cluster Volume options. This is an expected behavior.

    For Config Volume, enter the path leading up to the /config directory on the shared storage location where Oracle BI Publisher repository and configuration files can be stored. For example, /u01/software/examplehost/shrd/BIP/config

    For Cluster Volume, enter the path leading up to the /cluster directory on the shared storage location where Oracle BI Publisher scheduler storage can be maintained for Oracle BI Publisher to operate in a high-availability environment. For example, /u01/software/examplehost/shrd/BIP/cluster

    WARNING:

    Do not delete these directories after the installation. The directories are required for proper functioning of Oracle BI Publisher, and therefore are required during the installation and also after the installation.

  2. Enable or disable the installed and configured Oracle BI Publisher. Enabling Oracle BI Publisher starts the software and keeps it ready for use within the Enterprise Manager system. Disabling Oracle BI Publisher leaves the software as it is without starting it.

    To enable Oracle BI Publisher, select Enable Oracle BI Publisher.

    Note:

    If you choose to disable Oracle BI Publisher during the installation, then you can enable it after the installation by running the following EM CTL command from the Oracle home of the upgraded OMS.

    $<ORACLE_HOME>/bin/emctl config oms -enable_bip

    For example,

    /u01/software/em13c/oraclehome/bin/emctl config oms -enable_bip

    The command only enables Oracle BI Publisher, but does not start it. To start it, run the following command from the Oracle home of the upgraded OMS.

    $<ORACLE_HOME>/bin/emctl start oms -bip_only

    /u01/software/em13c/oraclehome/bin/emctl start oms -bip_only

Configuring the Ports

On the Port Configuration Details screen, customize the ports to be used for the new components being added for this release. The ports for most components are automatically carried over from the previous release, and therefore, this screen lists only the ports for the new components being added for this release.

Note:

If all the ports on this screen appear as -1, then it indicates that the installer is unable to bind the ports on the host. To resolve this issue, exit the installer, verify the host name and the IP configuration of this host (ensure that the IP address of the host is not being used by another host), restart the installer, and try again.

You can enter a free custom port that is either within or outside the port range recommended by Oracle.

To verify if a port is free, run the following command:

  • On Unix:

    netstat -an | grep <port no>

  • On Microsoft Windows:

    netstat -an|findstr <port_no>

However, the custom port must be greater than 1024 and lesser than 65535. Alternatively, if you already have the ports predefined in a staticports.ini file and if you want to use those ports, then click Import staticports.ini file and select the file.

Note:

If the staticports.ini file is passed during installation, then by default, the ports defined in the staticports.ini file are displayed. Otherwise, the first available port from the recommended range is displayed.

The staticports.ini file is available in the following location:

<Software_Extracted_Location>/response

Reviewing the Upgrade Details

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.

Monitoring the Upgrade Progress

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 Oracle home of the OMS to rerun the Configuration Assistant in silent mode. If the runConfig.sh script fails, raise a service request and contact Oracle Support.

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

    For example,

    /u01/software/em13c/oraclehome/oui/bin/runConfig.sh ORACLE_HOME=/u01/software/em13c/oraclehome MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

    Note:

    For Microsoft Windows platforms, invoke runConfig.bat script.

    If the runConfig.sh script fails after the above steps, fix the issue and re-run the runConfig command. Re-running the script will start from the failure point. If the issue still exists, perform a triage, check the relevant log files and try to resolve the issue. If you still see the runConfig script failure, please contact Oracle Support for further assistance.

  • If the Management Repository upgrade fails with the following error in the schemamanager logs, then restart the database, and then try the upgrade again.

    ORA-04020: deadlock detected while trying to lock object SYSMAN.MGMT_GLOBAL

Ending the Upgrade

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.

Upgrading the Additional OMS Instances

If you have additional OMS instances, then start upgrading each of them sequentially by following steps outlined in this section (Configuring the Enterprise Manager Cloud Control 13c Release 4 Software Binaries in Graphical Mode).

Upgrading the Management Agents

After upgrading all the OMS instances, upgrade the Management Agents, including the one that was installed with the first, old OMS (that is, central agent).For more information, refer to Upgrading Oracle Management Agents.

Note:

  • Oracle recommends that you upgrade your central agent immediately after upgrading your OMS instances. However, for some reason if you are unable to upgrade your central agent immediately after upgrading the OMS instances, then ensure that at least you apply the JDK 1.7u111 patch on your central agent. Otherwise, the targets of the GC WLS domain will not be monitored in the Enterprise Manager Cloud Control Console. This issue will not occur once the central agent is upgraded.

  • After upgrading the central agent, if you find the agent base directory of the upgraded central agent in the old Oracle Middleware home, and if you want to move it outside that old Oracle Middleware home, then follow the instructions outlined in Moving the Central Agent Base Directory Outside Oracle Middleware Home.

  • Oracle Enterprise Manager now supports Oracle Linux host administration feature without YAST dependency. However, to get complete solution for this issue, your agent and OMS must be upgraded to 13.4.0.0.0 or higher. In absence of either upgrade, system will continue to behave as it did before and not support the new feature.

Upgrading the OMS and the Management Repository to 13c Release 4 Using the Software-Only Method in Silent Mode

This section explains how you can upgrade your OMS and Management Repository to version 13c Release 4 using the software-only method in silent mode.

Using the software-only method, you essentially install the software binaries of Enterprise Manager Cloud Control 13c Release 4 at one point, and upgrade the earlier release of Enterprise Manager to the newly installed 13c Release 4 software binaries at a later point.

This upgrade approach is best suited for multi-OMS environments, as it minimizes the downtime of the OMS instances. This approach consists of three parts, mainly copying the software binaries, running the root.sh script, and configuring the software binaries. You can copy the software binaries on all the OMS hosts in parallel without shutting down the OMS instances. This not only saves time but also enables the earlier release of the OMS instances to remain up and running at this point. Once the software binaries are copied, you can shut down all the OMS instances, and configure the software binaries to upgrade the OMS instances, one after the other. Therefore, the downtime begins only when you start configuring the OMS instances, and not while copying the software binaries to the host.

In particular, this section covers the following:

Note:

If you see an error message stating that you have not copied the emkey, do the following:

  • If your OMR is configured with a service name, then run the following command on the OMS you are about to upgrade. Here, <ORACLE_HOME> is the Oracle home of the OMS.

    <ORACLE_HOME>/bin/emctl config emkey -copy_to_repos_from_file -repos_conndesc '"(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=<>)(PORT=<>)))(CONNECT_DATA=(SERVICE_NAME=<>)))"' -repos_user <> [-repos_pwd <pwd> ] [-admin_pwd <pwd>] -emkey_file <oracle_home>/sysman/config/emkey.ora

  • If your OMR is not configured with a service name, then run the following command on the OMS you are about to upgrade. Here, <ORACLE_HOME> is the Oracle home of the OMS.

    <ORACLE_HOME>/bin/emctl config emkey -copy_to_repos_from_file -repos_host <host> -repos_port <port> -repos_sid <sid> -repos_user <username> [-repos_pwd <pwd> ] [-admin_pwd <pwd>] -emkey_file <oracle_home>/sysman/config/emkey.ora

Here, the Management Repository details are details of the existing or old Management Repository. You will be prompted for the administration server password and the repository password if you do not explicitly specify them in the command line.

Note:

If you are upgrading a multi-OMS environment, 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 you are about to upgrade, and verify if the output displays the Admin Server details. Here, <ORACLE_HOME> is the Oracle home of the OMS.

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

You should see a similar output:

Oracle Enterprise Manager Cloud Control 13c Release 4 
Copyright (c) 1996, 2018 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
[…]

Installing the Enterprise Manager Cloud Control 13c Release 4 Software Binaries in Silent Mode

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

Generating the Response File for Software-Only Installation in Silent Mode

Invoke the installer and generate the response file you need to use for performing a silent software-only installation:

./em13400_<platform>.bin -getResponseFileTemplates -outputLoc <absolute_path_to_a_directory_to_store_the_generated_response_file>

Note:

The command generates three response files. You must use only the software_only.rsp file for this silent software-only installation.

Editing the Response File for Software-Only Installation in Silent Mode

Edit the software_only.rsp file and enter appropriate values for the parameters described in Table 4-2.

Table 4-2 Editing the software_only.rsp Response File for Software-Only Installation in Silent Mode

Parameter Data Type Double Quotes Required for Values? Description

UNIX_GROUP_NAME

String

Yes

(Required only when central inventory does not exist) Enter the name of the UNIX group you belong to.

For example, "dba".

INVENTORY_LOCATION

String

Yes

(Required only when central inventory does not exist and if the OMS you are upgrading was installed using the invPtrLoc argument) Enter the absolute path to the Central Inventory.

For example, "/scratch/oracle/oraInventory".

SECURITY_UPDATES_VIA_MYORACLESUPPORT

Boolean

Yes

  • Enter TRUE if you want to download and install security updates. Then, enter the credentials for the following parameters in double quotes:

    MYORACLESUPPORT_USERNAME

    MYORACLESUPPORT_PASSWORD

  • Enter FALSE if you do not want to download and install security updates:

DECLINE_SECURITY_UPDATES

Boolean

No

  • Enter TRUE if you want to decline the security updates. In this case, you should have entered FALSE for SECURITY_UPDATES_VIA_MYORACLESUPPORT.

  • Enter FALSE if you do not want to decline the security updates. In this case, you should have entered TRUE for SECURITY_UPDATES_VIA_MYORACLESUPPORT.

INSTALL_UPDATES_SELECTION

String

Yes

By default, this parameter 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 parameter to "download". Then, enter the credentials for the following parameters in double quotes:

    MYORACLESUPPORT_USERNAME_FOR_SOFTWAREUPDATES

    MYORACLESUPPORT_PASSWORD_FOR_SOFTWAREUPDATES

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

    For this option, as a prerequisite, you must have already downloaded the software updates. For instructions, seeOracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.

ORACLE_MIDDLEWARE_HOME_LOCATION

String

Yes

Upgrade to 13c Release 4 is an out-of-place upgrade, therefore enter a new middleware home where the installer can automatically install Oracle WebLogic Server 12c Release 2 (12.2.1.3.0) and JDK 1.8.0_231.

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

For example, /u01/software/em13c/oraclehome

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.

AGENT_BASE_DIR

String

Yes

Enter the absolute path to the agent base directory, a location outside the Oracle Middleware home where the Management Agent can be installed. You will eventually remove this Management Agent from the host because you will upgrade the earlier release's Management Agent using the Agent Upgrade Console. However, for the software binaries to be successfully copied, you need to have this parameter and specify a valid location so that the Management Agent binaries can be copied, thereby allowing the installation to go through successfully.

For example, /u01/software/em13c/agentbasedir

Ensure that this location is empty and has write permission. Also ensure that it is always maintained outside the Oracle Middleware home.

Note: (Only for Microsoft Windows) Ensure that the number of characters in the agent base directory path does not exceed 25 characters. For example, the agent base directory path C:\Oracle\Agent\ containing only 16 characters is acceptable. However, C:\Oracle\ManagementAgent\13c\new containing more than 25 characters is not acceptable.

ORACLE_HOSTNAME

String

Yes

Enter a fully qualified domain name that is registered in the DNS and is accessible from other network hosts, or enter an alias host name that is defined in the /etc/hosts file on all the OMS instances at this site.

The host name must resolve to the local host because the host name is used for the local Oracle WebLogic Server as well as the Oracle Management Service. Do not provide a remote host or a load balancer virtual host in this field. Do not enter an IP address. Do not use underscores in the name. Short names are allowed, but you will see a warning, so Oracle recommends that you enter a fully qualified domain name instead.

If you do not mention the host name, the installation wizard will proceed further, honoring the host name it automatically detects for that host.

Installing the Software Binaries in Silent Mode

To copy the software binaries in silent mode, invoke the installer in the following way:

./em13400_<platform>.bin -silent -responseFile <absolute_path_to_the_directory_where_the_generated_and_updated_response_file_is_stored>/software_only.rsp [-invPtrLoc <absolute_path_to_oraInst.loc>]

Note:

  • To invoke the installation wizard on UNIX platforms, run ./em13400_<platform>.bin. To invoke on Microsoft Windows platforms, run setup_em13400_win64.exe.

  • For information about the additional, advanced options you can pass while invoking the installer, refer to Advanced Installer Options Supported for Installing an Enterprise Manager System in Silent Mode.

  • The installer requires about 14 GB of hard disk space in the temporary directory. If your temporary directory does not have this space, then pass the -J-Djava.io.tmpdir parameter and provide an alternative directory where there is 14 GB of space.

    The directory specified by this parameter will also be used as the location for the Provisioning Advisor Framework (PAF) staging directory, which is used for copying the Software Library entities related to the deployment procedures. The PAF staging directory is used only for provisioning activities — entities are copied for a deployment procedure, and then, deleted once the deployment procedure ends.

    For example,

    ./em13400_linux64.bin -J-Djava.io.tmpdir=/u01/software/em13c/stage/

  • While installing on IBM AIX, if you see an error message stating that your JDK version in the middleware home is not of a supported version, then make sure you install the supported version mentioned in the message, and then invoke the installer passing the -skipJDKValidation argument.

    For example,

    ./em13400_<platform>.bin -skipJDKValidation

Running the 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 Oracle home of the OMS you installed in Installing the Enterprise Manager Cloud Control 13c Release 4 Software Binaries in Silent Mode.

$<ORACLE_HOME>/allroot.sh

For example,

/u01/software/em13c/oraclehome/allroot.sh

If you have additional OMS instances, then run this script on those additional OMS hosts as well.

Note:

If you do not have the permission to run this script at this point, you can always run it after configuring the software binaries, but make sure you run it before you start upgrading the Management Agents.

Deinstalling the Management Agent and Deleting the Agent Base Directory

Deinstall the Management Agent and delete the agent base directory you created. For instructions, see Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.

The Management Agent you installed and the agent base directory you created is essentially for a fresh installation, and is not used while upgrading Management Agents using the Agent Upgrade Console.

Download and Copy Software Binaries to the Additional OMS Hosts in Silent Mode

If you have additional OMS instances, then download the software binaries from Oracle Software Downloads site and copy them into the additional OMS hosts by following steps outlined in Installing the Enterprise Manager Cloud Control 13c Release 4 Software Binaries in Silent Mode.

Configuring the Enterprise Manager Cloud Control 13c Release 4 Software Binaries in Silent Mode

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

Note:

If the Management Repository upgrade fails with the following error in the schemamanager logs, then restart the database, and then try the upgrade again.

ORA-04020: deadlock detected while trying to lock object SYSMAN.MGMT_GLOBAL

Editing the Response File for Configuring the Software Binaries in Silent Mode

Access the upgrade.rsp file that you generated in Generating the Response File for Software-Only Installation in Silent Mode while generating the software_only.rsp file. Edit the upgrade.rsp file and enter appropriate values for the parameters described in Editing the Response File for Upgrading Oracle Management Service and Oracle Management Repository in Silent Mode.

Note:

If you have any plug-ins that are obsolete and are not supported in 13c Release 4, then you must first remove those plug-ins from the previous release. You can proceed with the upgrade only after removing those obsolete plug-ins.

To remove the obsolete plug-ins, follow these steps:

  1. First, undeploy the obsolete plug-ins from the Management Agents. Next, undeploy them from the OMS instances. For instructions, see the chapter on managing plug-ins in Oracle Enterprise Manager Cloud Control Administrator's Guide.

  2. Finally, remove the binaries of these obsolete plug-ins from the Self Update Console. For instructions, see the chapter on updating cloud control in Oracle Enterprise Manager Cloud Control Administrator's Guide.

Configuring the Software Binaries in Silent Mode

Configure the software binaries by invoking the ConfigureGC.sh script from the Oracle home of the OMS you installed in Installing the Software Binaries in Silent Mode, and passing the response file you edited in the previous step.

$<ORACLE_HOME>/sysman/install/ConfigureGC.sh -silent -responseFile <absolute_path_to_the_directory_where_the_generated_and_updated_response_file_is_stored>/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 required plug-ins from Plug-in Update.

    In addition, plug-ins produced by partners or customers are available for download from Enterprise Manager Extensibility Exchange.

  3. Invoke the ConfigureGC.sh script with the following parameter, and pass the location where the additional plug-ins have been downloaded. Here, <ORACLE_HOME> is the Oracle home of the OMS you installed in Installing the Enterprise Manager Cloud Control 13c Release 4 Software Binaries in Silent Mode:

    <ORACLE_HOME>/sysman/install/ConfigureGC.sh -silent PLUGIN_LOCATION=<absolute_path_to_plugin_sw>

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

Upgrading the Additional OMS Instances

If you have additional OMS instances, then start upgrading each of them sequentially by following steps outlined in Editing the Response File for Configuring the Software Binaries in Silent Mode and Configuring the Software Binaries in Silent Mode.

Upgrading the Management Agents

After upgrading all the OMS instances, upgrade the Management Agents, including the one that was installed with the first, old OMS (that is, central agent). For more information, refer to Upgrading Oracle Management Agents.

Note:

  • Oracle recommends that you upgrade your central agent immediately after upgrading your OMS instances. However, for some reason if you are unable to upgrade your central agent immediately after upgrading the OMS instances, then ensure that at least you apply the JDK 1.7u111 patch on your central agent. Otherwise, the targets of the GC WLS domain will not be monitored in the Enterprise Manager Cloud Control Console. This issue will not occur once the central agent is upgraded.

  • After upgrading the central agent, if you find the agent base directory of the upgraded central agent in the old Oracle Middleware home, and if you want to move it outside that old Oracle Middleware home, then follow the instructions outlined in Moving the Central Agent Base Directory Outside Oracle Middleware Home.

Upgrading the OMS and any Additional OMSs in Parallel using the Software-Only Method in Graphical Mode Along with Plug-ins

Follow the steps below to upgrade multiple Oracle Management Services in Parallel to version 13c Release 4:

Note:

Always start the upgrade process with the first OMS, where the Admin Server (Primary OMS) 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 you are about to upgrade, and verify if the output displays the Admin Server details. Here, <ORACLE_HOME> is the Oracle home of the OMS.

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

You should see a similar output:

Oracle Enterprise Manager Cloud Control 13c Release 4
Copyright (c) 1996, 2019 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
[…]

Performing Prerequisites

Perform the following prerequisites:

  1. Ensure that all Oracle Management Agents in your enterprise are version 13.2.0.0.0 or greater.

    To find agents versions lower than 13.2.0.0.0 run the following SQL on the repository database, as a user with the Administrator role:
    select mt.target_name||' Agent Version='|| mtp.property_value from 
    mgmt_target_properties mtp , mgmt_targets mt where 
    mt.target_type='oracle_emd' and mt.target_guid = mtp.target_guid and 
    mtp.property_name='Version' and mtp.property_value < '13.2.0.0.0'
  2. Undeploy all the obsolete plug-ins from Admin (Primary) OMS.

    For instructions, see Undeploy Obsolete Plug-ins from Prerequisites for Upgrading to Enterprise Manager Cloud Control 13c Release 4 chapter.

  3. Run prerequisite checks on the repository:

    Step 1: Upgrading your Repository to a Supported Version

    Step 2: Invoking the Enterprise Manager Cloud Control Installer

    Step 3: Selecting the Installation Type

    Step 4: Providing Database Connection Details

    Step 5: Selecting the Deployment Size

    Step 6: Running the Prerequisite Checks

    Step 7: Evaluating the Correction Types

Step 1: Upgrading your Repository to a Supported Version

Refer to Database Version Requirements from Prerequisites for Installing an Enterprise Manager System.

Ensure that the existing database is a certified database as mentioned in the Enterprise Manager certification matrix available on My Oracle Support. To access the Enterprise Manager certification matrix and identify whether your database is a certified database, follow these steps in Accessing the Enterprise Manager Certification Matrix.

Alternatively, the database can be a database instance created with a preconfigured Management Repository using the database templates offered by Oracle. For information about creating a database instance with a preconfigured Management Repository using the database templates offered by Oracle, refer to Creating a Database Instance with Preconfigured Repository Using Database Templates. Ensure that this database is dedicated to Enterprise Manager.

The database configuration types that are supported are pluggable database (PDB), lone-pluggable database (Lone-PDB), and non-container database (Non-CDB).

Step 2: Invoking the Enterprise Manager Cloud Control Installer

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

./em13400_<platform>.bin [-invPtrLoc <absolute_path_to_oraInst.loc>] EMPREREQ_KIT=true

Note:

  • To invoke the installation wizard on UNIX platforms, run ./em13400_<platform>.bin.

  • To invoke on Microsoft Windows platforms, run setup_em13400_win64.exe.

  • While invoking the installer, ensure that you pass the invPtrLoc argument if the OMS you are upgrading was installed using the invPtrLoc argument.

  • -invPtrLoc is not supported on Microsoft Windows.

  • The installer requires about 14 GB of hard disk space in the temporary directory. If your temporary directory does not have this space, then pass the -J-Djava.io.tmpdir parameter and provide an alternative directory where there is 14 GB of space.

Step 3: Selecting the Installation Type

On the Installation Types screen, select Upgrade an existing Enterprise Manager system and click Next.

Step 4: Providing Database Connection Details

On the Database Connection Details screen, do the following, and click Next.

The installer performs only the software install with plug-ins and this step is part of the process. There is no actual upgrade in progress.

  • Enter the passwords for the SYS and SYSMAN user accounts of the database that houses the Management Repository for the selected OMS.

  • Confirm that you have backed up the Management Repository (although the installer checks only if you have backed up the Management Repository, Oracle strongly recommends that you back up the OMS, the inventory, the Software Library, and other components that are critical to the functioning of Enterprise Manager. This will enable you to revert to the original contents if the upgrade fails). As a prerequisite, you must back up the Management Repository before starting the upgrade process. If you have not already taken a backup, then do so immediately, and then return to the installer to continue with the upgrade.

  • If you have to stop the Enterprise Manager system for postupgrade maintenance, then select Disable DDMP Jobs to disable the DDMP jobs. If you do not plan to stop the Enterprise Manager system for postupgrade maintenance, and hence do not want to disable the DDMP jobs, then do not select the option.

    Deferred Data Migration (DDMP) is a post-upgrade activity to migrate the format of the data stored in an earlier release of Enterprise Manager to the format compatible with the upgraded Enterprise Manager system. The migration activity is essentially a job in Enterprise Manager that is submitted when the Oracle Management Repository gets upgraded, and is scheduled to run in the background when the upgraded Enterprise Manager system starts functioning.

    The time taken to migrate the data format depends on the volume of data available in your earlier release of Enterprise Manager. Therefore, if you have a large amount of data, then it takes longer to migrate.

    If you have to stop the Enterprise Manager system for postupgrade maintenance, then you can choose to disable the DDMP jobs now and run them later from the postupgrade console after the maintenance period ends and after the Enterprise Manager system becomes operational.

    To run the DDMP jobs later from the Post Upgrade Console, in the Enterprise Manager Cloud Control Console, from the Setup menu, select Manage Cloud Control, then select Post Upgrade Tasks.

Note:

For information about the various prerequisite checks that are run on the database at this point and how to fix them if they fail, see Prerequisites for Upgrading to Enterprise Manager Cloud Control 13c Release 4.

Step 5: Selecting the Deployment Size

On the Deployment Size screen, select one of the following options: Small, Medium or Large, and click Next.

Step 6: Running the Prerequisite Checks

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. Then click Next.

The installation wizard runs the prerequisite checks automatically when you come to this screen. The status of the prerequisite check can be either Warning, Failed, Succeeded, Not Executed, In Progress, or Pending.

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.

Step 7: Evaluating the Correction Types

Correction Types can be one of the following:

  1. Not Required: This is simply a warning message, it can be ignored.

  2. Manual: Manually fix all issues identified as this type.

  3. Auto: In this case, the installer has pre-defined corrective actions and is able to automatically fix these issues. These actions will automatically be run during the upgrade process.

Installing the OMS Software Only

Invoke the installer with the following option and pass the location where the plug-ins have been downloaded.

On the Admin (Primary) OMS, run the following:

./em13400_<platform>.bin -invPtrLoc <absolute_path_to_oraInst.loc_Inventory Pointer_File> PLUGIN_LOCATION=<absolute_path_to_plugin_software_location> INSTALL_SWONLY_WITH_PLUGINS=TRUE

On the additional OMS instances, run the following:

./em13400_<platform>.bin -invPtrLoc <absolute_path_to_oraInst.loc_Inventory Pointer_File> PLUGIN_LOCATION=<absolute_path_to_plugin_software_location> INSTALL_SWONLY_WITH_PLUGINS=TRUE PARALLEL_ADD_OMS_UPG=true

Refer to Installing an Enterprise Manager System Using Software Only Install Along With Plugins and Configuring Later for details about Installing OMS with Software Only option.

Running the 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 Oracle home of the OMS you installed in Installing the OMS Software Only.

On the Admin (Primary) OMS, run the following:

$<ORACLE_HOME>/allroot.sh

For example,

/u01/software/em13c/oraclehome/allroot.sh

On the additional OMS instances, run this script as well.

Note:

If you do not have the permission to run this script at this point, you can always run it after configuring the software binaries, but make sure you run it before you start upgrading the Management Agents.

Applying Required Patches on the OMS

Apply the latest software updates, including the latest PSU patches, bundle patches and plug-ins patches on top of the Enterprise Manager Release 4 software only home.

You can download the software updates in offline mode (if you do not have Internet connectivity) or online mode (if you have Internet connectivity). For instructions, see Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.

Upgrading the Admin OMS

This section explains how you can upgrade your Admin (Primary) OMS to version 13c Release 4.

Step 1: Stop all the OMS and Agents.

Step 2: Start the repository and OMS upgrade

Invoke the installation wizard by running the following script from the Oracle home of the OMS you installed in Installing the OMS Software Only:

$<ORACLE_HOME>/sysman/install/ConfigureGC.sh | ConfigureGC.bat

For 13c Release 4 on Microsoft Windows platforms, run the ConfigureGC.bat script with INSTALL_SWONLY_WITH_PLUGINS=true.
ConfigureGC.bat INSTALL_SWONLY_WITH_PLUGINS=true

Note:

Step 3: Selecting the Installation Type

On 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.

Step 4: Continue with the upgrade.

If an error occurs, the installer will pause. Rectify the issue and click Retry to resume the upgrade.

Performing Additional OMS Upgrades in Parallel

All additional OMS instances can now be upgraded simultaneously.

Run the upgrade process from all the additional OMS instances, simultaneously:

  • Invoke the installation wizard by running the following script from the Oracle home of the OMS of each additional OMS instance:

    For UNIX environment, run: <ORACLE_HOME>/sysman/install/ConfigureGC.sh

    For Windows environment, run: <ORACLE_HOME>/sysman/install/ConfigureGC.bat

    For 13c Release 4 on Microsoft Windows environment, run the ConfigureGC.bat script for any additional OMS upgrade using the following:
    ConfigureGC.bat INSTALL_SWONLY_WITH_PLUGINS=true CONFIGURE_BIP=false
  • Click Configure to start upgrade process.

    Figure 4-1 OMS Upgrade

    OMS Upgrade
  • Upgrade process is in progress.

    Figure 4-2 Upgrade In Progress

    Upgrade In Progress

If an error occurs, the installer will pause. Rectify the issue and click Retry to resume the upgrade.