Patch OBIEE the quicker way – with OPatch napply

July 4th, 2013 by

Since 2012, Oracle’s patching strategy for OBIEE has been Bundle Patches released approximately once a month. These bundle patches are usually cumulative ones, applied on top of the .0 version of the product. Patching is done through Oracle’s standard OPatch tool, which manages the application of patches along with an inventory of them and rollback if necessary.

I’ve previously written about the overall patching process here. OPatch is part and parcel of an OBIEE sysadmin’s life, so I wanted to share this short article to show the quicker way to apply the PSUs. It uses a more direct way than the patch documentation describes, taking advantage of the napply option of OPatch (documented here). By using this option OPatch will apply all listed patches in one go, rather than one at a time. As well as this, we can use the silent flag to stop OPatch from prompting to apply each patch in turn.

  1. Download the necessary patches – for 11.1.1.7.1 this is 16569379 and 16556157. In a server environment you can use wget to download the patches as detailed here.
  2. Validate the checksums for the downloaded files, to make sure they didn’t get corrupted during download. Use the Digest link when downloading to view the checksums. For example, the Linux x86-64 checksums are :
  3. Unzip the patches. Within the main patch (16556157) there are a series of further zip archives – unzip these too
  4. Put all the patch folders in a single folder, so it looks something like this:

    Patches on Linux

    Patches on Windows

  5. Take backups, as described in the patch documentation.
  6. Set your environment variables, setting PATCH_FOLDER to the folder you unzipped the patches to in step 4 above, and ORACLE_HOME to your FMW_HOME/Oracle_BI1 folder
    1. Windows:
    2. Linux:
  7. Shut down OPMN, the Managed Server and the Admin Server
  8. Apply all the patches in one go, with no prompting:
    1. Windows:
    2. Linux:
  9. Validate that they’ve been applied – the following should list all seven patches plus the bugs they fix:
  10. Per the instructions in the README.html for patch 16453010 for post-patch actions:
    1. Windows:
    2. Linux:

    (NB the msmdacc64.dll didn’t exist on either of my installations that I’ve tried this on)

  11. Start up Admin Server, Managed Server, and OPMN. Login to OBIEE and check the new version:
  12. Don’t forget to check the README.html for patch 16453010 for full instructions on updating the client, customised skins, mapviewer config, etc.

Tags: , , , ,

Comments

  1. Thomas Says:

    Thanks for another interesting post.
    I never understood why Oracle can’t include such extremely simple steps like deleting or copying a file (in this case Desktop*.exe) in a proper patching routine. Would you be aware of any reasoning for this?
    I think Oracle has much to improve on this kind of things i.e. compared with applying patches to any modern Operating System which likely are more complex behind the scenes but easier for the Sysadmins to apply.

  2. Stewart Bryson Says:

    This was awesome Robin. I wrote an apply script that applied the entire patch. I don’t know how we missed this for so long.

  3. Christian Says:

    Robin,

    This is a great find. I wasn’t aware that this existed. This is certainly a time saver and a great tip.

    Cheers,
    Christian

  4. jonathan mcgowen Says:

    Has anyone run into issues with patch #3 – 16916026? It’s looking for this file which doesn’t exist in the patch — \products\Essbase\eas\server\tomcat\webapps\eas.ear.

    I’ve unzipped the patch twice just to make sure. I downloaded in the bundle zip 16556517, and patches 1 & 2 applied successfully.

  5. jonathan mcgowen Says:

    To follow up my previous comment – I re-extracted 16916026 from 16556517, and the patch successfully applied this time. For some reason not all files extracted the first time. Go figure.

  6. Mike Brookes Says:

    Hi Robin
    Went like a dream – I didn’t install the 16569379 patch as the readme said unless you were experiencing the specific problems this patched, then best wait for the official opatch in a future version, as it is not supported yet…other than that eveything went as planned :-)
    cheers
    Mike

Website Design & Build: tymedia.co.uk