Skip Headers
Oracle® Enterprise Manager Bundle Patch 1 Application Guide
12c Release 1 (12.1.0.1)

E35229-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

5 Bundle Patch 1 for Solaris (SPARC), Solaris (x86-64), and IBM AIX (64-bit)

This chapter describes various usecases to apply Bundle Patch 1 on Solaris (SPARC), Solaris (x86-64), and IBM AIX (64-bit) OMS and Management Agents. This chapter contains the following sections:

5.1 Before You Begin

Read the following important notes before proceeding with the installation process:

5.2 Installing Enterprise Manager Cloud Control 12c on Solaris (SPARC), Solaris (x86-64), or IBM AIX (64-bit)

To install Enterprise Manager Cloud Control 12c on Solaris (SPARC), Solaris (x86-64), or, IBM AIX (64-bit) download the binaries from Oracle Technology Network. You can get the 12.1.0.1 installation software from the product DVD or from Oracle Technology Network (OTN) at:

http://www.oracle.com/technetwork/oem/enterprise-manager/downloads/index.html

For more information, refer to the Procuring Software section of the Oracle® Enterprise Manager Cloud Control Advanced Installation and Configuration Guide 12c Release 1 (12.1.0.1), which can be found at the following location:

http://docs.oracle.com/cd/E24628_01/install.121/e24089/getstrtd_proc_sw.htm#BACFDBCA

On the download page, select the Solaris (SPARC), or Solaris (x86-64), or IBM AIX (64-bit) (With Bundle Patch 1) release.

The Bundle Patch 1 binaries will be installed by default. Enterprise Manager binaries will have BP1 patches included by default. You do not need to follow the BP1 patch instructions outlined in this document.

The 12.1.0.2 versions of the Oracle Database, Oracle Fusion Middleware, My Oracle Support, and Exadata plug-ins will also be installed by default as part of the Solaris (SPARC), Solaris (x86-64), or, IBM AIX (64-bit) installation process. You will have the option of installing additional available plug-ins, such as the Fusion Applications plug-in, during installation. Oracle recommends that you also install all the plug-ins that you think you may need.

When you invoke the Enterprise Manager Cloud Control Installation Wizard, you will be given a choice between two Install Types: Simple and Advanced. To install the additional plug-ins, you must perform an Advanced installation.

For more information, see "Installing with Advanced Configuration" in the Oracle® Enterprise Manager Cloud Control Basic Installation Guide 12c Release 1 (12.1.0.1), available at the following link:

http://docs.oracle.com/cd/E24628_01/install.121/e22624/install_em_exist_db.htm#CHDECIFI

You can also find more installation information in the Oracle® Enterprise Manager Cloud Control Advanced Installation and Configuration Guide 12c Release 1 (12.1.0.1), available at the following location:

http://docs.oracle.com/cd/E24628_01/install.121/e24089/toc.htm

5.3 Applying Bundle Patch 1 on Solaris SPARC, Solaris (x86-64), or IBM AIX

To apply Bundle Patch 1 on Solaris SPARC or 64 bit or AIX, follow these steps:

5.3.1 Step 1: Applying Bundle Patch 1 on Oracle Management Service

To apply Bundle Patch 1 on Solaris (SPARC), Solaris (x86-64), or, IBM AIX (64-bit) Oracle Management Service, follow these steps:

  1. Ensure that the Oracle Management Service (OMS) on which you are installing the patch or from which you are rolling back the patch is Oracle Management Service 12c Release 1 (12.1.0.1.0).

  2. Ensure that you have the latest version of OPatch. If you do not have the latest version, then follow the instructions outlined in the My Oracle Support note 224346.1 available at:

    https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=224346.1

  3. Ensure that you set the ORACLE_HOME environment variable to OMS core home, which is <%MIDDLEWARE_HOME%>/oms.

    Where <%MIDDLEWARE_HOME%> refers to the location where Enterprise Manager Cloud Control is installed. For example, /u01/app/Oracle/Middleware.

  4. Ensure that you set the PATH environment variable to include the location of the unzip executable, and the <ORACLE_HOME>/bin and the <ORACLE_HOME>/OPatch directories present in the Oracle home of the OMS.

  5. Verify the Oracle Inventory because OPatch accesses it to install the patches. To verify the inventory, run the following command. If the command displays some errors, then contact Oracle Support and resolve the issue.

    $ opatch lsinventory

  6. Check that the Oracle Database, which contains the Management Repository, and its listener are up and running.

  7. Download OMS BP1 13242773 from My Oracle Support, and extract its contents to an accessible location, which is referred to as <PATCH_TOP_DIR> in this section.

  8. Download the JDeveloper and Web Services Manager patches 13470978 and 12321965, respectively, from My Oracle Support. You will be required to apply these patches after applying the 13242773 BP1 on the OMS. Download the patch 12321965 for Release 11.1.1.5.0 version.

  9. Stop the OMS:

    $ emctl stop oms

    To verify that the OMS has stopped, run the following command:

    $ emctl status oms

    Note:

    In a multi-OMS environment, shut down all OMS instances.
  10. Stop the following components if running within your Cloud Control domain before applying BP1 or updating any plug-in to the latest release:

    • Application Dependency and Performance (ADP) Manager.

    • JVM Diagnostics (JVMD) Manager.

    • BI Publisher Managed Server named "BIP".

  11. Install OMS BP1 13242773 by running the following command:

    $ cd PATCH_TOP_DIR/13242773

    $ opatch apply

    Note:

    In a multi-OMS environment, run this command on all OMS instances. Run opatch apply in parallel for all OMS instances in this step OR complete the BP1 application process on the first OMS, then do the same for the other OMS instances.
  12. Select the appropriate script to automate the BP1 postinstallation process, depending on whether you have a single-OMS environment or a multi-OMS environment.

    Note:

    Ensure that you are in the BP1 location PATCH_TOP_DIR. Also, keep the Repository host name, SID, Listener port, and SYSMAN password ready before running the post_deploy.sh script.
    • Single OMS Environment

      In a single-OMS environment, run the following command from the Bundle Patch 1 directory:

      $ PATCH_TOP_DIR/13242773/post_deploy.sh
      

      The post_deploy.sh script prompts for the following details: SYSMAN password, Enterprise Manager Repository Host, Enterprise Manager Repository Port, Enterprise Manager Repository SID, and the patch location.

      The OMS will be started automatically after running the post_deploy.sh script.

    • Multi-OMS Environment

      In a multi-OMS environment, do the following:

      1. Find the Administration Server by running the following command from OMS home:

        $ORACLE_HOME/bin/emctl status oms -details

        Output similar to the following is displayed:

        Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.2.0 
        Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved
        Enter Enterprise Manager Root (SYSMAN) Password :
        Console Server Host : myhost.example.com
        HTTP Console Port : 7788
        HTTPS Console Port : 7799
        HTTP Upload Port : 4889
        HTTPS Upload Port : 4900
        EM Instance Home : /scratch/userid/work/insthome914/em/EMGC_OMS1
        OMS Log Directory Location : /scratch/userid/work/insthome914/em/EMGC_OMS1/sysman/log
        OMS is not configured with SLB or virtual hostname
        Agent Upload is locked.
        OMS Console is locked.
        Active CA ID: 1
        Console URL: https://myhost.example.com:7799/em
        Upload URL: https://myhost.example.com:4900/empbs/upload
        
        WLS Domain Information
        Domain Name : GCDomain
        Admin Server Host: myhost.example.com
        
        Managed Server Information
        Managed Server Instance Name: EMGC_OMS1
        Managed Server Instance Host: myhost.example.com
        WebTier is Down
        Oracle Management Server is Down
        
      2. Run the following command on the Primary OMS of a multi-OMS setup:

        The Primary OMS is the one co-located with the Admin server.

        $ ./PATCH_TOP_DIR/13242773/post_deploy.sh

      3. Run the following command on the other OMS environments (non-Primary):

        $ ./ PATCH_TOP_DIR/13242773/MultiOms_post_deploy.sh

        You will be asked to enter the patch location. For example:

        /scratch/xxx/PATCH_TOP_DIR/13242773

  13. Apply the JDeveloper and Web Services Manager patches 13470978 and 12321965 to OMS.

    Note:

    This must be applied to all of the OMS instances in a multi-OMS environment. Also, there is no specific sequence to apply these two patches.

    If you have Enterprise Manager installed using the Enterprise Manager binaries with BP1, then this JDeveloper patch is automatically installed with no further work required.

    If you are applying the BP1 on your existing Enterprise Manager installation, then you must apply the JDeveloper patch as an extra step. There are a variety of fixes in the patch, including functional issues and Google Chrome and Microsoft Internet Explorer 9 browser support. The JDeveloper patch should be applied after BP1. For instructions, refer to the README of the respective patch.

    Apply the patches following the instructions in the README of the corresponding patch. When you search for patch 12321965, you will find two releases of the patch, namely, 11.1.1.5.0 and 11.1.1.4.0. Make sure that you select and apply the 11.1.1.5.0 release of the patch. Verify that you apply both the patches in the oracle_common directory that resides in the Middleware Home (MW_HOME/oracle_common/). Set environment variable ORACLE_HOME to your [MW_HOME]/oracle_common directory before applying patches 13470978 and 12321965 to the OMS.

  14. Verify that BP1 was properly installed by running the following command to check that the patch is registered in the inventory:

    $<MIDDLEWARE_HOME>/oms/OPatch/opatch lsinventory

    To verify that all the patches are installed on the OMS, run the following commands:

    1. Set the following environment variable on the OMS host:

      setenv ORACLE_HOME <MIDDLEWARE_HOME>/oms

    2. Run the following verification commands to ensure the patch has been applied to the OMS:

      $<MIDDLEWARE_HOME>/oms/OPatch/opatch lspatches -id 13242773 -verify

      $<MIDDLEWARE_HOME>/oms/OPatch/opatch lspatches -oh <MIDDLEWARE_HOME>/oracle_common -id 12321965 -verify

      $<MIDDLEWARE_HOME>/oms/OPatch/opatch lspatches -oh /<MIDDLEWARE_HOME>/oracle_common -id 13470978 –verify

      The results of the commands will show the patch number and its details if present in the OMS.

  15. Download OMS BP1 14040891 from My Oracle Support, and extract its contents to an accessible location, which is referred to as <PATCH_TOP_DIR2> in the rest of this section.

  16. If the OMS is running, stop it. Otherwise, skip this step.

    $ emctl stop oms

    To verify that the OMS has stopped, run the following command:

    emctl status oms

    Note:

    In a multi-OMS environment, shut down all OMS instances.
  17. Install OMS BP1 14040891:

    $ cd <PATCH_TOP_DIR2>/14040891

    $ opatch napply

    Note:

    In a multi-OMS environment, run this command on all OMS instances. Run opatch napply in parallel for all OMS instances in this step OR complete the BP1 application process on the first OMS, then do the same for the other OMS instances.
  18. Run the following command:

    $ emctl applypatch repos -patchHome <PATCH_TOP_DIR2>/14040891/13653571

    If the command succeeds, the following message is displayed:

    PATCH APPLICATION HAS SUCCEEDED

  19. Run the following command:

    $ emctl register oms metadata -service swlib -file $ORACLE_HOME/sysman/metadata/swlib/multioms -core

    $ emctl register oms metadata -service procedures -file $ORACLE_HOME/sysman/metadata/procedures/multioms/MultiOMS.xml -core

    $ emctl register oms metadata -service derivedAssocs -file $ORACLE_HOME/sysman/metadata/derivedAssocs/emSystemAssocRules.xml -core

  20. Start the OMS by running the following command:

    $ emctl start oms

Note:

If you have a standby site, then follow these steps:
  1. On each standby OMS, follow Step (1) to Step (11), then Step (13) and Step (14).

    Note: DO NOT run the post_deploy.sh command as described in Step (12).

  2. Then, run the following for each standby OMS instance, where ORACLE_HOME is the OMS home:

    $ ORACLE_HOME/perl/bin/perl 13242773_PATCH_TOP_DIR/apply12959056.pl

    $ ORACLE_HOME/perl/bin/perl 13242773_PATCH_TOP_DIR/apply13479448.pl

    $ sh $ORACLE_HOME/bin/exec_13651296_patch

    These scripts can be found under:

    13242773_PATCH_TOP_DIR/custom/scripts/

  3. And then, follow Step (15) to Step (19).

For instructions to set up a standby OMS, refer to Setting Up High Availability.

5.3.2 Step 2: Setting Up Infrastructure for Patching Management Agents

Follow the steps outlined in this section for setting up the infrastructure for patching Management Agents:

  1. For setting up My Oracle Support Credentials, refer to Section 2.2.1.

  2. For setting up infrastructure in Online Mode, refer to Section 2.2.2.

  3. For setting up infrastructure in Offline Mode, follow these steps:

    1. Verify that the connection to My Oracle Support is set to "Offline".

      From the Setup menu, select Provisioning and Patching, then select Offline Patching.

    2. From the Patching Setup page, select Online and Offline Settings, then select Offline and click Apply.

    3. Log in to another host with internet connectivity, and perform the following steps:

      - Download Management Agent patches 13242776, 14041708, and 13491785, and OPatch patch 6880880 from My Oracle Support.

      - Upload these patches to Software Library.

    4. Go back to your infrastructure in the Offline mode, and perform the following steps:

      1. Download the Management Agent patches by specifying the patch numbers 13242776, 14041708, and 13491785 as comma-separated entries In the Patch Search region of the Patches & Updates page, then click Search.

        Make sure you select the right platform, for example, Solaris SPARC.

      2. Click Search.

      3. Download the patch zip files and the patch metadata files for the patches.

        To download the patch metadata, click Download Patch Metadata, then click Download.

        Click the patch zip file to download the zip file.

        Note:

        Make sure you download both.
      4. Download the required OPatch patches from My Oracle Support (https://support.oracle.com).

        Search for patch "6880880" for the appropriate platform for the Management Agent target. For example, if your target is Linux x86-64, pick platform Linux x86-64.

      5. Click Search.

        Download the patch for the version 11.1.0.0.0 series only.

      6. Download both the patch zip file and the patch metadata.

        To download the patch metadata file, click Download Patch Metadata, then click Download.

    5. Upload the Management Agent patches to the Software Library.

      1. From the Enterprise menu, select Provisioning and Patching, then select Saved Patches.

      2. Click Upload to open the Upload Patches to Software Library page.

      3. On the Upload Patches to Software Library page, in the Basic Information section, do the following:

        - From the Product Family list, select the product family for which you are uploading the patch. For example, for patches 13242776, 13491785, and 14041708 select Oracle System Management Products.

        - From the Product list, select the product for which you are uploading the patch. For example, for patches 13242776, 13491785, and 14041708 select Enterprise Manager Base Platform.

        - From the Select Type of Patch, select either Patch or Patch Set depending on the type of patch you are uploading. For example, for patches 13242776, 13491785, and 14041708 select Patch from the menu.

      4. For patches 13242776, 14041708, and 13491785, select the patch metadata file and patch zip file from the local directory on the system and click Upload.

      5. Upload patches 13242776, 14041708, and 13491785 by selecting their patch metadata and the patch zip file.

      6. Reset the Basic Information attributes as shown.

      7. Select the patch metadata and the patch zip file and click Upload.

    6. To upload OPatch 6880880 to the Software Library, specify the Basic Information attributes.

      Select the patch metadata and patch zip file for the Opatch patch 6880880 and upload it. Ensure that you fill in all attributes required in the page:

      - Product Family: Oracle Systems Management Products

      - Product: Universal Installer

      - Release: Choose version as "11.1.0.0.0".

      - Created On: Use today's date

      - Description: Opatch for version 11.1.0.x

      - Platform: Select the platform for which you downloaded the patch (for example, Solaris SPARC)

      - Language: Select 'American English'

    7. Click Upload.

      Upon successful upload, all the patches will be visible in the Saved Patches page.

      At the end of this process, all of the Agent patches and the Opatch patch should be listed in the Saved Patches in Software Library page.

5.3.3 Step 3: Downloading and Deploying Plug-ins on Oracle Management Service

To download and deploy the plug-ins on the OMS in graphical mode, refer to Section 2.3.1 and Section 2.3.2.

To download the plug-ins in graphical mode, and to deploy them on the OMS, particularly multiple plug-ins at a time, in silent mode, follow these steps:

  1. Meet the prerequisites in Section 2.3.1. Then, download the plug-ins following Step (1) to Step (6) in Section 2.3.2.

  2. Log in to EM CLI as follows:

    cd $ORACLE_HOME/bin/emcli login -username=sysman
    
  3. Run the following command:

    $ORACLE_HOME/emcli sync
    
  4. To deploy the plug-ins on the OMS, run the following command:

    emcli deploy_plugin_on_server 
    -plugin="plug-in_id"[:"version"]
    [-sys_password="sys_password"] 
    [-prereq_check] 
    

    For example,

    emcli deploy_plugin_on_server -plugin="oracle.sysman.db:12.1.0.2.0;oracle.sysman.emas:12.1.0.2.0"
    

5.3.4 Step 4: Applying Patch 14158696 on Solaris x86-64 Management Agents Only

To apply patch 14158696 on Management Agents, refer to Section 2.4.

Note:

Ensure that you add the patch number 14158696 to the patch plan instead of the patches mentioned in Section 2.4. The instructions outlined in Section 2.4 is specific to Linux, consider that only an example and follow the instructions outlined in the section to apply 14158696 patch.

Do NOT add any other patch to this patch plan. This patch plan must have only this 14158696 patch.

5.3.5 Step 5: Applying Patches 13242776, 14041708, 13491785 on Management Agents

Note:

If the Management Agents are running on a HP-PA RISC host or a HP-Itanium host, then ensure that you use the latest OPatch version 11.1.0.9.7. To upload the new OPatch 11.1.0.9.7 version to Software Library, perform the following steps:
  1. Run the following steps to delete the current OPatch version as follows:

    - Log in to Enterprise Manager Cloud Control.

    - From Enterprise menu, select Provisioning and Patching, and click Saved Patches.

    - On the Saved Patches in Software Library page, search for patch 6880880.

    - Click Remove.

  2. To upload OPatch patches to Oracle Software Library, refer to Uploading OPatch Patches to Oracle Software Library.

To apply patches 13242776, 14041708, and 13491785 on Management Agents, refer to Section 2.4.

Note:

Ensure that you add the patch numbers13242776, 14041708, and 13491785 to the patch plan instead of the patches mentioned in Section 2.4. The instructions outlined in Section 2.4 is specific to Linux, consider that only an example and follow the instructions outlined in the section to apply these patches.

5.3.6 Step 6: Deploying Plug-ins on Management Agents

For deploying plug-ins on Management Agents, refer to Section 2.5.

5.3.7 Step 7: Upgrading BI Publisher Reports Shipped with the Plug-ins

To upgrade the Oracle Business Intelligence Publisher (BI Publisher) reports that are packaged with the plug-ins, refer to Section 2.6.

Note:

Upgrade the BI Publisher reports only if BI Publisher was previously installed and configured to work with Oracle Enterprise Manager Cloud Control 12c. If it was not already installed and configured, then this step will automatically occur when BI Publisher is configured at a later time.

5.3.8 Step 8: Upgrading ADP and JVM Diagnostics

To upgrade ADP and JVM Diagnotics, refer to Section 2.7.

5.3.9 Step 9: Updating the Existing Agent Image to the Latest Agent Image with Bundle Patch 1

For updating the existing agent image present on your Oracle Management Service to the latest agent image with Bundle Patch 1, refer to Chapter 3.

5.4 Managing New Management Agents Deployed on Solaris SPARC, Solaris (x86-64), IBM AIX, HP-UX, or HP-UX Itanium Hosts from OMS on Linux with BP1 or from OMS on Windows with Bundle Patch 1

If you are planning to monitor a newly deployed Management Agent on Solaris SPARC, Solaris 64 bit, AIX, HP-UX, or HP-UX Itanium host from Oracle Management Service on Linux (32-bit or 64-bit) with BP1 or Oracle Management Service on Windows with BP1, then follow these steps:

5.4.1 Step1: Applying Patch 14040891 on Oracle Management Service

To apply patch 14040891 on Oracle Management Service, follow these steps:

  1. Ensure that the Oracle Management Service (OMS) on which you are installing the patch or from which you are rolling back the patch is Oracle Management Service 12c Release 1 (12.1.0.1.0).

  2. Ensure that you have the latest version of OPatch. If you do not have the latest version, then follow the instructions outlined in the My Oracle Support note 224346.1 available at:

    https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=224346.1

  3. Ensure that you set the ORACLE_HOME environment variable to OMS core home, which is <%MIDDLEWARE_HOME%>/oms.

    Where <%MIDDLEWARE_HOME%> refers to the location where Enterprise Manager Cloud Control is installed. For example, /u01/app/Oracle/Middleware.

  4. Ensure that you set the PATH environment variable to include the location of the unzip executable, and the <ORACLE_HOME>/bin and the <ORACLE_HOME>/OPatch directories present in the Oracle home of the OMS.

  5. Verify the Oracle Inventory because OPatch accesses it to install the patches. To verify the inventory, run the following command. If the command displays some errors, then contact Oracle Support and resolve the issue.

    $ opatch lsinventory

  6. Check that the Oracle Database, which contains the Management Repository, and its listener are up and running.

  7. Stop the OMS:

    $ emctl stop oms

    To verify that the OMS has stopped, run the following command:

    $ emctl status oms

    Note:

    In a multi-OMS environment, shut down all OMS instances.
  8. Stop the following components if running within your Cloud Control domain before applying BP1 or updating any plug-in to the latest release:

    • Application Dependency and Performance (ADP) Manager.

    • JVM Diagnostics (JVMD) Manager.

    • BI Publisher Managed Server named "BIP".

  9. Download OMS BP1 14040891 from My Oracle Support, and extract its contents to an accessible location, which is referred to as <PATCH_TOP_DIR2> in the rest of this section.

  10. Install OMS BP1 14040891:

    $ cd <PATCH_TOP_DIR2>/14040891

    $ opatch napply

    Note:

    In a multi-OMS environment, run this command on all OMS instances. Run opatch napply in parallel for all OMS instances in this step OR complete the BP1 application process on the first OMS, then do the same for the other OMS instances.
  11. Run the following command:

    $ emctl applypatch repos -patchHome <PATCH_TOP_DIR2>/14040891/13653571

  12. Run the following command:

    $ emctl register oms metadata -service swlib -file $ORACLE_HOME/sysman/metadata/swlib/multioms -core

    $ emctl register oms metadata -service procedures -file $ORACLE_HOME/sysman/metadata/procedures/multioms/MultiOMS.xml -core

    $ emctl register oms metadata -service derivedAssocs -file $ORACLE_HOME/sysman/metadata/derivedAssocs/emSystemAssocRules.xml -core

  13. Start the OMS by running the following command:

    $ emctl start oms

5.4.2 Step 2: Applying Plug-In Patches on Plug-In Homes Deployed to Oracle Management Service

The following sections describe the process of applying plug-in patches on plug-in homes deployed to Oracle Management Service:

5.4.2.1 Applying Oracle Database Plug-In Patch 14089634

To apply Oracle Database Plug-in patch 14089634 on your Oracle Management, follow these steps:

  1. Shut down the OMS by running the following command:

     <ORACLE_HOME>/bin emctl stop oms
    

    Make sure to shut down all OMS instances in a multi-OMS environment.

  2. Set the environment variable PLUGIN_HOME to:

    <%MIDDLEWARE_HOME%>/plugins/oracle.sysman.db.oms.plugin_12.1.0.2.0

    For example:

    setenv PLUGIN_HOME /example/work/midlwre6465/plugins/oracle.sysman.db.oms.plugin_12.1.0.2.0

  3. Maintain a location for storing the contents of the patch ZIP file.

    In the rest of this section, this location (absolute path) is referred to as PATCH_TOP_DIR.

  4. Run the following command to extract the contents of the patch ZIP file to the location you created in the previous step:

    $ unzip -d PATCH_TOP_DIR p14089634_121010_Generic.zip
    
  5. Use the following command to navigate to the PATCH_TOP_DIR/14089634 directory:

    $ cd PATCH_TOP_DIR/14089634
    
  6. Run the following command on each OMS instance (in a multi-OMS environment) to apply the patch:

    $ opatch napply -oh $PLUGIN_HOME
    

    The following messages appear on screen:

    • Do you want to proceed? [y|n]: (yes)

    • Oracle Support Email address/User Name: (provide your details or press Enter to continue)

    • Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: (y)

    If the patch is applied successfully, the following message is displayed:

    OPatch succeeded
    
  7. Run the following four commands on the first OMS only (you will be prompted for the SYSMAN password):

    If the commands succeed, the following message is displayed:

    Metadata registration successful
    

    Note:

    In the following commands, <command prompt> is ORACLE_HOME/bin.
    1. <command prompt> emctl register oms metadata -service swlib -file $PLUGIN_HOME/metadata/swlib -pluginId oracle.sysman.db

    2. <command prompt> emctl register oms metadata -service procedures -file $PLUGIN_HOME/metadata/procedures/ExtendClusterNG.xml -pluginId oracle.sysman.db

    3. <command prompt> emctl register oms metadata -service procedures -file $PLUGIN_HOME/metadata/procedures/provsidb.xml -pluginId oracle.sysman.db

    4. <command prompt> emctl register oms metadata -service preNGProcedures -file $PLUGIN_HOME/metadata/preNGProcedures/RACProvisionWIN.xml -pluginId oracle.sysman.db

  8. Start the OMS instance:

    <ORACLE_HOME>/bin emctl start oms

5.4.2.2 Applying Oracle Fusion Applications Patch 13719833

To apply Oracle Fusion Applications Patch 13719833, refer to Section 4.2.2.3.

Note:

If you have already applied this patch before, then you need not apply it again. For example, if you have applied Bundle Patch 1 on Linux hosts, and then installed Management Agents on Microsoft Windows hosts as described in Section 4.2, then as part of the bundle patch application process, you would have already applied this Oracle Fusion Applications plug-in patch. In such cases, you need not apply this patch all over again.

5.4.2.3 Applying Oracle Fusion Middleware Plug-in Patch 13963029

To apply Oracle Fusion Middleware Plug-in patch 13963029, follow these steps:

  1. Ensure that the Oracle Management Service (OMS) on which you are installing the patch or from which you are rolling back the patch is Oracle Management Service 12c Release 1 (12.1.0.1.0).

  2. Ensure that you have the latest version of OPatch. If you do not have the latest version, then follow the instructions outlined in the My Oracle Support note 224346.1 available at:

    https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=224346.1

  3. Ensure that you set the ORACLE_HOME environment variable to OMS Core home, which is <%MIDDLEWARE_HOME%>/oms.

  4. Set the environment variable PLUGIN_HOME to <%MIDDLEWARE_HOME%>/plugins/oracle.sysman.emas.oms.plugin_12.1.0.2.0

  5. Ensure that you set the PATH environment variable to include the location of the unzip executable, and the <ORACLE_HOME>/bin and the <ORACLE_HOME>/OPatch directories present in the Oracle home of the OMS.

  6. Verify the Oracle Inventory because OPatch accesses it to install the patches. To verify the inventory, run the following command. If the command displays some errors, then contact Oracle Support and resolve the issue.

    $ opatch lsinventory -oh $PLUGIN_HOME

  7. Ensure that you shut down the OMS by running the following command:

    $ emctl stop oms

    Note:

    In case of a multi-OMS environment, shut down all the OMSes.
  8. Ensure that the Oracle Database, which contains the Management Repository, and its listener are up and running.

  9. Maintain a location for storing the contents of the patch ZIP file. In the rest of the document, this location (absolute path) is referred to as <PATCH_TOP_DIR>.

  10. Extract the contents of the patch ZIP file to the location you created in Step (1). To do so, run the following command:

    $ unzip -d <PATCH_TOP_DIR> p13963029_121020_Generic.zip

  11. Navigate to the <PATCH_TOP_DIR>/13963029 directory:

    $ cd <PATCH_TOP_DIR>/13963029

  12. Install the patch by running the following command:

    On Unix:

    $ opatch napply -oh $PLUGIN_HOME

    On Windows:

    opatch napply -oh %PLUGIN_HOME%

  13. Register the JobType using the following command:

    Enter SYSMAN Password for each command when prompted.

    $ emctl register oms metadata -service swlib -file $PLUGIN_HOME/metadata/swlib/coherenceprov -pluginId oracle.sysman.emas

    $ emctl register oms metadata -service swlib -pluginId oracle.sysman.emas -file $PLUGIN_HOME/metadata/swlib

    $ emctl register oms metadata -pluginId oracle.sysman.emas -service procedures -file $PLUGIN_HOME/metadata/procedures/FMWPROV.xml

    $ emctl register oms metadata -pluginId oracle.sysman.emas -service procedures -file $PLUGIN_HOME/metadata/procedures/DomainScaleUp.xml

    $ emctl register oms metadata -pluginId oracle.sysman.emas -service jobTypes -file $PLUGIN_HOME/metadata/jobTypes/CreateFMWBundle.xml

    $ emctl register oms metadata -pluginId oracle.sysman.emas -service jobTypes -file $PLUGIN_HOME/metadata/jobTypes/CreateFMWGoldImage.xml

    $ emctl register oms metadata -service procedures -file $PLUGIN_HOME/metadata/procedures/WholeServerMigration.xml -pluginId oracle.sysman.emas

    $ emctl register oms metadata -service swlib -file $PLUGIN_HOME/metadata/swlib/patch -pluginId oracle.sysman.emas

  14. Start the OMS instance:

    <ORACLE_HOME>/bin emctl start oms

5.4.3 Step 3: Downloading and Upgrading Plug-ins to 12.1.0.2 Release

You need to obtain the Solaris SPARC, Solaris (x86-64), IBM AIX-specific revisions of the plug-ins using Self Update in either online or offline mode. The plug-ins have been revised are for Database, Fusion Middleware, and Exadata components. The steps are similar to those outlined in Section 2.3.

To view the available revisions for the Oracle Database, Oracle Fusion Middleware, and Oracle Fusion Applications plug-ins, log in to the Cloud Control console and from the Setup menu, select Extensibility, then select Plug-ins.

5.4.4 Step 4: Upgrading ADP and JVM Diagnostics

To upgrade ADP and JVM Diagnotics, refer to Section 2.7.

5.4.5 Step 5: Updating the Existing Agent Image to the Latest Agent Image with Bundle Patch 1

For updating the existing agent image present on your Oracle Management Service to the latest agent image with Bundle Patch 1, refer to Chapter 3.

5.4.6 Step 6: Deploying Management Agents on Solaris SPARC, Solaris (x86-64), IBM AIX, HP-UX, and HP-UX Itanium

For deploying a fresh Management Agent on Solaris SPARC, Solaris 64 bit, AIX, HP-UX, or HP-UX Itanium, refer to "Installation Procedure" section in the Oracle® Enterprise Manager Cloud Control Basic Installation Guide 12c Release 1 (12.1.0.1), available at the following link:.

http://docs.oracle.com/cd/E24628_01/install.121/e22624/install_agent.htm#BABIHIAG

5.5 Managing Existing Management Agents Running on Solaris SPARC, Solaris (x86-64), IBM AIX, HP-UX, or HP-UX Itanium Hosts from OMS on Linux with BP1 or from OMS on Windows with Bundle Patch 1

If you are planning to monitor existing Management Agents running on Solaris SPARC, Solaris 64 bit, AIX, HP-UX, or HP-UX Itanium hosts from Oracle Management Service on Linux (32-bit or 64-bit) with BP1 or Oracle Management Service on Windows with BP1, then follow these steps:

5.5.1 Step 1: Applying Patch 14040891 on Oracle Management Service

For information about applying patch 14040891 on Oracle Management Service, refer to Section 5.3.1.

5.5.2 Step 2: Applying Plug-In Patches on Plug-In Homes Deployed to Oracle Management Service

For information about applying Plug-in patches on Plug-in homes deployed to Oracle Management service, refer to Section 5.4.2.

5.5.3 Step 3: Setting Up Infrastructure for Patching Management Agents Before Upgrading Plug-ins

For information about setting up infrastructure for patching Management Agents before upgrading plug-ins, refer to Section 5.3.2.

5.5.4 Step 4: Applying Patch 14158696 on Solaris x86-64 Management Agents Only

To apply patch 14158696 on Management Agents, refer to Section 2.4.

Note:

Ensure that you add the patch number 14158696 to the patch plan instead of the patches mentioned in Section 2.4. The instructions outlined in Section 2.4 is specific to Linux, consider that only an example and follow the instructions outlined in the section to apply 14158696 patch.

Do NOT add any other patch to this patch plan. This patch plan must have only this 14158696 patch.

5.5.5 Step 5: Applying Patches 13242776, 14041708, 13491785 on Management Agents

Note:

If the Management Agents are running on a HP-PA RISC host or a HP-Itanium host, then ensure that you use the latest OPatch version 11.1.0.9.7. To upload the new OPatch 11.1.0.9.7 version to Software Library, perform the following steps:
  1. Run the following steps to delete the current OPatch version as follows:

    - Log in to Enterprise Manager Cloud Control.

    - From Enterprise menu, select Provisioning and Patching, and click Saved Patches.

    - On the Saved Patches in Software Library page, search for patch 6880880.

    - Click Remove.

  2. To upload OPatch patches to Oracle Software Library, refer to Uploading OPatch Patches to Oracle Software Library.

To apply patches 13242776, 14041708, and 13491785 on Management Agents, refer to Section 2.4.

Note:

Ensure that you add the patch numbers13242776, 14041708, and 13491785 to the patch plan instead of the patches mentioned in Section 2.4. The instructions outlined in Section 2.4 is specific to Linux, consider that only an example and follow the instructions outlined in the section to apply these patches.

5.5.6 Step 6: Upgrading ADP and JVM Diagnostics

To upgrade ADP and JVM Diagnotics, refer to Section 2.7.

5.5.7 Step 7: Deploying Plug-ins on Management Agents

For deploying plug-ins on Management Agents, refer to Section 2.5.