Proactive insights, news and tips from Oracle Fusion Middleware Support. Learn Oracle from Oracle.

WebCenter Content Server; Patching Changes

So, what "version" is the smart-phone that you are carrying?  Personally, I have an "S6-Active Lollipop."  I don't know about you, but "S6-Acvite Lollipop" sounds more like an NFL's offensive formation that a quarterback might call for a play, than a phone.  What version is your Word Processor?  Chances are, you probably don't even know the version number but it looks something like "14.0.7128.5000(64)" easy, right?  The truth is, we live in a technological world that has many more options for developers than it used to.  Obviously, you would need a different version of your favorite Word Processor if you were running Linux, XP, NT, 2010, 7, Mobile, or some other platform. 

For this, and many other reasons, developers need a way to differentiate the versions they're writing code for.  They also need to present the customer with an easy enough "version number" so that the customers know what they have and when to upgrade, etc.  This is harder than it looks.  Recently, the development team for WebCenter Content server has made a change to the way they release their Bundle Patches.  Have a look at the table below:

See anything strange?  There's no Bundle Patch 7!  Instead, you have this weird number, 151221.  This is "Developer Shorthand" for 2015, December 21st.  That's easy enough to deal with, but there's a hitch!  This patch may be have been released on the 21st of December, but it was entered into the development system a bit earlier than that.  The development team actually started to assemble this patch for final release on the 11th of December (not the 21st).  Why would you care?  Well, once you install this patch, you'll probably have the urge to check your Configuration Page and to look at the version, to make sure you installed the patch properly.  Well, the date in the Configuration Page will match this earlier date, and not the release date!

Here's an example: Have a look at the WebCenter Configuration page.  According to this, WebCenter Content Server is running Version  This version is accurately being reported after installing the 151221 patch. 

Time for the million dollar question... "How do I know which patches will report which versions in my Configuration page?  Well, "There's an App for that!"  More accurately, there's a NOTE for that.  If you read Note 1509747.1, you'll see 4 columns for each major release of Content Server.  The first column has a list of available patches for that particular version.  The second column has a status (like "Fully Released" for example).  Column three has the release date, and the last column will have the "Reported Date" that will appear in the Configuration Page (as shown here on the right). 

This note is important and should be added as a favorite.  There will also be a similar note published for v12c of Content Server, as soon as patches are released for it.  Remember, you can also visit the "Patches" tab of My Oracle Support (MOS) to search for patches as well.

Join the discussion

Comments ( 2 )
  • Jonathan Hult Wednesday, January 6, 2016

    I fail to see why Oracle cannot make the two dates match. This seems like a poor release process to me.

  • guest Thursday, January 7, 2016

    I agree, Jonathan. I've passed your comment (along with others) back to the Development team.

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.