Weblogic Patching Method Changes , Prior to 12.1.1, On and after 12.1.2

Weblogic Patching Method Changes , Prior to 12.1.1, On and after 12.1.2

Weblogic Server Patching, CPU ( Critical Patch Update ) and PSU ( Patch Set Update )

As I have explained in my earlier post "Weblogic Server Patching" - 

BSU ( Smart Update ) utility can be used to apply patch below weblogic 12.1.2 versions, but Opatch utility 12.1.2 on-wards.

From Weblogic 10.3.4, Oracle has started releasing PSU ( Patch Set Update ) and same can be applied to the Weblogic server.

CPU ( Critical Patch Update ) & PSU ( Patch Set Update )

Earlier Oracle were releasing CPU ( Critical Patch Updates ) every quarterly for weblogic Server. CPU is one of the specific patch to fix some of the critical issues encountered in some of the production environment of the some client, Which could be generic and may impact other client production as well thus, Oracle release that as CPU for all clients to apply. 

PSU is Patch Set Update and it's cumulative. Means every release of PSU included all previously release patches, CPU as well as all other released patches. It's a bundle of critical fixes as well as few more fixes those are not critical but can impact production environments of clients anytime.

So, if you are going to apply PSU then don't bother about previous patches and conflictions, since it's included all previous patches as well so during apply, it will remove all previous applied patches automatically and apply again with new patches and will increment you patch set update no by one, for example from 10.3.4.0.1 to 10.3.4.0.2.


Note -  Oracle has started releasing that doesn't mean it's not going to release CPU's, it's still there for previous versions of Weblogic 10.3.4 wherever applicable.


PSU Tracking & Versioning

Earlier Oracle were using 3 number standard format for version like, in 10.3.4, 10 is Major version, 3 is minor version and 4 is patch set or you can say service pack. Now after PSU, oracle has started using 5 number versioning format, like 10.3.4.0.1, Where 10.3.4 meaning is same i have explained, 4th digit "0" reserved for some future use and last number 1 is representing patch set update.

So, Like in WebLogic Server 11g  [10.3.1+], product versions are numbered a1.a2.a3.a4.a5 where

• a1=Is the major version
• a2=Is the minor version
• a3=patch set or you can say maintenance pack or service pack
• a4=it reserved for future use
• a5=PSU (patch set update)

Last a5 will maintain for PSU's and will increment with each new PSU release like 10.3.4.0.1 then 10.3.4.0.2 etc.

So by this, it will help all to maintain and remember only one last digit to know which patch set update was applied instead of remembering all applied on off patches ( CPU's ).


There is a difference in versioning WLS 12c onwards as below 

Version number contain 5 decimal places and versioning maintained as below

Suppose if your weblogic version if Weblogic 12c ( 12.1.2.0.0 ) then 

• The first two decimal places together describe the Major Version number, for example "12.1" in 12.1.2.0.0.
• The first three decimal places together describe the Minor Version number, for example "12.1.2" in 12.1.2.0.0
• According to the version conventions, a Patch Set release for WebLogic Server 12.1.2.0.0 would increment the fourth decimal place, for example 12.1.2.1.0.
• Patch Set Update releases are named uniquely by incrementing the fifth decimal place, for example 12.1.2.0.1

So, Net Net

In WebLogic Server versions up to 12.1.1, Smart Update should be used to install/uninstall both interim and PSU patches.

In WebLogic Server 12.1.2 and higher, OPatch should be used to install/uninstall both interim and PSU patches