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 APRIL 2014 DATABASE PATCH SET UPDATE 11.2.0.3.10 - Patch 18031683
1) Download Patch 18031683 relevant for your environment
2) Verify if the patch already applied or not
$opatch lsinventory | grep 18031683
3) Check opatch version to ensure it is 11.2.0.3.0 or higher
$opatch version
Note: If Opatch version is not up to date then download patch 6880880 from Metalink
4) Check for patch conflicts
Copy patch onto target host $ORACLE_HOME/patches, unzip the patch.
opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir ./18031683
Note: If there's no conflict please proceed with applying the patch. In case of conflicts, contact product support.
5) Check for invalid objects in Database
select owner,object_name,object_type from dba_objects where status='INVALID';
6) Shutdown the services and apply the patch (make sure backup is taken before applying patch).
$ opatch apply
Do you want to proceed? [y|n]
y
User Responded with: Y
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
Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
Is the local system ready for patching? [y|n]
y
User Responded with: Y
Backing up files...
OPatch succeeded.
7) Check if patch is successfully applied or not.
$ opatch lsinventory | grep 18031683
8) Post patch, load modified SQL files into the Database:
Start the database
cd $ORACLE_HOME/rdbms/admin
SQL> @catbundle.sql psu apply
PL/SQL procedure successfully completed.
-------------------
SQL> COMMIT;
Commit complete.
9) Check log files in $ORACLE_HOME/cfgtoollogs/catbundle for any errors
10)Query registry$history to ensure PSU was applied.
SQL> select * from registry$history;
11) Run utlrp.sql for any invalid objects reported.
