EBS upgrade 12.2.0-12.2.5 Missing Bugfix: 21967332- 25305405

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

EBS upgrade 12.2.0-12.2.5 Missing Bugfix: 21967332- 25305405

Daniel
Dear Erman,  

I am upgrade APPs DB node and Apps Node.


I couldn't solve the following error.



Checking Mapping XML file for 12.1.0.2

  Missing Bugfix: 21967332  ->  Patch 21967332
  Missing Bugfix: 25305405  ->  Patch 25305405

./checkDBpatch.sh

 +===============================================================+
 |    Copyright (c) 2005, 2018 Oracle and/or its affiliates.     |
 |                     All rights reserved.                      |
 |             Oracle E-Business Suite Release 12.2              |
 |          Database EBS Technology Codelevel Checker            |
 +===============================================================+

Using context file from currently set database environment:
/u01/home/oracle/WIS/12.1.0/appsutil/TESTT_racnode1.xml


Starting Database EBS Technology Codelevel Checker, Version 120.69
Sat Oct 20 13:54:39 +03 2018
Log file for this session : /u01/home/oracle/WIS/12.1.0/appsutil/etcc/log/checkDBpatch_19895.log

Identifying database release.
Database release set to 12.1.0.2.

Connecting to database.

+-----------------------------------------------------------------------------+
[WARNING] DB-ETCC: Could not connect to database, so unable to check:
  - Whether database is in READ-WRITE mode.
  - Existence of table needed to store DB-ETCC results.
  - Enablement of database In-Memory option.
    If this feature is enabled, additional fixes need to be verified.

Resolve the database connectivity issue, and then rerun DB-ETCC.
+-----------------------------------------------------------------------------+

Bugfix file ./db/onprem/txk_R1220_DB_base_bugs.xml : 120.0.12020000.43
This file will be used for identifying missing bugfixes.

Mapping file ./db/onprem/txk_R1220_DB_mappings.xml : 120.0.12020000.18
This file will be used for mapping bugfixes to patches.


[WARNING] DB-ETCC: Bugfix XML file (./db/onprem/txk_R1220_DB_base_bugs.xml) is more than 30 days old.
 Check if a newer version is available in patch 17537119.

Checking Bugfix XML file for 12.1.0.2

Obtained list of bugfixes to be applied and the list to be rolled back.
Now checking Database ORACLE_HOME.

The opatch utility is version 12.2.0.1.14.
DB-ETCC is compatible with this opatch version.

Found patch records in the inventory.

Checking Mapping XML file for 12.1.0.2

  Missing Bugfix: 21967332  ->  Patch 21967332
  Missing Bugfix: 25305405  ->  Patch 25305405

Generating Patch Recommendation Summary.

===============================================================================
PATCH RECOMMENDATION SUMMARY
===============================================================================
The default patch recommendations to install these missing bugfixes are:
-------------------------------------------------------------------------------
Oracle Database Release 12.1.0.2 - InMemory status unknown (No PSU applied)
-------------------------------------------------------------------------------
  Patch 21967332
    - Filename: p21967332_121020_Linux-x86-64.zip

  Patch 25305405
    - Filename: p25305405_121020_Linux-x86-64.zip


+-----------------------------------------------------------------------------+
[WARNING] DB-ETCC: Could not connect to database, so unable to check:
  - Whether database is in READ-WRITE mode.
  - Existence of table needed to store DB-ETCC results.
  - Enablement of database In-Memory option.
    If this feature is enabled, additional fixes need to be verified.

Resolve the database connectivity issue, and then rerun DB-ETCC.
+-----------------------------------------------------------------------------+

+-----------------------------------------------------------------------------+
A consolidated zip file with the required patches for Database release
12.1.0.2.0 is available on My Oracle Support via:

  Patch 28128412 [12.1.0.2.0 version]
    - EBS RELEASE 12.2 CONSOLIDATED DATABASE FIXES FOR JUL 2018

Note: This zip does not include any database bundle patches or PSUs.
+-----------------------------------------------------------------------------+

See Doc ID 1594274.1 for any special instructions for these patches.
Note: Footnotes in Doc ID 1594274.1 also apply to corresponding overlay patches.

[WARNING] Database not available. DB-ETCC results cannot be stored.

Finished checking fixes for Oracle Database: Sat Oct 20 13:54:54 +03 2018

Log file for this session: /u01/home/oracle/WIS/12.1.0/appsutil/etcc/log/checkDBpatch_19895.log


----------------------------

-bash-4.1$ cd 21967332/
-bash-4.1$ opatch apply
Oracle Interim Patch Installer version 12.2.0.1.14
Copyright (c) 2018, Oracle Corporation.  All rights reserved.


Oracle Home       : /u01/home/oracle/WIS/12.1.0
Central Inventory : /u01/home/oracle/WIS/oraInventory
   from           : /u01/home/oracle/WIS/12.1.0/oraInst.loc
OPatch version    : 12.2.0.1.14
OUI version       : 12.1.0.2.0
Log file location : /u01/home/oracle/WIS/12.1.0/cfgtoollogs/opatch/opatch2018-10-20_14-00-54PM_1.log

Verifying environment and performing prerequisite checks...

Conflicts/Supersets for each patch are:

Patch : 21967332

        Conflict with 18893947
        Conflict details:
        /u01/home/oracle/WIS/12.1.0/lib/libgeneric12.a:qcdo.o


Following patches have conflicts: [   18893947   21967332 ]
Use the MOS Patch Conflict Checker "https://support.oracle.com/epmos/faces/PatchConflictCheck" to resolve.
See MOS documents 1941934.1 and 1299688.1 for additional information and resolution methods.

UtilSession failed: Inter-conflict checking failed in apply incoming patches
Log file location: /u01/home/oracle/WIS/12.1.0/cfgtoollogs/opatch/opatch2018-10-20_14-00-54PM_1.log

OPatch failed with error code 73


Can you Help. Br.
Reply | Threaded
Open this post in threaded view
|

Re: EBS upgrade 12.2.0-12.2.5 Missing Bugfix: 21967332- 25305405

ErmanArslansOracleBlog
Administrator
You have a conflict.. Fotuneatly, it is already addressed ..

If a conflict is reported with Patch 18893947, roll back the conflicting patch before applying Patch 21967332.

So, it is safe to rollback 18893947.

Run the rollback command, opatch rollback -id 18893947 and retry applying 21967332.