Oracle WebLogic Server Applying 12.2.1.0.0 Patch 22505388: WLS PATCH SET UPDATE 12.2.1.0.160419

Oracle WebLogic Server Applying 12.2.1.0.0 Patch 22505388: WLS PATCH SET UPDATE 12.2.1.0.160419

- Download & unzip Patch 22505388 (p22505388_122100_Generic.zip)

$ unzip -d PATCH_TOP p22505388_122100_Generic.zip

Apply Patch

- Set ORACLE_HOME environment to WLS Home

- Stop MT services (Admin Server and all Managed servers)

$ cd PATCH_DIR/22505388

- Apply Patch

$ opatch apply

- Start MT services (Admin Server and all Managed servers)

Patch rollback

- If any issues after applying the patch and rollback is required, follow below steps:

- Stop MT services (Admin Server and all Managed servers)

$ cd PATCH_DIR/22505388

- Run opatch rollback

$ opatch rollback -id  22505388


- Restart MT services (Admin Server and all Managed servers)

Related Posts:

WLS 12.1.2.0.0 - Applying Patch 22505331: WLS PATCH SET UPDATE 12.1.2.0.160419

FMW 12.1.3.0.0 - Applying Patch 22505404: WLS PATCH SET UPDATE 12.1.3.0.160419

WLS 10.3.6 Applying Patch 22505423: SU Patch [DEM4]: WLS PATCH SET UPDATE 10.3.6.0.160419

FMW 12.1.3.0.0 - Applying Patch 22505404: WLS PATCH SET UPDATE 12.1.3.0.160419

FMW 12.1.3.0.0 - Applying Patch 22505404: WLS PATCH SET UPDATE 12.1.3.0.160419

- Download and unzip Patch 22505404 (p22505404_121300_Generic.zip)

$ unzip -d PATCH_TOP p22505404_121300_Generic.zip

- Set ORACLE_HOME environment to WLS Home

Apply Patch

- Stop MT services (Admin Server and all Managed servers)

$ cd PATCH_TOP/22505404

- Apply Patch

$ opatch apply

- Start MT services (Admin Server and all Managed servers)

Patch rollback

- If any issues after applying the patch and rollback is required, follow below steps:

- Stop MT services (Admin Server and all Managed servers)

$ cd PATCH_TOP/22505404

- Run opatch rollback

$ opatch rollback -id  22505404

- Restart MT services (Admin Server and all Managed servers)

Related Posts:

WLS 12.1.2.0.0 - Applying Patch 22505331: WLS PATCH SET UPDATE 12.1.2.0.160419

WLS 12.2.1.0.0 - Applying Patch 22505388: WLS PATCH SET UPDATE 12.2.1.0.160419

WLS 10.3.6 Applying Patch 22505423: SU Patch [DEM4]: WLS PATCH SET UPDATE 10.3.6.0.160419

WLS 12.1.1.0 - Applying Patch 16219305: SU Patch [HVMW]: NONSTRESS:CLASSCASTEXCEPTION DURING SERVICE MIGRATION IN UNICAST CLUSTERING

WLS 12.1.1.0 - Applying Patch 16219305: SU Patch [HVMW]: NONSTRESS:CLASSCASTEXCEPTION DURING SERVICE MIGRATION IN UNICAST CLUSTERING

- Download Patch 16219305 (p16219305_12110_Generic.zip)

- SU Patch [BYGU] for WLS 10.3.6 and SU Patch [5YKP] for WLS 10.3.5

Applying Patch 16219305

- Stop MT services

- Remove any existing conflicting patches already applied

- Unzip the patch 

$ unzip p16219305_12110_Generic.zip

- $ cd PATCH_TOP/16219305

- Copy contents of the patch zip file except README to $MW_HOME/utils/bsu/cache_dir/

- $ cd $MW_HOME/utils/bsu/cache_dir/

- Take backup of existing patch-catalog.xml and rename the one copied from patch zip file to patch-catalog.xml

- Apply the patch using Smart Update Utility

$ ./bsu.sh -prod_dir=$MW_HOME/WL_Home -patch_download_dir=$MW_HOME/utils/bsu/cache_dir -patchlist=HVMW  -verbose -install

- Start MT services

- Verify WebLogic Server PSU

$ . $WL_HOME/server/bin/setWLSEnv.sh 

$ java weblogic.version

Related Posts:

<BEA-000802> ExecuteRequest failed java.lang.ClassCastException: weblogic.jms.frontend.FEConnectionFactoryImpl

Oracle 12.1.0.2.0 - Applying Patch 21948354: DATABASE PATCH SET UPDATE 12.1.0.2.160119 (INCLUDES CPUJAN2016)

Oracle 12.1.0.2.0 - Applying Patch 21948354: DATABASE PATCH SET UPDATE 12.1.0.2.160119 (INCLUDES CPUJAN2016)

- Download Patch 21948354 (p21948354_121020_Linux-x86-64.zip)

- Before applying this patch, ensure Oracle home has 12.1.0.2.0 Database installed

- Ensure OPatch utility version is 12.1.0.1.7 or later to apply this patch

- If applying the PSU to environment with Grid Infrastructure home, ensure Grid Infrastructure PSU 12.1.0.2.160119 Patch 22191349 is applied to the Grid Infrastructure home and Database home.

- Set the environment variables

Please note below steps for Standalone DB only (For RAC, Single / Multitenant (CDB/PDB), patching steps vary slightly. Refer to patch readme for more details)

Applying Patch 21948354

- Unzip the patch

$ unzip p21948354_121020_Linux-x86-64.zip

$ cd 21948354

- Run conflict checks

$ opatch prereq CheckConflictAgainstOHWithDetail -ph ./

- Shutdown the services

- Run opatch apply

$ opatch apply

- Start the services

Post-Patching Steps

- Load Modified SQL Files into Database

$ cd $ORACLE_HOME/OPatch

$ ./datapatch -verbose

- Upgrade RMAN Catalog (if using Oracle Recovery Manager)

$ rman catalog username/password@alias
RMAN> UPGRADE CATALOG;


Patch Rollback Steps

If any issues after applying patch and rollback is required,

- Shutdown all services

- Run opatch rollback

$ opatch rollback -id 21948354

- Start all Services

- Run datapatch utility

$ cd $ORACLE_HOME/OPatch

$ ./datapatch -verbose

- Upgrade RMAN Catalog (if using Oracle Recovery Manager)

$ rman catalog username/password@alias
RMAN> UPGRADE CATALOG;



Related Posts

Oracle 12.1.0.2.0 - Applying Patch 18201352: ORA-7445 [QERTBSTART()+3105] CRASHES QUERY WITH DISTINCT AND PJE TRANSFORMATION

Oracle 12.1.0.2.0 - Applying Patch 20228093: MATERIALIZED VIEW DEFERRED MODE ORA-00918: COLUMN AMBIGUOUSLY DEFINED

Oracle 12.1.0.2.0 - Applying Patch 22139226: OJVM PATCH SET UPDATE 12.1.0.2.160119

libserver11.a:/qksbg.o Patch 12942119 conflicts when applying Oracle 11.2.0.3.0 Patch 20760997: DATABASE PATCH SET UPDATE 11.2.0.3.15 (INCLUDES CPUJUL2015)

libserver11.a:/qksbg.o Patch 12942119 conflicts when applying Oracle 11.2.0.3.0 Patch 20760997: DATABASE PATCH SET UPDATE 11.2.0.3.15 (INCLUDES CPUJUL2015)

When applying Patch 20760997, there is conflict with existing patch 12942119. However, patch 12942119 can be rollbacked and once the cpu patch 20760997 is applied then apply the overlay patch 12942119 version 11.2.0.3.8 

(Reference: Database Patch Set Update Overlay Patches Required for Use with PSUs and Oracle E-Business Suite Doc ID 1147107.1)


- Download Patch 20760997 (p20760997_112030_Linux-x86-64.zip)


Patch 20760997 Conflict Checks


$ cd $DB_HOME/patches/20760997

$ opatch prereq CheckConflictAgainstOHWithDetail -ph ./

Oracle Interim Patch Installer version 11.2.0.3.0

Copyright (c) 2012, Oracle Corporation.  All rights reserved.

PREREQ session


Oracle Home       : $DB_HOME/product/112
Central Inventory : $DB_HOME/oraInventory

   from           : $DB_HOME/product/112/oraInst.loc
OPatch version    : 11.2.0.3.0

OUI version       : 11.2.0.3.0


Invoking prereq "checkconflictagainstohwithdetail"


ZOP-40: The patch(es) has conflicts with other patches installed in the Oracle Home (or) among 
themselves.

Prereq "checkConflictAgainstOHWithDetail" failed.


Summary of Conflict Analysis:

There are no patches that can be applied now.


Following patches have conflicts. Please contact Oracle Support and get the merged patch of the 
patches :
20760997, 12942119


Following patches will be rolled back from Oracle Home on application of the patches in the given 
list :
12942119

Conflicts/Supersets for each patch are:

Patch : 20760997


        Conflict with 12942119
        Conflict details:

        $DB_HOME/product/112/lib/libserver11.a:/qksbg.o

OPatch succeeded.

Patch 12942119 Version 11.2.0.3.8 Conflict Checks

$ pwd

$DB_HOME/patches/12942119
$ opatch prereq CheckConflictAgainstOHWithDetail -ph ./

Oracle Interim Patch Installer version 11.2.0.3.0

Copyright (c) 2012, Oracle Corporation.  All rights reserved.

PREREQ session


Oracle Home       : $DB_HOME/product/112
Central Inventory : $DB_HOME/oraInventory

   from           : $DB_HOME/product/112/oraInst.loc
OPatch version    : 11.2.0.3.0

OUI version       : 11.2.0.3.0

Log file location : 
$DB_HOME/product/112/cfgtoollogs/opatch/opatch2015-12-19_02-51-27AM_1.log


Invoking prereq "checkconflictagainstohwithdetail"


Prereq "checkConflictAgainstOHWithDetail" passed.

OPatch succeeded.
$


Apply Patch 20760997

- Shutdown DB & MT services (Cold backup recommended)

- Login to DB Node

PATH=$ORACLE_HOME/OPatch:$PATH export PATH

cd $DB_HOME/patches/20760997

 opatch apply


Note while applying the patch there will be conflict with patch 12942119. Rollback patch 12942119 and proceed with applying CPU patch 20760997. 

Once completed apply overlay patch 12942119 verison 11.2.0.3.8. 

- Apply overlay patch  12942119 verison 11.2.0.3.8

cd $DB_HOME/patches/12942119


opatch apply

Post Patch Steps
- Start DB and Listener services

- Load modified SQL files into the database following below steps.

For a RAC environment, perform these steps on only one node.


For each database instance running on the Oracle home being patched, connect to the database 

using SQL*Plus. Connect as SYSDBA and run the catbundle.sql script as follows:


    cd $ORACLE_HOME/rdbms/admin
    sqlplus /nolog
    SQL> CONNECT / AS SYSDBA


    SQL> STARTUP
    SQL> @catbundle.sql psu apply
    SQL> QUIT

The catbundle.sql execution is reflected in the dba_registry_history view by a row associated with bundle series PSU.

If OJVM PSU was applied for a previous PSU patch, you may see invalid Java classes after execution of the catbundle.sql script in the previous step. If this is the case, run utlrp.sql to  re-validate these Java classes.

    cd $ORACLE_HOME/rdbms/admin
    sqlplus /nolog


    SQL> CONNECT / AS SYSDBA
    SQL> @utlrp.sql

Check the following log files in $ORACLE_HOME/cfgtoollogs/catbundle or $ORACLE_BASE/cfgtoollogs/catbundle for any errors:

catbundle_PSU_<database SID>_APPLY_<TIMESTAMP>.log
catbundle_PSU_<database SID>_GENERATE_<TIMESTAMP>.log


- Start MT services


Related Posts:

Checking for Patch conflicts - 21352635: DATABASE PATCH SET UPDATE 11.2.0.4.8 (INCLUDES CPUOCT2015)

Applying 21352635: DATABASE PATCH SET UPDATE 11.2.0.4.8 (INCLUDES CPUOCT2015)

Rollback Patch 21352635: DATABASE PATCH SET UPDATE 11.2.0.4.8 (INCLUDES CPUOCT2015)

Applying Patch 20181997: SU Patch [YUIS]: WLS PATCH SET UPDATE 10.3.6.0.11

Applying Patch 20181997: SU Patch [YUIS]: WLS PATCH SET UPDATE 10.3.6.0.11


Download and copy the patch p20181997_1036_Generic.zip to staging area.

Copy the patch files to /sid/fmw/product/112/utils/bsu/cache_dir

cp $STAGE_DIR/patches/YUIS.jar $MW_HOME/product/112/utils/bsu/cache_dir/

cp $STAGE_DIR/patches/patch-catalog_22580.xml $MW_HOME/product/112/utils/bsu/cache_dir/

cd $MW_HOME/product/112/utils/bsu

Backup existing patch-catalog.xml

cp patch-catalog.xml patch-catalog_orig.xml

mv patch-catalog_22580.xml patch-catalog.xml

(Note: Remove any existing patches that may conflict with the new patch.
Run ./bsu.sh -remove -patchlist={PATCH_ID} -prod_dir={MW_HOME}/{WL_HOME})


Applying the patch 

- Stop the services

./bsu.sh -install -patch_download_dir=$MW_HOME/product/112/utils/bsu/cache_dir/ -patchlist=YUIS -prod_dir=$MW_HOME/product/112/wlserver_10.3
Checking for conflicts...

No conflict(s) detected

Installing Patch ID: YUIS..
Result: Success

- Restart services

- Verify the patch applied

./bsu.sh -view -status=applied -prod_dir=$MW_HOME/product/111/wlserver_10.3

bash-4.1$ . $MW_HOME/product/111/wlserver_10.3/server/bin/setWLSEnv.sh

bash-4.1$ java weblogic.version

WebLogic Server 10.3.6.0.11 PSU Patch for BUG20181997 TUE NOV 12 15:54:42 IST 2015

Uninstalling the patch

 - Stop MT services
 - Navigate to the {MW_HOME}/utils/bsu directory.
 - Run ./bsu.sh -remove -patchlist={PATCH_ID} -prod_dir={MW_HOME}/{WL_HOME}
 - Start MT services 

Related Posts:

Applying Patch 21364493: WLS PATCH SET UPDATE 12.1.2.0.7

Applying Patch 20844228: WLS PATCH SET UPDATE 12.1.2.0.6

Oracle WebLogic Server WLS 10.3.6.0.13 - Applying Patch 21984589: SU Patch [S8C2]: WLS PATCH SET UPDATE 10.3.6.0.13

Applying Patch 20780171: SU Patch [EJUW]: WLS PATCH SET UPDATE 10.3.6.0.12

Applying Patch 19637463: SU Patch [12UV]: Oracle WebLogic Server (WLS) PATCH SET UPDATE 10.3.6.0.10

Applying Patch 19182814: SU Patch [FSR2]: Weblogic Server (WLS) PATCH SET UPDATE 10.3.6.0.9

Applying Patch 18040640 - SU Patch [T5F1]: Weblogic Server (WLS) PATCH SET UPDATE 10.3.6.0.8 on OBIEE client

Applying Patch 20780171: SU Patch [EJUW]: WLS PATCH SET UPDATE 10.3.6.0.12

Applying Patch 20780171: SU Patch [EJUW]: WLS PATCH SET UPDATE 10.3.6.0.12

- Download the patch 20780171 and copy it to the staging area of the server

To install the patch, follow below steps:

- unzip p20780171_1036_Generic.zip to {MW_HOME}/utils/bsu/cache_dir or staging area (ensure appopriate permissions are set & take backup of cache_dir)

- {MW_HOME}/utils/bsu

./bsu.sh -install -patch_download_dir={MW_HOME}/utils/bsu/cache_dir -patchlist={PATCH_ID} -prod_dir={MW_HOME}/{WL_HOME}

- If any patch conflicts with existing PSU patch, uninstall existing patch and re-attempt patching

- Restart MT services after applying patch

- Verify the latest version of WebLogic

  $ . $WL_HOME/server/bin/setWLSEnv.sh
  $ java weblogic.version

You should see version similar to below

WebLogic Server 10.3.6.0.12 PSU Patch for BUG20780171

To unistall the patch, follow below steps:

 - Stop MT services
 - Navigate to the {MW_HOME}/utils/bsu directory.
 - Run ./bsu.sh -remove -patchlist={PATCH_ID} -prod_dir={MW_HOME}/{WL_HOME}
 - Start MT services 


 Related posts:

Applying Patch 21364493: WLS PATCH SET UPDATE 12.1.2.0.7

Applying Patch 20844228: WLS PATCH SET UPDATE 12.1.2.0.6

Oracle WebLogic Server WLS 10.3.6.0.13 - Applying Patch 21984589: SU Patch [S8C2]: WLS PATCH SET UPDATE 10.3.6.0.13

WLS 10.3.6.0.12 - Applying Patch 21325021: SU Patch [JGWA] :10.3.6.0.12 Overlay: MERGE REQUEST ON TOP OF WLS PSU 10.3.6.0.12 FOR BUGS 18057437 18438079 20062321

Applying Patch 20181997: SU Patch [YUIS]: WLS PATCH SET UPDATE 10.3.6.0.11

Applying Patch 19637463: SU Patch [12UV]: Oracle WebLogic Server (WLS) PATCH SET UPDATE 10.3.6.0.10

Applying Patch 19182814: SU Patch [FSR2]: Weblogic Server (WLS) PATCH SET UPDATE 10.3.6.0.9

Applying Patch 18040640 - SU Patch [T5F1]: Weblogic Server (WLS) PATCH SET UPDATE 10.3.6.0.8 on OBIEE client