Here is a note that is created by my collegue Hulya Yılmaz, while patching a 10.3.6 Weblogic instance with the WLS Patch Set Update 13.
The master note used in this upgrade was:
Master Note on WebLogic Server Patch Set Updates (PSUs)(Doc ID 1470197.1)
The Middleware and Weblogic Home were:
MW_HOME=/data/oracledev/Middleware
WL_HOME=/data/oracledev/Middleware/wlserver_10.3
The steps :
1. Stop all WebLogic servers
2. unzip p21984589_1036_Generic.zip to {MW_HOME}/utils/bsu/cache_dir
3. . $WL_HOME/server/bin/setWLSEnv.sh
4. Navigate to the {MW_HOME}/utils/bsu directory
5. Execute bsu.sh -install -patch_download_dir={MW_HOME}/utils/bsu/cache_dir -patchlist={PATCH_ID} -prod_dir={MW_HOME}/{WL_HOME}
bash-3.2$ bsu.sh -install -patch_download_dir=/data/oracledev/Middleware/utils/bsu/cache_dir -patchlist=S8C2 - prod_dir=/data/oracledev/Middleware/wlserver_10.3 -log=/tmp/bsu.log
Checking for conflicts.......
No conflict(s) detected Installing Patch ID: S8C2..
Result: Success
Note: if bsu will hand, then we increase the heapsize by following the note below.
WebLogic Server: Smart Update Throwing OutOfMemoryError (Doc ID 1154089.1)
6. Verify psu:
bash-3.2$ java weblogic.version
WebLogic Server 10.3.6.0.13 PSU Patch for BUG21984589 TUE NOV 26 15:54:42 IST 2015 WebLogic Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050
7. Restart all WebLogic Servers
The master note used in this upgrade was:
Master Note on WebLogic Server Patch Set Updates (PSUs)(Doc ID 1470197.1)
The Middleware and Weblogic Home were:
MW_HOME=/data/oracledev/Middleware
WL_HOME=/data/oracledev/Middleware/wlserver_10.3
The steps :
1. Stop all WebLogic servers
2. unzip p21984589_1036_Generic.zip to {MW_HOME}/utils/bsu/cache_dir
3. . $WL_HOME/server/bin/setWLSEnv.sh
4. Navigate to the {MW_HOME}/utils/bsu directory
5. Execute bsu.sh -install -patch_download_dir={MW_HOME}/utils/bsu/cache_dir -patchlist={PATCH_ID} -prod_dir={MW_HOME}/{WL_HOME}
bash-3.2$ bsu.sh -install -patch_download_dir=/data/oracledev/Middleware/utils/bsu/cache_dir -patchlist=S8C2 - prod_dir=/data/oracledev/Middleware/wlserver_10.3 -log=/tmp/bsu.log
Checking for conflicts.......
No conflict(s) detected Installing Patch ID: S8C2..
Result: Success
Note: if bsu will hand, then we increase the heapsize by following the note below.
WebLogic Server: Smart Update Throwing OutOfMemoryError (Doc ID 1154089.1)
6. Verify psu:
bash-3.2$ java weblogic.version
WebLogic Server 10.3.6.0.13 PSU Patch for BUG21984589 TUE NOV 26 15:54:42 IST 2015 WebLogic Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050
7. Restart all WebLogic Servers
An older patch "p22248372_1036012_Generic.zip" says to set
ReplyDeleteMEM_ARGS="-Xms512m -Xmx1024m".
We ran into "Exception in thread "Main Thread" java.lang.OutOfMemoryError" when patching an old test server which never had 22248372 installed.
Thanks for pointing this out, Jerry.
ReplyDeleteIt is a known Issue for weblogic patches, documented in other documents like Oracle E-Business Suite 12.2 Patching Technology Components Guide (Doc ID 1355068.1), as well.
Can you please let me know the standard procedure to apply the Weblogic patches.
ReplyDeleteScenario 1:
1. Source RUN file-system
2.Apply Weblogic patches on RUN file-system
3. adop fs_clone
Scenario 2:
1. Source patch file system.
2. Apply Weblogic patches on Patch-filesystem Weblogic home
3. ADOP start the cycle until cutover and then FS_CLONE
Scenario 3:
1. Start ADOP Prepare phase
2. Apply Weblogic patches on Patch file-system
3. After applying CUTOVER and then FS_CLONE
Regards,
Saif
Hi,
ReplyDeleteShould you not initiate an ADOP cycle before applying the WLS PSU?
Thanks.