RSS

OBIEE 11.1.1.3.0 to 11.1.1.5.0 – In-Place-Upgrade

19 Jun

During my 11G journey am frequently asking for “How to upgrade new OBIEE 11.1.1.5.0 on top of OBIEE 11.1.1.3.0” i.e. In-Place-Upgrade. So thought of writing a post on this topic today. Hope this helps you in your executions.

When we are moving from OBIEE 11.1.1.3 to 11.1.1.5 there are two ways to upgrade our environment.

  1. out-of-place upgrade : This is quite simply installing new OBIEE 11.1.1.5.0 by uninstalling 11.1.1.3.0 or maintaining two Middleware homes.
  2. in-place upgrade : This upgrade operates on existing files. Moving from one 11g release to another 11g release. The advantage of this is we can still have custom configurations which are configured in 11.1.1.3.0 version. Because technically this just upgrade the new BI binaries not the configurations.

As you all know how to do the out-of-place upgrade. Today am going to explain about in-place upgrade.

Here are the basic steps of the ‘in-place upgrade’. And also you can find the upgrade document @ http://download.oracle.com/docs/cd/E21764_01/bi.1111/e16452/bi_plan.htm#BABECJJH

  1. Download the appropriate Product Installers
  2. Patch Oracle WebLogic Server to the latest version (10.3.5)
  3. Run the Oracle BI Product Installer, and perform a Software Only installation, specifying the existing Middleware home to be upgraded.
  4. Run the Patch Set Assistant for each of the Oracle BI schemas created with RCU.
  5. Upgrade BI system components
  6. Update Fusion Middleware Shared Libraries
  7. Update configurations and stores
  8. Upgrade code grants (that is, security policy artifacts) for Oracle BI
  9. Upgrade OBIEE catalogs
  10. Start servers and processes.

Before you start perform the following general pre-upgrade tasks:

  • Stop all WebLogic Servers, Node Manager, OPMN, and OPMN-managed system components that are part of all Oracle BI domains that use the Middleware Home that you must upgrade.On Windows systems, also stop the component that is called Oracle WebLogic NodeManager (name).
  • Back up directories.

 

Patch Oracle WebLogic Server to the latest version (10.3.5):

 

With OBIEE 11.1.1.3.0 installation we will have WebLogic Server (WLS) is 10.3.3. But the new OBIEE 11.1.1.5.0 requires weblogic 10.3.5. so you need to upgrade this to 10.3.5 before installing/upgrading OBIEE. In order to upgrade weblogic you will need this 10.3.5 upgrade version of WLS, which you can download from Oracle Metalink site.

Upgrade WebLogic Server

1. After unzip the downloaded file, launch wls1035_upgrade_generic.jar if you’re on Windows 64bit family.(e.g.: java –jar wls1035_upgrade_generic.jar)

2. Accept all the default values and keep ‘Next’ till end, and start the upgrade.

Once the upgrade process completes you’ll see the following window. But don’t select Run QuickStart checkbox and click Done button.

 

Run the Oracle BI Product Installer, and perform Software Only installation:

Download the OBIEE 11.1.1.5 version from  OTN page.

1. Launch the installer by double click ‘setup.exe’ (for Windows)

2. Select ‘Software Only Install’ option

3. Select your original Middleware Home where you installed OBIEE 11.1.1.3.

4. Click ‘Install’ button to start the installation.

This upgrades the OBIEE System to 11.1.1.5.0 from 11.1.1.3.0

Run the Patch Set Assistant for each of the Oracle BI schemas created with RCU:

You need to upgrade the BIPLATFORM and MDS Schemas. Run the Patch Set Assistant for each of the Oracle BI schemas created with RCU.Update the MDS schema first.

  1. MDS
  2. BIPLATFORM

Upgrade MDS schema:

psa.bat -dbConnectString Shivapc:1521:orcl -dbaUserName sys -schemaUserName DEV_MDS

Upgrade BIPLATFORM schema:

psa.bat -dbConnectString Shivapc:1521:orcl -dbaUserName sys -schemaUserName DEV_BIPLATFORM

 

Upgrade BI system components:

This step is required for any system component that is associated with a WebLogic domain.

After you have patched your system component software that is associated with a WebLogic domain, you must run E:\MW\Oracle_BI1\opmn\bin\upgradenonj2eeapp.bat (on Windows operating systems) script to update your system components.

Before running this script, make sure:

  1. The Administration Server is up and running.
  2. The OPMN instance in the bin directory in the Instance home is up and running.

Here is the syntax for the ‘upgradenonj2eeapp.bat command.

upgradenonj2eeapp.bat
-oracleInstance Instance_Home_Location
-adminHost WebLogic_Server_Host_Name
-adminPort administration_server_port_number
-adminUsername administration_server_user

And here is an example:

cd E:\MW\Oracle_BI1\opmn\bin
upgradenonj2eeapp.bat -oracleInstance E:\MW\instances\instance1 -adminHost Shivapc -adminPort 7001 -adminUsername weblogic

Update Fusion Middleware Shared Libraries:

 

Upgrade Shared Library (JRF)

For each WebLogic Server domain, you must run the updateJRF() WLST command to update the shared libraries in your domain. Before you do this, you need to stop all running instances, Managed Servers, Administration Server, and Node Manager in the domain.

Here is an example of the ‘upgradeJRF()’ command:

cd E:\MW\oracle_common\common\binwlst.cmdupgradeJRF(‘ E:/MW/user_projects/domains/bifoundation_domain’)

Upgrade Fusion Middleware Security (OPSS)

For each WebLogic Server domain, you must run the upgradeOpss() WLST command to update your configurations and stores from previous releases to Release 11.1.1.5.0 configurations and stores using a system-jazn-data file in Release 11.1.1.5.0. You can use ‘upgradeOpss()’ WLST command. Here is a syntax for the command.

upgradeOpss(jpsConfig=”existing_jps_config_file”, jaznData=”system_jazn_data_file”)

The ‘existing jps-config.xml file can be found under E:\MW\user_projects\domains\bifoundation_domain\config\fmwconfig\jps-config.xml and the ‘system_jazn_data_file’ can be found under E:\MW\oracle_common\modules\oracle.jps_11.1.1\domain_config\system-jazn-data.xml.

And here is an example:

cd E:\MW\oracle_common\common\binwlst.cmdupgradeOpss(jpsConfig=”E:\MW\user_projects\domains\bifoundation_domain\config\fmwconfig\jps-config.xml”, jaznData=”E:\MW\oracle_common\modules\oracle.jps_11.1.1\domain_config\system-jazn-data.xml”)exit()

Upgrade Code Grants for Oracle BI Domain

If you are updating to the latest version of Oracle Business Intelligence (BI) from Release 11.1.1.3.0, you must run the bi-upgrade.py script in each Oracle BI domain. This script configures the code grants necessary to ensure that SSL works correctly for Oracle BI, and must be run even if SSL is not used. And if you have multiple BI domains (Enterprise deployment) then you need to run this on each domain.

Here is an example:

cd E:\MW\oracle_common\common\binwlst E:\MW\Oracle_BI1\bin\bi-upgrade.py –bioraclehome E:\MW\Oracle_BI1 –domainhome E:\MW\user_projects\domains\bifoundation_domain

Upgrade OWSM Policy Repository

This is to upgrade OWSM (Oracle Web Service Manager) policy repository, you can use WLST command ‘upgradeWSMPolicyRepository()’. In order to run this command you need to have your WebLogic Server up-and-running. Here is an example.

cd E:\MW\user_projects\domains\bifoundation_domain\binstopWebLogic.cmdcd E:\MW\oracle_common\common\binwlst.cmd
connect (‘weblogic’,’weblogic14′,’t3://Shivapc:7001′)
upgradeWSMPolicyRepository()exit()

Upgrade OBIEE catalogs:

When updating your Oracle Business Intelligence (BI) software from Release 11.1.1.3.0 to 11.1.1.5.0, you must manually update your Oracle BI Presentation Catalogs. Instructions are provided below:

  • Shut down Oracle BI Presentation Services using Oracle Enterprise Manager.
  • Back up your Release 11.1.1.3.0 catalogs by using the 7-Zip utility to create a compressed file for it.
  • Create a backup copy of the instanceconfig.xml file.

The instanceconfig.xml file is located in the E:\MWH\instances\instance1\config\OracleBIPresentationServicesComponent\ coreapplication_obips1.

Change the upgradeAndExit option to true in the instanceconfig.xml file.

Find the following code:

<ps:Catalog xmlns:ps=”oracle.bi.presentation.services/config/v1.1″>

   <ps:UpgradeAndExit>false</ps:UpgradeAndExit>
</ps:Catalog>

Change it to the following:

<ps:Catalog xmlns:ps="oracle.bi.presentation.services/config/v1.1">
   <ps:UpgradeAndExit>true</ps:UpgradeAndExit>
</ps:Catalog>
  • Start Oracle BI Presentation Services using the following OPMN command the update the catalogs:
  • opmnctl startproc ias-component=coreapplication_obips1

For example, On a Windows operating system:

cd E:\MW\instances\instance1\bin
opmnctl startproc ias-component=coreapplication_obips1
  • After the catalogs are updated, edit the instanceconfig.xml file again and change the upgradeAndExit option back to false.
  • Restart Oracle BI Presentation Services using Fusion Middleware Control.

Login to analytics and make sure it’s working fine.

 

 

Thanks,

Shiva

Advertisements
 
4 Comments

Posted by on June 19, 2011 in BI Publisher, OBI EE, OBIEE 11g

 

Tags: , ,

4 responses to “OBIEE 11.1.1.3.0 to 11.1.1.5.0 – In-Place-Upgrade

  1. Rajkiran Taraka

    June 21, 2011 at 3:16 pm

    Thanks Siva…

     
  2. Paula

    July 1, 2011 at 12:56 am

    Hi Shiva,

    I can not do the step Upgrade BI system components. Admin Server is running and opmnctl too. But I get the following error:

    SEVERE: Command failed:
    oracle.as.config.ProvisionException: Exception while unregistering the instance
    at oracle.as.config.impl.OracleASInstanceImpl.unregister(OracleASInstanceImpl.java:289)
    at oracle.as.config.impl.OracleASInstanceImpl.unregister(OracleASInstanceImpl.java:249)
    at oracle.as.config.provisioner.commands.UnregisterInstanceCommand.execute(UnregisterInstanceCommand.java:34)
    at oracle.as.config.provisioner.InstallerCmdLine.run(InstallerCmdLine.java:146)
    at oracle.as.config.provisioner.InstallerCmdLine.main(InstallerCmdLine.java:46)
    Caused by: oracle.as.config.impl.SimpleProvisionException: Failed to unregister instance instance1. It does not exist on the adminserver.
    at oracle.as.config.impl.OracleASInstanceImpl.unregisterInstance(OracleASInstanceImpl.java:431)
    at oracle.as.config.impl.OracleASInstanceImpl.unregister(OracleASInstanceImpl.java:273)
    … 4 more

     
  3. mishrahv

    August 9, 2011 at 3:33 pm

    Hi Shiva,

    I have a question on dowloading weblogic server for upgrade. I see following versions on Oracle Weblogic Download Page, which one I have to download?

    (1)
    Oracle WebLogic Server 11gR1 (10.3.5) + Coherence + OEPE – Package Installer

    (2)
    Oracle WebLogic Server 11gR1 (10.3.5) + Coherence –
    Package Installer

    (3)
    Oracle WebLogic Server 11gR1 (10.3.5)
    ZIP Distribution

    (4)
    Oracle WebLogic Server 11gR1 (10.3.5) Supplemental ZIP distribution

    Waiting for your reply…

    Thanks

    HM

     

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: