Upgrading Fusion Middleware 11.1.1.x to 11.1.1.4

This is a follow on from my previous post where we upgraded 11.1.1.2 to 11.1.1.3. The instructions I provide here will work for Fusion Middleware 11.1.1.2 and 11.1.1.3 wanting to upgrade to 11.1.1.4.

In this example I’m just upgrading SOA Suite on OEL 64bit but the steps will be the same, some of the downloads may be different based on your environment.

To upgrade to 11.1.1.4 you need to have access to http://support.oracle.com as this is where the downloads reside. Oracle provides 11.1.1.4 as a standalone download so you can do a fresh install if required using OTN downloads (http://www.oracle.com/technetwork/indexes/downloads/index.html).

The high level steps to upgrade are as follows:

  • Download software
  • Shutdown your SOA Environment
  • Upgrade WLS to 11.1.1.4
  • Upgrade SOA Suite to 11.1.1.4
  • Upgrade OSB to 11.1.1.4
  • Upgrade MSD Schemas
  1. Identify the downloads you require for your install. You will need the WebLogic Server Upgrade and the additional product downloads. If you are using 64bit then use the generic version. The downloads are found from the following location - http://download.oracle.com/docs/html/E18749_01/download_readme.htm#BABDDIIC

    For the purpose of this post I downloaded the following patches
    11060985 – WLS Server Generic
    11060960 – SOA Suite
    11061005 – OSB Suite 
  2. Make sure you have set the Java executable in your PATH e.g.

    export PATH=$JAVA_HOME/bin:$PATH
  3. Make sure all your WebLogic environment has been shut down before performing the upgrade.
  4. Extract the WLS patch 11060985 to a temporary directory and start the installer

    java –jar wls1034_upgrade_generic.jar

    Please note if you are not running 64BIT then the upgrade executable will be just a bin file which you can execute directly.

    image
  5. Chose the right Oracle home for your WebLogic Server install.

    image
  6. In the Register for Security Updates you can enter your details or just click Next. If you do not enter details confirm that you don’t want to receive these updates

    image

    image
  7. Select the products you want to upgrade and select next. It is recommended that you accept the defaults.

    image
  8. Confirm the directories that will be upgraded

    image
  9. Upgrade of WLS ahs been completed

    image
  10. Extract your both SOA downloads to a temporary directory and run the installer found in Disk1

    ./runInstaller -jreLoc /java/jdk1.6.0_20/jre

    Please note that the java location and version may be different for your environment

    image
  11. Skip the Software Updates

    image
  12. Ensure your system meets the prerequisites

    image
  13. Set the Oracle home for your SOA install.

    image

    You will be asked to confirm that you want to upgrade, click Yes

    image
  14. Choose your application server. Since you are upgrading from 11.1.1.x you will be on WebLogic

    image
  15. Start the Install

    image
  16. Installation Upgrade of SOA Suite completed accept the default to finish.

    image


    image
  17. In my environment I have OSB installed so I need to upgrade this next. If you don’t have SOA Suite you can go straight to completing the DB Schema updates at Step 24. 
  18. Extract the OSB upgrade files to a temporary directory and execute the installer found in the Disk1 folder.
    ./runInstaller -jreLoc /java/jdk1.6.0_20/jre

    image

  19. Skip the software updates

    image
  20. Select the Oracle home for your environment

    image

    Accept the warning to continue the upgrade

    image
  21. Point to the location of your WebLogic Server installation

    image
  22. Install the OSB upgrade

    image
  23. Upgrade has been completed accept the defaults

    image

    image
  24. Change directory to $MW_HOME/oracle_common/bin where the Patch Set Assistant is installed
  25. Execute the following command to update the MDS schema. Please not for my examples I have the context set to DEV. your may be different. This means that all my schemas are prefixed by DEV.

    ./psa -dbType Oracle -dbConnectString 'localhost:1521:xe' -dbaUserName sys -schemaUserName DEV_MDS

    You will be asked you passwords for sys and the schema

    Enter the database administrator password for "sys":
    Enter the schema password for schema user "DEV_MDS":

  26. Change directory to $MW_HOME/Oracle_SOA1/bin to where the Patch Set Assistant is installed for SOA Suite.
    Execute the following command to update the SOA and BAM schemas

    ./psa -dbType Oracle -dbConnectString 'localhost:1521:xe' -dbaUserName sys -schemaUserName DEV_SOAINFRA
  27. To check that you have the installed correctly run the following SQL as sysdba.

    SELECT owner, version, status FROM schema_version_registry;

    OWNER                          VERSION                        STATUS
    ------------------------------ ------------------------------ -----------
    DEV_MDS                        11.1.1.4.0                     VALID
    DEV_SOAINFRA                   11.1.1.4.0                     VALID

    Don’t stress if the versions are not all sitting at version 11.1.1.4 as not all schemas need to be updated. The key ones are MDS and SOAINFRA

Comments:

Excellent blog post. Is there not any OSB schema that should be updated to 11.1.1.4 ?

Posted by Jon Petter Hjulstad on February 23, 2011 at 08:51 AM GMT+13:00 #

There maybe but this would be only if you have the OSB examples. In my version I don't have them installed.

I have seen references in the Fusion Middleware Patching Guide (E16793-06) to OSB Schemas for MSSQL.

best way to check is to run the following SQL

SELECT owner, version, status FROM schema_version_registry;

and see if there is a DEV_ORAOSB or something similar. If there is then you will need to run psa in the Oracle_OSB1/bin

cheers
James

Posted by James Taylor on February 23, 2011 at 08:57 AM GMT+13:00 #

helloooo

Posted by pepe on March 02, 2011 at 05:24 PM GMT+13:00 #

Hi James,

We are considering an upgrade from 11.1.1.2 to 11.1.1.4, apart from the steps mentioned above, do we need to upgrade the SOA composites as well i.e open the composites in Jdeveloper 11.1.1.4 version and redeploy ?

Or does the MDS and SOAInfra DB upgrade take care of the metadata upgrade?

Posted by Subhankar on May 14, 2012 at 07:45 PM GMT+13:00 #

The upgrade will take care of the Composites as well. When you are looking at upgrading a live system you need to also address what to do with long running processes. This link may be able to help plan what is best for your environment.
http://docs.oracle.com/cd/E23943_01/upgrade.1111/e10127/cutover_strategy.htm#BAEDCCHH

cheers
James

Posted by James Taylor on May 15, 2012 at 11:05 AM GMT+13:00 #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Discussions and Examples using Oracle Fusion Middleware. Some image links are broken when using Firefox, Safari, and Chrome. If you want to see the full image please use IE.

Twitter:@james8001

tumblr hit counter vistors, thanks for your support

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today