By William Sescu
A new OUD bundle patch was release at the 18th of July 2017, and this gives me the opportunity to show how fast an OUD can be patched, if configured correctly. In case you have an OUD multi master replication with a load balancer virtual IP on top, then zero downtime patching is possible. This is the configuration that I usually recommend. Not only for high availability, but also for maintenance.
A typical OUD installation consists not only of the OUD itself, but also of a few other components like the JDK, the WebLogic and the ODSM which is deployed in WebLogic and the last but not lease the OPatch utility.
In the end, for upgrading successfully to the OUD to bundle patch 11.1.2.3.170718 we need the following patches.
- Patch 25840309: OUD BUNDLE PATCH 11.1.2.3.170718
- Patch 13079846: Oracle JDK 1.7.0 (build 1.7.0_151-b15)
- Patch 25869650: SU Patch [B25A]: WLS PATCH SET UPDATE 10.3.6.0.170718
- Patch 6880880: OPatch patch of version 11.1.0.12.9 for Oracle software releases 11.1.0.x (OCT 2015)
A few steps can be done beforehand, like patching the OPatch itself and rolling out the new JDK. No downtime is required for those steps. A very important part is the Java environment. If you have set it up like in the following blog, you can change to the new JDK by simply changing a symbolic link.
Ok. Let’s get started. Currently we do have the following patches in the staging area.
[dbafmw@dbidg01 20170718]$ ls -l total 698560 -rw-r--r-- 1 dbafmw oinstall 467017155 Jul 19 07:37 p13079846_17000_Linux-x86-64.zip -rw-r--r-- 1 dbafmw oinstall 98414546 Jul 19 07:33 p25840309_111230_Generic.zip -rw-r--r-- 1 dbafmw oinstall 95019336 Jul 19 07:38 p25869650_1036_Generic.zip -rw-r--r-- 1 dbafmw oinstall 54867592 Jul 19 08:34 p6880880_111000_Linux-x86-64.zip
And the following versions.
-- Current Java Version
[dbafmw@dbidg01 bin]$ ./java -version
java version "1.7.0_141"
Java(TM) SE Runtime Environment (build 1.7.0_141-b11)
Java HotSpot(TM) 64-Bit Server VM (build 24.141-b11, mixed mode)
-- Current WebLogic Version
. /u01/app/oracle/product/Middleware/11.1.2.3/wlserver_10.3/server/bin/setWLSEnv.sh
java weblogic.version -verbose
WebLogic Server 10.3.6.0.170117 PSU Patch for BUG24667634 FRI NOV 25 18:34:42 IST 2016 ImplVersion: 10.3.6.0
WebLogic Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050 ImplVersion: 10.3.6.0
-- Current OUD Version and OPatch version
[dbafmw@dbidg01 OPatch]$ ./opatch lsinv
Oracle Interim Patch Installer version 11.1.0.11.0
Copyright (c) 2017, Oracle Corporation. All rights reserved.
Oracle Home : /u01/app/oracle/product/Middleware/11.1.2.3/Oracle_OUD1
Central Inventory : /u01/app/oraInventory
from : /u01/app/oracle/product/Middleware/11.1.2.3/Oracle_OUD1/oraInst.loc
OPatch version : 11.1.0.11.0
OUI version : 11.1.0.11.0
Log file location : /u01/app/oracle/product/Middleware/11.1.2.3/Oracle_OUD1/cfgtoollogs/opatch/opatch2017-07-19_08-53-32AM_1.log
OPatch detects the Middleware Home as "/u01/app/oracle/product/Middleware/11.1.2.3"
Lsinventory Output file location : /u01/app/oracle/product/Middleware/11.1.2.3/Oracle_OUD1/cfgtoollogs/opatch/lsinv/lsinventory2017-07-19_08-53-32AM.txt
--------------------------------------------------------------------------------
Installed Top-level Products (1):
Oracle Unified Directory 11.1.2.3.0
There are 1 products installed in this Oracle Home.
Interim patches (2) :
Patch 25383162 : applied on Fri Jun 02 11:39:44 CEST 2017
Unique Patch ID: 21007593
Created on 8 Feb 2017, 02:26:53 hrs PST8PDT
Bugs fixed:
21110317, 24731779, 19596240, 20987332, 20786014, 19271756, 21024218
24333856, 21184039, 17409345, 22555819, 21569267, 19987242, 17416498
23703560, 22927723, 21835208, 21278352, 22308304, 24409239, 21620706
21225831, 21634829, 23317872, 21126991, 20771322, 21189204, 19670854
23327572, 22843404, 21097296, 23066020, 21298039, 21967348, 20688926
20813995, 17488044, 18311877, 21249082, 20198154, 20415424, 23032811
21207635, 21415093, 21831011, 21575993, 21882589, 17568241, 22611713
20363721, 21498205, 21301617, 24577814, 19991366, 21098103, 21932111
24390289, 21282258, 19636259, 24399724, 22916463, 20235234, 20630323
20113230, 20554639, 24481116, 24681490, 21924319, 20979061, 20469049
24490948, 22017920, 23195988, 22564810, 24565597, 22950438, 20881625
21169776, 20736946, 21032490, 22641166, 21644986, 21337744, 23262289
21509636, 21183856, 22369027, 22075202, 21464932, 20692543, 20805136
21754188, 21889432, 20924952, 21683538, 20554436, 24372668, 20881496
21527426, 23703466, 21605154, 24310538, 21959508, 22689164, 20875947
22119339, 20778847, 23207713, 21503767, 21310463, 20554511, 21387378
21075558, 22180844, 21665762, 20987758, 24405001, 20529805, 20470402
20381973, 21881962, 20830152, 23090053, 17406282, 21461976, 20989144
20180870, 20312191, 21111836, 22732230, 21387387, 19504096, 24544860, 18312432
Patch 21197325 : applied on Mon Mar 27 12:25:39 CEST 2017
Unique Patch ID: 18996262
Created on 3 Jul 2015, 07:28:59 hrs PST8PDT
Bugs fixed:
21197325
--------------------------------------------------------------------------------
OPatch succeeded.
Patching the OPatch itself is an operation which requires no downtime. You simply unzip the new OPatch in the OUD home. Please be aware that the OPatch version 11.1.x is needed for patching the OUD. Any other version is not supported. In my case I patch the OPatch from version 11.1.0.11.0 to version 11.1.0.12.9.
[dbafmw@dbidg01 20170718]$ cp p6880880_111000_Linux-x86-64.zip /u01/app/oracle/product/Middleware/11.1.2.3/Oracle_OUD1/ [dbafmw@dbidg01 20170718]$ cd /u01/app/oracle/product/Middleware/11.1.2.3/Oracle_OUD1/ [dbafmw@dbidg01 Oracle_OUD1]$ unzip p6880880_111000_Linux-x86-64.zip Archive: p6880880_111000_Linux-x86-64.zip inflating: OPatch/operr creating: OPatch/scripts/oms/ inflating: OPatch/scripts/oms/opatchauto.bat inflating: OPatch/scripts/oms/opatchauto inflating: OPatch/scripts/oms/generateMultiOMSPatchingScripts.pl creating: OPatch/scripts/oms/oms_child_scripts/ inflating: OPatch/scripts/oms/oms_child_scripts/opatchauto_fmw inflating: OPatch/scripts/oms/oms_child_scripts/opatchauto_fa creating: OPatch/scripts/oms/wlskeys/ inflating: OPatch/scripts/oms/wlskeys/createkeys.sh ... ... [dbafmw@dbidg01 OPatch]$ ./opatch lsinv | grep "OPatch version" OPatch version : 11.1.0.12.9
As a next step. We roll out the new JDK, which is 1.7.0_151-b15. This is also a step which requires no downtime, because we simply untar the new JDK in the appropriate directory. We are not changing the symbolic link at this point.
[dbafmw@dbidg01 20170718]$ cp jdk-7u151-linux-x64.tar.gz /u01/app/oracle/product/Middleware/11.1.2.3/ [dbafmw@dbidg01 20170718]$ cd /u01/app/oracle/product/Middleware/11.1.2.3/ [dbafmw@dbidg01 11.1.2.3]$ tar -xzvf jdk-7u151-linux-x64.tar.gz jdk1.7.0_151/ jdk1.7.0_151/LICENSE jdk1.7.0_151/release jdk1.7.0_151/jre/ jdk1.7.0_151/jre/LICENSE jdk1.7.0_151/jre/Welcome.html jdk1.7.0_151/jre/plugin/ jdk1.7.0_151/jre/plugin/desktop/ jdk1.7.0_151/jre/plugin/desktop/sun_java.png jdk1.7.0_151/jre/plugin/desktop/sun_java.desktop jdk1.7.0_151/jre/lib/ jdk1.7.0_151/jre/lib/fontconfig.SuSE.10.properties.src jdk1.7.0_151/jre/lib/alt-rt.jar jdk1.7.0_151/jre/lib/meta-index jdk1.7.0_151/jre/lib/net.properties jdk1.7.0_151/jre/lib/oblique-fonts/ jdk1.7.0_151/jre/lib/oblique-fonts/LucidaSansDemiOblique.ttf jdk1.7.0_151/jre/lib/oblique-fonts/fonts.dir jdk1.7.0_151/jre/lib/oblique-fonts/LucidaTypewriterOblique.ttf ... jdk1.7.0_151/db/bin/sysinfo.bat jdk1.7.0_151/db/bin/setNetworkClientCP jdk1.7.0_151/db/bin/derby_common.bat jdk1.7.0_151/db/bin/startNetworkServer.bat jdk1.7.0_151/db/bin/startNetworkServer jdk1.7.0_151/db/bin/setNetworkServerCP.bat jdk1.7.0_151/db/bin/stopNetworkServer jdk1.7.0_151/db/README-JDK.html jdk1.7.0_151/db/NOTICE jdk1.7.0_151/README.html jdk1.7.0_151/THIRDPARTYLICENSEREADME.txt
The symbolic link is still pointing to the old JDK version, which is 1.7.0_141.
[dbafmw@dbidg01 11.1.2.3]$ rm jdk-7u151-linux-x64.tar.gz rm: remove write-protected regular file ‘jdk-7u151-linux-x64.tar.gz’? y [dbafmw@dbidg01 11.1.2.3]$ ls -l | grep jdk lrwxrwxrwx 1 dbafmw oinstall 12 May 29 14:10 jdk -> jdk1.7.0_141 drwxr-x--- 8 dbafmw oinstall 4096 Dec 12 2016 jdk1.7.0_131 drwxr-xr-x 8 dbafmw oinstall 4096 Mar 14 06:10 jdk1.7.0_141 drwxr-xr-x 8 dbafmw oinstall 4096 Jul 12 11:31 jdk1.7.0_151
Now the downtime for the WebLogic and OUD server starts. From a downtime perspective, the WebLogic server is not so important, because it is only used for ODSM. If the WebLogic server is down, it means only that you can’t use the graphical ODSM tool anymore. It is much more important to get the OUD up and running again.
[dbafmw@dbidg01 ~]$ ./stopOUD.sh Stopping Weblogic Server... ... Stopping Derby Server... Stopping Server... ...
After the WebLogic and OUD server is stopped, it is time to switch the symbolic link for the JDK to the new version.
[dbafmw@dbidg01 11.1.2.3]$ rm jdk [dbafmw@dbidg01 11.1.2.3]$ ln -s jdk1.7.0_151 jdk [dbafmw@dbidg01 11.1.2.3]$ ls -l | grep jdk lrwxrwxrwx 1 dbafmw oinstall 12 Jul 19 09:02 jdk -> jdk1.7.0_151 drwxr-x--- 8 dbafmw oinstall 4096 Dec 12 2016 jdk1.7.0_131 drwxr-xr-x 8 dbafmw oinstall 4096 Mar 14 06:10 jdk1.7.0_141 drwxr-xr-x 8 dbafmw oinstall 4096 Jul 12 11:31 jdk1.7.0_151
Now we can patch the OUD to 11.1.2.3.170718.
[dbafmw@dbidg01 OPatch]$ cdh
[dbafmw@dbidg01 11.1.2.3]$ cd Oracle_OUD1/OPatch/
[dbafmw@dbidg01 OPatch]$ ./opatch apply /u01/app/oracle/product/Middleware/stage/PSU/20170718/25840309
Oracle Interim Patch Installer version 11.1.0.12.9
Copyright (c) 2017, Oracle Corporation. All rights reserved.
Oracle Home : /u01/app/oracle/product/Middleware/11.1.2.3/Oracle_OUD1
Central Inventory : /u01/app/oraInventory
from : /u01/app/oracle/product/Middleware/11.1.2.3/Oracle_OUD1/oraInst.loc
OPatch version : 11.1.0.12.9
OUI version : 11.1.0.11.0
Log file location : /u01/app/oracle/product/Middleware/11.1.2.3/Oracle_OUD1/cfgtoollogs/opatch/25840309_Jul_19_2017_09_05_01/apply2017-07-19_09-05-01AM_1.log
OPatch detects the Middleware Home as "/u01/app/oracle/product/Middleware/11.1.2.3"
Applying interim patch '25840309' to OH '/u01/app/oracle/product/Middleware/11.1.2.3/Oracle_OUD1'
Verifying environment and performing prerequisite checks...
Conflicts/Supersets for each patch are:
Patch : 25840309
Bug Superset of 25383162
Super set bugs are:
21110317, 24731779, 19596240, 20987332, 20786014, 19271756, 21024218, 24333856, 21184039, 17409345, 22555819, 21569267, 19987242, 17416498, 23703560, 22927723, 21835208, 21278352, 22308304, 24409239, 21620706, 21225831, 21634829, 23317872, 21126991, 20771322, 21189204, 19670854, 23327572, 22843404, 21097296, 23066020, 21298039, 21967348, 20688926, 20813995, 17488044, 18311877, 21249082, 20198154, 20415424, 23032811, 21207635, 21415093, 21831011, 21575993, 21882589, 17568241, 22611713, 20363721, 21498205, 21301617, 24577814, 19991366, 21098103, 21932111, 24390289, 21282258, 19636259, 24399724, 22916463, 20235234, 20630323, 20113230, 20554639, 24481116, 24681490, 21924319, 20979061, 20469049, 24490948, 22017920, 23195988, 22564810, 24565597, 22950438, 20881625, 21169776, 20736946, 21032490, 22641166, 21644986, 21337744, 23262289, 21509636, 21183856, 22369027, 22075202, 21464932, 20692543, 20805136, 21754188, 21889432, 20924952, 21683538, 20554436, 24372668, 20881496, 21527426, 23703466, 21605154, 24310538, 21959508, 22689164, 20875947, 22119339, 20778847, 23207713, 21503767, 21310463, 20554511, 21387378, 21075558, 22180844, 21665762, 20987758, 24405001, 20529805, 20470402, 20381973, 21881962, 20830152, 23090053, 17406282, 21461976, 20989144, 20180870, 20312191, 21111836, 22732230, 21387387, 19504096, 24544860, 18312432
Interim patch 25840309 is a superset of the patch(es) [ 25383162 ] in the Oracle Home
OPatch will roll back the subset patches and apply the given patch.
All checks passed.
Provide your email address to be informed of security issues, install and
initiate Oracle Configuration Manager. Easier for you if you use your My
Oracle Support Email address/User Name.
Visit http://www.oracle.com/support/policies.html for details.
Email address/User Name:
You have not provided an email address for notification of security issues.
Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: Y
Backing up files...
Rolling back interim patch '25383162' from OH '/u01/app/oracle/product/Middleware/11.1.2.3/Oracle_OUD1'
Patching component oracle.idm.oud, 11.1.2.3.0...
RollbackSession removing interim patch '25383162' from inventory
OPatch back to application of the patch '25840309' after auto-rollback.
Patching component oracle.idm.oud, 11.1.2.3.0...
Verifying the update...
Patch 25840309 successfully applied
Log file location: /u01/app/oracle/product/Middleware/11.1.2.3/Oracle_OUD1/cfgtoollogs/opatch/25840309_Jul_19_2017_09_05_01/apply2017-07-19_09-05-01AM_1.log
OPatch succeeded.
[dbafmw@dbidg01 OPatch]$
[dbafmw@dbidg01 OPatch]$ ./opatch lsinv
Oracle Interim Patch Installer version 11.1.0.12.9
Copyright (c) 2017, Oracle Corporation. All rights reserved.
Oracle Home : /u01/app/oracle/product/Middleware/11.1.2.3/Oracle_OUD1
Central Inventory : /u01/app/oraInventory
from : /u01/app/oracle/product/Middleware/11.1.2.3/Oracle_OUD1/oraInst.loc
OPatch version : 11.1.0.12.9
OUI version : 11.1.0.11.0
Log file location : /u01/app/oracle/product/Middleware/11.1.2.3/Oracle_OUD1/cfgtoollogs/opatch/opatch2017-07-19_09-05-45AM_1.log
OPatch detects the Middleware Home as "/u01/app/oracle/product/Middleware/11.1.2.3"
Lsinventory Output file location : /u01/app/oracle/product/Middleware/11.1.2.3/Oracle_OUD1/cfgtoollogs/opatch/lsinv/lsinventory2017-07-19_09-05-45AM.txt
--------------------------------------------------------------------------------
Installed Top-level Products (1):
Oracle Unified Directory 11.1.2.3.0
There are 1 products installed in this Oracle Home.
Interim patches (2) :
Patch 25840309 : applied on Wed Jul 19 09:05:10 CEST 2017
Unique Patch ID: 21265541
Created on 14 Jul 2017, 00:55:06 hrs PST8PDT
Bugs fixed:
21310463, 21503767, 23531972, 25396981, 25201795, 25411721, 20554639
24372668, 20415424, 17406282, 22180844, 24409239, 17416498, 20987332
21298039, 21075558, 21575993, 24577814, 21110317, 22927723, 20235234
22308304, 17409345, 21301617, 21846477, 20989144, 22641166, 21098103
24390289, 24753992, 22564810, 21415093, 20554511, 20469049, 22732230
21569267, 23607708, 21889432, 22963292, 21882589, 25022506, 25326997
19596240, 21387378, 21278352, 21683538, 21387387, 18325609, 20786014
20692543, 21665762, 21184039, 20778847, 20805136, 21932111, 20881625
20736946, 22555819, 25176210, 19504096, 23703466, 23032811, 20771322
20830152, 24677562, 21461976, 22017920, 19670854, 23090053, 21527426
20813995, 21169776, 20113230, 20875947, 21282258, 24490948, 24731779
18312432, 20529805, 21097296, 25173266, 24681490, 21464932, 21881962
21498205, 21605154, 24793179, 21249082, 21509636, 22611713, 23703560
22369027, 21126991, 20470402, 22075202, 21207635, 24902148, 24763428
25451319, 25167070, 21111836, 22950438, 19991366, 20312191, 19987242
20198154, 25166847, 21967348, 23066020, 24544860, 21032490, 24481116
24701083, 25951621, 24405001, 21835208, 23327572, 24399724, 20979061
20630323, 21959508, 19636259, 17568241, 25437857, 23319809, 19947883
20987758, 20881496, 20924952, 20554436, 21754188, 20381973, 21183856
24333856, 21620706, 24310538, 22916463, 21634829, 21337744, 22843404
21924319, 20180870, 17488044, 20688926, 21811333, 21189204, 21644986
23195988, 24565597, 22119339, 22689164, 23207713, 25686699, 25166924
21831011, 18311877, 19271756, 21024218, 21680391, 21225831, 20979247
20363721, 23262289, 23317872
Patch 21197325 : applied on Mon Mar 27 12:25:39 CEST 2017
Unique Patch ID: 18996262
Created on 3 Jul 2015, 07:28:59 hrs PST8PDT
Bugs fixed:
21197325
--------------------------------------------------------------------------------
OPatch succeeded.
After the patching has successfully done, we can start the OUD instance.
[dbafmw@dbidg01 ~]$ /u01/app/oracle/product/Middleware/11.1.2.3/asinst_1/OUD/bin/start-ds [19/Jul/2017:09:06:48 +0200] category=CORE severity=INFORMATION msgID=132 msg=The Directory Server is beginning the configuration bootstrapping process [19/Jul/2017:09:06:48 +0200] category=CORE severity=NOTICE msgID=458886 msg=Oracle Unified Directory 11.1.2.3.170718 (build 20170621135318Z, R1706210545) starting up [19/Jul/2017:09:06:52 +0200] category=RUNTIME_INFORMATION severity=NOTICE msgID=20381717 msg=Installation Directory: /u01/app/oracle/product/Middleware/11.1.2.3/Oracle_OUD1 [19/Jul/2017:09:06:52 +0200] category=RUNTIME_INFORMATION severity=NOTICE msgID=20381719 msg=Instance Directory: /u01/app/oracle/product/Middleware/11.1.2.3/asinst_1/OUD ... ... [19/Jul/2017:09:06:57 +0200] category=CORE severity=INFORMATION msgID=720 msg=No worker queue thread pool size specified: sizing automatically to use 24 threads [19/Jul/2017:09:06:57 +0200] category=PROTOCOL severity=NOTICE msgID=2556180 msg=Started listening for new connections on Administration Connector 0.0.0.0 port 4444 [19/Jul/2017:09:06:57 +0200] category=PROTOCOL severity=NOTICE msgID=2556180 msg=Started listening for new connections on LDAP Connection Handler 192.168.56.201 port 1389 [19/Jul/2017:09:06:57 +0200] category=PROTOCOL severity=NOTICE msgID=2556180 msg=Started listening for new connections on LDAP Connection Handler 192.168.56.201 port 1636 [19/Jul/2017:09:06:57 +0200] category=CORE severity=NOTICE msgID=458887 msg=The Directory Server has started successfully [19/Jul/2017:09:06:57 +0200] category=CORE severity=NOTICE msgID=458891 msg=The Directory Server has sent an alert notification generated by class org.opends.server.core.DirectoryServer (alert type org.opends.server.DirectoryServerStarted, alert ID 458887): The Directory Server has started successfully [dbafmw@dbidg01 ~]$
Ok. OUD is up and running again and ready to use. The whole downtime for patching it, in case you don’t have a multi master replication, was only a few minutes. That is very fast from my point of view.
Now let’s take care of the WebLogic Server. First of all, we need to unzip the new WebLogic patch into the bsu/cache_dir directory, or any other directory.
[dbafmw@dbidg01 ~]$ echo $JAVA_HOME /u01/app/oracle/product/Middleware/11.1.2.3/jdk [dbafmw@dbidg01 ~]$ /u01/app/oracle/product/Middleware/11.1.2.3/jdk/bin/java -version java version "1.7.0_151" Java(TM) SE Runtime Environment (build 1.7.0_151-b15) Java HotSpot(TM) 64-Bit Server VM (build 24.151-b15, mixed mode) [dbafmw@dbidg01 20170718]$ cp p25869650_1036_Generic.zip /u01/app/oracle/product/Middleware/11.1.2.3/utils/bsu/cache_dir/ [dbafmw@dbidg01 20170718]$ cd /u01/app/oracle/product/Middleware/11.1.2.3/utils/bsu/cache_dir/ [dbafmw@dbidg01 cache_dir]$ unzip p25869650_1036_Generic.zip Archive: p25869650_1036_Generic.zip inflating: README.txt inflating: B25A.jar inflating: patch-catalog_25250.xml [dbafmw@dbidg01 cache_dir]$
Patching the WebLogic server is a little different then patching the OUD. It does not come with the OPatch utility, but for and foremost it is not cumulative. That means, you can’t apply patch B over patch A. You have to remove patch A beforehand. In case you have not removed it beforehand, you will end up with conflict like shown below.
[dbafmw@dbidg01 cache_dir]$ . /u01/app/oracle/product/Middleware/11.1.2.3/wlserver_10.3/server/bin/setWLSEnv.sh [dbafmw@dbidg01 cache_dir]$ cd /u01/app/oracle/product/Middleware/11.1.2.3/utils/bsu/ [dbafmw@dbidg01 bsu]$ ./bsu.sh -install -patch_download_dir=/u01/app/oracle/product/Middleware/11.1.2.3/utils/bsu/cache_dir -patchlist=XIDD -prod_dir=/u01/app/oracle/product/Middleware/11.1.2.3/wlserver_10.3 Result: Failure Unable to locate patch archive: XIDD [dbafmw@dbidg01 bsu]$ ./bsu.sh -install -patch_download_dir=/u01/app/oracle/product/Middleware/11.1.2.3/utils/bsu/cache_dir -patchlist=B25A -prod_dir=/u01/app/oracle/product/Middleware/11.1.2.3/wlserver_10.3 Checking for conflicts..... Conflict(s) detected - resolve conflict condition and execute patch installation again Conflict condition details follow: Patch B25A is mutually exclusive and cannot coexist with patch(es): XIDD [dbafmw@dbidg01 bsu]$ ./bsu.sh -remove -patchlist=XIDD -prod_dir=/u01/app/oracle/product/Middleware/11.1.2.3/wlserver_10.3 Checking for conflicts.... No conflict(s) detected Removing Patch ID: XIDD.. Result: Success [dbafmw@dbidg01 bsu]$ [dbafmw@dbidg01 bsu]$ ./bsu.sh -install -patch_download_dir=/u01/app/oracle/product/Middleware/11.1.2.3/utils/bsu/cache_dir -patchlist=B25A -prod_dir=/u01/app/oracle/product/Middleware/11.1.2.3/wlserver_10.3 Checking for conflicts..... No conflict(s) detected Installing Patch ID: B25A.. Result: Success [dbafmw@dbidg01 bsu]$ [dbafmw@dbidg01 ~]$ nohup /u01/app/oracle/product/Middleware/11.1.2.3/user_projects/domains/base_domain/bin/startWebLogic.sh & [1] 20001 [dbafmw@dbidg01 ~]$ nohup: ignoring input and appending output to ‘nohup.out’
Ready. We have now patched the WebLogic server to 10.3.6.0.170718. In case you have issues with the bsu utility, you might want to use the -log option for debugging: bsu.sh -log=bsu_debug.trc. Or you take a quick look at the BSU Command line interface reference guide. http://docs.oracle.com/cd/E14759_01/doc.32/e14143/commands.htm
Ok. OUD and WebLogic is fully patched and running. But what about the ODSM? Do I have to redeploy it? No, you don’t. The odsm.ear is redeployed automatically. The odsm.ear file is shipped along with every OUD bundle patch (bppatchnumber/files/odsm/odsm.ear). A new odsm.ear file is included with Patch 11.1.2.3.170718 at the following location:
[dbafmw@dbidg01 odsm]$ pwd /u01/app/oracle/product/Middleware/11.1.2.3/Oracle_OUD1/odsm [dbafmw@dbidg01 odsm]$ ls -l total 36660 -rw-r----- 1 dbafmw oinstall 37535804 Jul 14 09:55 odsm.ear
When you restart the Server for the first time after applying the patch, it will automatically redeploy the new odsm.ear file. Therefore, you might experience a slower restart of the WebLogic server. If you want, you cat take a look at the logs related to odsm.ear file deployment.
[dbafmw@dbidg01 logs]$ pwd /u01/app/oracle/product/Middleware/11.1.2.3/user_projects/domains/base_domain/servers/AdminServer/logs [dbafmw@dbidg01 logs]$ cat AdminServer.log | grep odsm.ear ####<Jul 19, 2017 10:23:22 AM CEST> <Info> <J2EE> <dbidg01> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1500452602820> <BEA-160166> <References were found in deployment plan for module 'odsm.ear' with uri, 'META-INF/application.xml'. The plan was merged.> ####<Jul 19, 2017 10:23:22 AM CEST> <Info> <Munger> <dbidg01> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1500452602830> <BEA-2156202> <References were found in deployment plan for module 'odsm.ear' with uri, 'META-INF/application.xml'. The plan was merged.> ####<Jul 19, 2017 10:23:22 AM CEST> <Info> <J2EE> <dbidg01> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1500452602830> <BEA-160166> <References were found in deployment plan for module 'odsm.ear' with uri, 'META-INF/weblogic-application.xml'. The plan was merged.> ####<Jul 19, 2017 10:23:22 AM CEST> <Info> <Munger> <dbidg01> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1500452602832> <BEA-2156202> <References were found in deployment plan for module 'odsm.ear' with uri, 'META-INF/weblogic-application.xml'. The plan was merged.> ####<Jul 19, 2017 10:23:22 AM CEST> <Info> <Munger> <dbidg01> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1500452602833> <BEA-2156202> <References were found in deployment plan for module 'odsm.ear' with uri, 'META-INF/weblogic-application.xml'. The plan was merged.> ####<Jul 19, 2017 10:23:22 AM CEST> <Info> <Munger> <dbidg01> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1500452602863> <BEA-2156202> <References were found in deployment plan for module 'odsm.ear' with uri, 'META-INF/application.xml'. The plan was merged.> ####<Jul 19, 2017 10:23:22 AM CEST> <Info> <Munger> <dbidg01> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1500452602863> <BEA-2156202> <References were found in deployment plan for module 'odsm.ear' with uri, 'META-INF/weblogic-application.xml'. The plan was merged.> ####<Jul 19, 2017 10:23:22 AM CEST> <Info> <Munger> <dbidg01> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1500452602863> <BEA-2156202> <References were found in deployment plan for module 'odsm.ear' with uri, 'META-INF/application.xml'. The plan was merged.> ####<Jul 19, 2017 10:23:22 AM CEST> <Info> <Munger> <dbidg01> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1500452602863> <BEA-2156202> <References were found in deployment plan for module 'odsm.ear' with uri, 'META-INF/weblogic-application.xml'. The plan was merged.>
If for any reason the odsm.ear file deployment fails during the first restart of the Server, then you manually need to redeploy the file. That’s it. We have now successfully upgraded JDK, OPatch, OUD, and WebLogic/ODSM to the latest release.
At the end, repeat the whole procedure on the second OUD, if you have one.
Conclusion
Patching an OUD requires a few steps, however, it can be done very fast if it is prepared well. And in case you have multi master replication with a load balancer vip on top, you can do it with no downtime at all.
![Thumbnail [60x60]](https://www.dbi-services.com/blog/wp-content/uploads/2022/12/oracle-square.png)
![Thumbnail [90x90]](https://www.dbi-services.com/blog/wp-content/uploads/2022/08/DWE_web-min-scaled.jpg)