In-Place Upgrading of OBIEE 11.1.1.3 to 11.1.1.5

May 13th, 2011 by

If you read my roundup of the new features in OBIEE 11.1.1.5 the other day, you may have noticed my comment about upgrades being “out of place”; this is where you install the new version of a product in a new Middleware Home, and migrate all the metadata from the old installation to the new one. This has the virtue of simplicity, but if your current installation is heavily customized and you’ve got lots of analyses, LDAP users and so on, you might prefer to upgrade your current installation “in-place”.

Because of the move to integrate OBIEE closer into Oracle Fusion Middleware, the in-place upgrade process is actually a bit complex, and in Fusion Middleware terms is referred to as “Applying the Latest Oracle Fusion Middleware Patchset”. To do such an in-place upgrade, you need to perform the following tasks.

Warning : Make sure you back-up your existing system before attempting an upgrade such as this. Read through the“Applying the Latest Oracle Fusion Middleware Patchset” documentation from Oracle and make sure that your system does not require any additional steps, or different steps. If you spot any issues or missed steps from this guide, add them to the comments and I’ll factor them in. It also makes the following assumptions:

  • You are running 32-bit Windows version of OBIEE 11.1.1.3 and WebLogic Server 10.3.3.
  • You have installed OBIEE 11g at c:\oracle\middleware
  • You have a single node install, with no vertical or horizontal scale-out

With that in mind, at a high-level, the steps to perform the in-place upgrade are:

  1. Upgrade Oracle WebLogic Server from 10.3.3 to 10.3.5
  2. Run the 11.1.1.5 installer against the current Middleware Home, and use the Software-Only Install option
  3. Run the Patchset Assistant to upgrade the BIPLATFORM and MDS schemas
  4. Run some WebLogic and Fusion Middleware post-patching tasks
  5. Run some OBIEE-specific post-upgrade tasks

Before you start, you’ll need two pieces of software; firstly, the WebLogic Server Upgrade Installer (wls1035_upgrade_win32.exe, for Windows 32-bit), which you have to obtain from Metalink using patch no. 12395560, again for Windows 32-bit. Secondly, you’ll need the full OBIEE 11.1.1.5 installer, which you can download directly from OTN. Then, follow these steps:

1. Pre-Patching Steps

Shut down any existing WebLogic, OPMN and OBIEE processes, including any Windows processes that you might see running in Task Manager (taskmgr.exe). This inclused beasvc.exe which normally stays running even after you’ve shut down the WebLogic administration and managed services.

Now take a backup of the Middleware Home directory and all it’s subdirectories, and the BIPLATFORM and MDS schemas.

2. Upgrade WebLogic Server to 10.3.5

Now, with the WebLogic Server Upgrade Installer that you downloaded from metalink, run the installer and point it to the existing WebLogic Server installation, like this:

Press Next at all the prompts, accept all the default and let the installer upgrade WebLogic Server for you.

3. Whilst the Upgrade Installer upgrades WebLogic for you and also copies an updated version of JRockit JVM to your installation, the WebLogic domain isn’t configured to use it yet. To enable this, using a text editor, locate the file C:\oracle\Middleware\user_projects\domains\bifoundation_domain\bin\setDomainEnv.cmd and change the references to the old JRockit directory to the new one; for example:

Where C:\oracle\Middleware\jrockit_160_24_D1.1.2-4 is the location of the updated JRockit JVM.

3. Perform a Software-Only Install of OBIEE 11.1.1.5

Next, start up the OBIEE 11.1.1.5 Universal Installer, and when prompted, select Software-Only Install as the install option, like this:

At the next prompt, select the existing Middleware Home for your OBIEE 11.1.1.3 installation, and then accept the defaults for the remainder of the prompts. The Universal Installer will then upgrade your OBIEE 11g software for you, to version 11.1.1.5.

4. Upgrading the BIPLATFORM and MDS Schemas

Now you need to upgrade the two schemas that OBIEE 11g uses. To do this, you use the Patchset Assistant, using the following commands (replace the middleware home location, and localhost:1521:orcl, with appropriate details for your environment)

5. Upgrade Your System Components

The system components (Oracle BI Server, Oracle BI Presentation Server etc) within your instance now need to be de-registered, and then re-registered, with your WebLogic domain. To do this, use these commands (again, adjust for your environment, including the “weblogic” username at the end of the last command).

6. Upgrade Fusion Middleware Shared Libraries, and Security Elements

Next you have to perform some maintenance work using WLST, the WebLogic Scripting Tool. Start by shutting down the WebLogic Server administration server, and then follow the rest of these steps. [Note : an earlier version of this posting had the wrong paths for the CD command before the WLST call and some missing commands - apologies for this, the correct paths and commands are highlighted in bold below]

7. Upgrade the Oracle BI Presentation Server Catalog

The final step is to upgrade the Web Catalog. To do this, ensure that the Presentation Server is shut down, edit the instanceconfig.xml file to enable the catalog upgrade, and then restart the Presentation Server.

Now use a text editor to open the fileC:\oracle\Middleware\instances\instance1\config\coreapplication_obips1\instanceconfig.xml, and change the reference:

to:

Now start the Presentation Server component, and once done, change the entry back to the original “false” value and stop the Presentation Server again.

8. Reboot, and Check your System

Once you’ve completed all these steps, reboot your server and then restart all the OBIEE components. You should then be able to start Enterprise Manager from your Web browser, and check that you’re now running version 11.1.1.5 of OBIEE.

So, it’s definitely possible to upgrade OBIEE 11g in-place, but there’s quite a few fiddly steps. You might still want to consider a full, new installation of OBIEE 11.1.1.5 and then manually migrate your metadata and settings over, but if you want to upgrade to 11.1.1.5 over your existing installation, this should help you get started.


Comments

  1. Sam Says:

    Hello Mark,

    It sure is a good start but I ran into a lot of errors. Stuck at step 6 right now.

    Get the following error when I run the WLST command:

    jpsConfigFile = c:\orcl\OBIEE11g\user_projects\domains\bifoundation_domain/confi
    g/fmwconfig/jps-config.xml
    jaznDataFile = c:\orcl\obiee11g\Oracle_BI1/bifoundation/admin/provisioning/bi-p
    olicystore.xml
    invoking: upgradeOpss( jpsConfig=”c:\orcl\OBIEE11g\user_projects\domains\bifound
    ation_domain/config/fmwconfig/jps-config.xml”, jaznData=”c:\orcl\obiee11g\Oracle
    _BI1/bifoundation/admin/provisioning/bi-policystore.xml”) …
    Problem invoking WLST – Traceback (innermost last):
    File “c:\orcl\obiee11g\Oracle_BI1\bin\bi-upgrade.py”, line 54, in ?
    NameError: upgradeOpss

    Any suggestions?

  2. Mark Rittman Says:

    A couple of points / observations on top of this.

    1. It’s really important that the WebLogic upgrade goes OK. I ran it once before, and it failed at about 50% due to components still being used elsewhere; basically, beasvc.exe was still running even after I ran the scripts to shutdown my WLS administration and managed services. After I shut beasvc.exe down, I re-ran the update installer, it completed fine, but several steps down the line I couldn’t start WLST.cmd, and therefore couldn’t complete the upgrade.

    2. There is a step detailed in the docs that says you should run the upgradeOpss() WLST command. I did this, but then found it was duplicated in an OBEE-specific script (bi-upgrade.py) that the docs ask you to run afterwards, so I left updateOpss() off of my instructions.

    3. There is also a step at the end where you are asked (in the docs) to update the BIAdministrator principal – this is the application policy that determines Java permissions for the BIAdministrator application role. Unfortunately when I amended the policy using the instructions, EM reported an error, and so given that the new permissions relate solely to RTD, and I don’t intend to use RTD, I skipped this step, and another one afterwards that was specific to RTD.

    So overall, the process works, but what Oracle really need to produce an upgrade option in the Universal Installer, rather than just have you do a software-only install into the existing middleware home and then make all the configuration changes yourself. What the upgrade installer should do is:

    - upgrade WLS for you (and also therefore avoid you needing to go to metalink and get the software – this will catch all “unsupported” users out)
    - Amend the WLS environment script to make use of the new JRockit JVM
    - Upgrade the software in the middleware home
    - Have a configuration stage that runs through all the processes that we have to do manually in my blog post

    Hopefully this is something they will consider at some point, as at present, it’s far easier for a customer to do an out-of-place upgrade and manually migrate the RPD, catalog objects over afterwards.

    regards, Mark

  3. Mark Rittman Says:

    Sam,

    If you get a name error on upgradeOpss(), it sounds like you’re running WLST from the wrong location, and the JARs to contain Oracle’s FMW extensions to WLST aren’t being picked up. Re-check the documentation and make sure you run WLST from the correct filesystem location – I think it’s [middleware_home]/oracle_common/common/bin, but check yourself.

    Mark

  4. David.Zhang Says:

    Hi Mark
    I try to do according the setps, It’s Ok from setps1 to steps4, but It’s responded error message on the step5′supgradenonj2eeapp.bat -oracleInstance C:\oracle\Middleware\instances\instance1 -adminHost localhost -adminPort 7001 -adminUsername weblogic

    Do you have any good suggestions? thanks!
    David

  5. Mark Rittman Says:

    David,

    What error message do you get? Were you doing anything unusual, or different from my steps, when you hit this error?

    regards, Mark

  6. Maxime Says:

    Hi Mark, thanks a lot for the quick testing of this new version. It sure is very helpful for early adopters like us !

    You mention 32-bit as a prerequirement but we are running 11.1.1.3 in a 64-bit environment. Are you seeing anything that could be a problem with that or is it only because you simply haven’t tested it ?

    Thanks

    Maxime

  7. Mark Rittman Says:

    Maxime,

    No, I’ve only tested in a 32-bit environment. I’ve seen nothing to suggest that 64-bit will be an issue. but based on 11.1.1.3 there might be some things that crop up. You’ll obviously need to test in a 64-bit environment to be sure it all works OK.

    regards

    Mark

  8. Mark Van den Meerssche Says:

    As David was mentioning, I also get errors on step 5:
    “Exception while unregistering the instance”

    Caused by… Failed to unregister instance instance1. It does not exist on the adminserver.

    regards, Mark

  9. Mark Rittman Says:

    Mark

    Have you carefully checked all the parameters you have passed to the opmnctl command? Is the Admin Server actually running, along with OPMN? Are you connecting to the correct Admin Server?

    If all else fails, go back to the full documentation detailed on the blog post, and carefully go back through all the steps. It should work, but there may be a step I missed that is important for you, or there may be some quirk of your system. But I suspect it’ll be a typing error or a step missed, as it did all work on my environment.

    Mark

  10. John Says:

    Mark,

    RE: Sam’s Question – you are correct the documentation oracle provides is specific to a WLS only install at this step. The WLST command should be run from: d:\orcl\mw_bi\oracle_common\common\bin (or something similar) – I had the same issue from the wlserver_10.3 directory.

    Couple other notes on a 64BIT upgrade:
    1. I noticed I needed the boot.properties file in \ORCL\MW_BI\user_projects\domains\bifoundation_domain\servers\AdminServer\security as it had the encryption flag but the ID/PW was not encrypted.
    2. I had the same error as the upgradenonj2eeapp.bat the first time I tried. The second I did not alter my setDomainEnv.cmd and it worked.

    Keep in mind I’m on a 64Bit Windows Env.

  11. Matthijs Says:

    Mark,

    When I do a clean 11.1.1.5 install and want to use my 11.1.1.3 developments, should I also upgrade the BIPLATFORM and MDS Schemas and the web catalog?

    A new BIPLATFORM and MDS schema should be created for the 11.1.1.5 install I assume?

    Regards,
    Matthijs

  12. Mark Rittman Says:

    @Sam, @John

    Yes you are correct, I had the wrong path in the script for the CD prior to the WLST calls. Not sure how this happened, apologies for this. The path to call WLST (according to the docs, and which worked for me) was:

    cd c:\oracle\middleware\oracle_common\common\bin

    I’ve updated the section accordingly.

    Mark

  13. Mark Rittman Says:

    @Matthijs

    Yes, In theory this should be correct, however I’ve not tried it myself.

    Mark

  14. Alekh Says:

    Dear Mark,

    with regards to your comment.
    my comment about upgrades being “out of place”; this is where you install the new version of a product in a new Middleware Home..

    We do not have many customizations in our 11.1.1.3 and we want to go with 11.1.1.5 “out of place” upgrade seems good for our setup. Where can I get a document on this?

    Thanks for the help
    Alekh

  15. Knut Says:

    Hi,

    for 64 bit Windows the jrockit is not included in the upgrade – at least in my case.

    Regards,

    Knut

  16. Mohammed Irfan Khan Says:

    In Out of place upgrade we might have to (correct me if I am wrong)

    1) New instanceconfig.xml has to be synced up with old one.
    2) New NQSConfig has to synced up as well. Esp. parameter which have been changed from default values.
    3) Also would need to take care of WebLogic customizations if any?
    4) Install possibly will need to be done on the same host as original environment to avoid hardcoded hostname values in config files.
    5) Port conflict will need to be avoided

    I might be missing few more things

    IK

  17. OR Says:

    Hi,

    I have upgrade OBIEE from 11.1.1.4 to 11.1.1.5 and after I start the BI services launch the weblogic server and start well but when it begins th bi services only show RUNNING and that all!

    Any help will be appreciated

  18. OR Says:

    Hi Mohamed, I follow the guide.

    I am not a experienced consultant of OBI so I do not know how to apply all the points that you mentioned.

  19. gcoculo Says:

    I’m upgrading but the command:
    upgradeOpss(jpsConfig=”E:/bi/Middleware/user_projects/domains/bionit_domain/config/fmwconfig/jps-config.xml”, jaznData=”E:/bi/Middleware/oracle_common/modules/oracle.jps_11.1.1/domain_config/system-jazn-data.xml”)

    restituisce il seguente errore:

    Starting upgrade of jps configuration and security stores.
    COMMAND FAILED due to an unknown reason, Check the stack trace for details
    Traceback (innermost last):
    File “”, line 1, in ?
    File “E:\bi\MIDDEL~1\ORACLE~1\common\wlst\jpsWlstCmd.py”, line 1270, in upgradeOpss
    at oracle.security.jps.upgrade.tools.utility.Upgrade.validateArgs(Upgrade.java:261)
    at oracle.security.jps.upgrade.tools.utility.Upgrade.upgrade(Upgrade.java:108)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)

    java.lang.IllegalArgumentException: java.lang.IllegalArgumentException: Illegal jps config file. please make sure the provided jps config file exists.

    This implies a generic safety issues in OBIEE.

    What should I do?

    thanks

    Gianluca

  20. Chris M. Says:

    I am doing the In-Place upgrade. At Step 3. Perform a Software-Only Install of OBIEE 11.1.1.5 I am getting an error on Step 5 of 8 Specify Installation Location. I point to location of 11.1.1.3 and there is an error in bottom panel “An Application Server must already be installed” and it will not proceed. any idea what is causing this? The 11.1.1.3 version was working before this upgrade.

  21. Hitesh Says:

    Hello Mark,

    I have a quick question. I am planning the out-of-place installtion of 11.1.1.5. Will my 11.1.1.3 RPD Work with 11.1.1.5 Environment?

    Thanks
    Hitesh

  22. Prashanth Thalla Says:

    Hello Mark,

    I having trouble running Upgrade code grant for oracle BI domain which uses the bi-upgrade.py. When I run this from WLST scripting tool, it throws a syntax error which looks like below.

    “Initializing WebLogic Scripting Tool (WLST) …

    Welcome to WebLogic Server Administration Scripting Shell

    Type help() for help on available commands

    wls:/offline> /opt/middleware/Oracle_BI1/bin/bi.upgrade.py –domainhome /opt/middleware/user_projects/domains/bifoundation_domain –bioraclehome /opt/middleware/Oracle_BI1
    Traceback (innermost last):
    (no code object) at line 0
    File “”, line 1
    /opt/middleware/Oracle_BI1/bin/bi.upgrade.py –domainhome /opt/middleware/user_projects/domains/bifoundation_domain –bioraclehome /opt/middleware/Oracle_BI1
    ^
    SyntaxError: invalid syntax”

  23. Bunker Says:

    How does one go about with upgrade of Siebel Analytics 7.8.5 to OBIEE 11g along with DAC? Are there any special routines to be run?
    I am sure there are more infrastructure components in OBIEE 11g given the fact that Fusion Middleware is playing a larger role and the Siebel Analytics 7.8.5 is pretty old. This may not allow a smooth upgrade of the very old version to latest OBIEE 11g version. Any help appreciated.

  24. Kevin Jacox Says:

    Gianluca:

    Try using double slashes in the diretory path.

    Example:

    upgradeOpss(jpsConfig=”E:\\bi\\Middleware\\user_projects\\domains\\bionit_domain\\config\\fmwconfig\\jps-config.xml”, jaznData=”E:\\bi\\Middleware\\oracle_common\\modules\\oracle.jps_11.1.1\\domain_config\\system-jazn-data.xml”)

Website Design & Build: tymedia.co.uk