Anuj Singh Oracle DBA: Oracle 12c Patch 38729239 - Database Jan 2026 Release Update 12.2.0.1.260120

Monday, 9 March 2026

Oracle 12c Patch 38729239 - Database Jan 2026 Release Update 12.2.0.1.260120

Patch 38729239 - Database Jan 2026 Release Update 12.2.0.1.260120

===============================================================================

export PATH=$ORACLE_HOME/OPatch:$PATH

[oracle@wcp12cr2 38729239]$ opatch version
OPatch Version: 12.2.0.1.6


cd $ORACLE_HOME
mv OPatch OPatch_old

===============
                                              oracle_home                  software location 
[oracle@wcp12cr2 software]$ unzip -qqd /u01/app/oracle/product/12.1.0/db_2 /oracle/software/p6880880_122010_Linux-x86-64.zip

[oracle@wcp12cr2 db_2]$ unzip -qqd /u01/app/oracle/product/12.1.0/db_2 /oracle/software/p6880880_122010_Linux-x86-64.zip


[oracle@wcp12cr2 db_2]$ opatch version
OPatch Version: 12.2.0.1.49   must check with readme file !!!!

OPatch succeeded.
 
 
 
 ===============


 cd /oracle/software/38729239

[oracle@wcp12cr2 38729239]$ opatch prereq CheckConflictAgainstOHWithDetail -ph ./

Oracle Interim Patch Installer version 12.2.0.1.49
Copyright (c) 2026, Oracle Corporation.  All rights reserved.

PREREQ session

Oracle Home       : /u01/app/oracle/product/12.1.0/db_2
Central Inventory : /oracle/oraInventory
   from           : /u01/app/oracle/product/12.1.0/db_2/oraInst.loc
OPatch version    : 12.2.0.1.49
OUI version       : 12.2.0.1.4
Log file location : /u01/app/oracle/product/12.1.0/db_2/cfgtoollogs/opatch/opatch2026-03-09_00-14-08AM_1.log

Invoking prereq "checkconflictagainstohwithdetail"

Prereq "checkConflictAgainstOHWithDetail" passed.

OPatch succeeded.

==================


drwxr-xr-x. 5 oracle oinstall     4096 Mar  8 23:37 38729239
[oracle@wcp12cr2 software]$ cd 38729239
[oracle@wcp12cr2 38729239]$ opatch apply
Oracle Interim Patch Installer version 12.2.0.1.49
Copyright (c) 2026, Oracle Corporation.  All rights reserved.


Oracle Home       : /u01/app/oracle/product/12.1.0/db_2
Central Inventory : /oracle/oraInventory
   from           : /u01/app/oracle/product/12.1.0/db_2/oraInst.loc
OPatch version    : 12.2.0.1.49
OUI version       : 12.2.0.1.4
Log file location : /u01/app/oracle/product/12.1.0/db_2/cfgtoollogs/opatch/opatch2026-03-09_00-30-59AM_1.log

Verifying environment and performing prerequisite checks...
OPatch continues with these patches:   38729239

Do you want to proceed? [y|n]
y
User Responded with: Y
yAll checks passed.

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = '/u01/app/oracle/product/12.1.0/db_2')


Is the local system ready for patching? [y|n]
y
Could not recognize input. Please re-enter.
y
User Responded with: Y
y
Backing up files...
Applying interim patch '38729239' to OH '/u01/app/oracle/product/12.1.0/db_2'
ApplySession: Optional component(s) [ oracle.swd.oui, 12.2.0.1.0 ] , [ oracle.rdbms.tg4tera, 12.2.0.1.0 ] , [ oracle.network.gsm, 12.2.0.1.0 ] , [ oracle.rdbms.tg4db2, 12.2.0.1.0 ] , [ oracle.rdbms.tg4ifmx, 12.2.0.1.0 ] , [ oracle.oid.client, 12.2.0.1.0 ] , [ oracle.sdo.companion, 12.2.0.1.0 ] , [ oracle.rdbms.tg4msql, 12.2.0.1.0 ] , [ oracle.ons.cclient, 12.2.0.1.0 ] , [ oracle.rdbms.drdaas, 12.2.0.1.0 ] , [ oracle.ons.eons.bwcompat, 12.2.0.1.0 ] , [ oracle.rdbms.tg4sybs, 12.2.0.1.0 ] , [ oracle.network.cman, 12.2.0.1.0 ] , [ oracle.ons.daemon, 12.2.0.1.0 ]  not present in the Oracle Home or a higher version is found.

Patching component oracle.network.rsf, 12.2.0.1.0...

Patching component oracle.rdbms.rsf, 12.2.0.1.0...

Patching component oracle.rdbms.util, 12.2.0.1.0...

Patching component oracle.ctx, 12.2.0.1.0...

Patching component oracle.dbdev, 12.2.0.1.0...

Patching component oracle.dbtoolslistener, 12.2.0.1.0...

Patching component oracle.has.common.cvu, 12.2.0.1.0...

Patching component oracle.ldap.owm, 12.2.0.1.0...

Patching component oracle.ldap.rsf, 12.2.0.1.0...

Patching component oracle.marvel, 12.2.0.1.0...

Patching component oracle.nlsrtl.rsf, 12.2.0.1.0...

Patching component oracle.oracore.rsf, 12.2.0.1.0...

Patching component oracle.oraolap, 12.2.0.1.0...

Patching component oracle.ordim.client, 12.2.0.1.0...

Patching component oracle.perlint, 5.22.0.0.0...

Patching component oracle.rdbms, 12.2.0.1.0...

Patching component oracle.rdbms.crs, 12.2.0.1.0...

Patching component oracle.rdbms.dbscripts, 12.2.0.1.0...

Patching component oracle.rdbms.deconfig, 12.2.0.1.0...

Patching component oracle.rdbms.rsf.ic, 12.2.0.1.0...

Patching component oracle.sdo, 12.2.0.1.0...

Patching component oracle.sdo.locator, 12.2.0.1.0...

Patching component oracle.sdo.locator.jrf, 12.2.0.1.0...

Patching component oracle.swd.oui.core, 12.2.0.1.4...

Patching component oracle.sysman.ccr, 12.1.2.0.0...

Patching component oracle.sysman.ccr.client, 10.3.2.1.0...

Patching component oracle.tfa, 12.2.0.1.0...

Patching component oracle.ldap.client, 12.2.0.1.0...

Patching component oracle.ons, 12.2.0.1.0...

Patching component oracle.ldap.rsf.ic, 12.2.0.1.0...

Patching component oracle.rdbms.rman, 12.2.0.1.0...

Patching component oracle.assistants.deconfig, 12.2.0.1.0...

Patching component oracle.xdk.rsf, 12.2.0.1.0...

Patching component oracle.sqlplus.ic, 12.2.0.1.0...

Patching component oracle.duma, 12.2.0.1.0...

Patching component oracle.duma, 12.2.0.1.0...

Patching component oracle.xdk, 12.2.0.1.0...

Patching component oracle.assistants.server, 12.2.0.1.0...

Patching component oracle.sqlplus, 12.2.0.1.0...

Patching component oracle.rdbms.dv, 12.2.0.1.0...

Patching component oracle.ctx.rsf, 12.2.0.1.0...

Patching component oracle.precomp.rsf, 12.2.0.1.0...

Patching component oracle.assistants.acf, 12.2.0.1.0...

Patching component oracle.xdk.xquery, 12.2.0.1.0...

Patching component oracle.rdbms.hs_common, 12.2.0.1.0...

Patching component oracle.install.deinstalltool, 12.2.0.1.0...

Patching component oracle.xdk.parser.java, 12.2.0.1.0...

Patching component oracle.rdbms.oci, 12.2.0.1.0...

Patching component oracle.rdbms.hsodbc, 12.2.0.1.0...

Patching component oracle.network.listener, 12.2.0.1.0...

Patching component oracle.rdbms.install.plugins, 12.2.0.1.0...

Patching component oracle.ovm, 12.2.0.1.0...

Patching component oracle.ons.ic, 12.2.0.1.0...

Patching component oracle.rdbms.lbac, 12.2.0.1.0...

Patching component oracle.blaslapack, 12.2.0.1.0...

Patching component oracle.rdbms.install.common, 12.2.0.1.0...

Patching component oracle.precomp.lang, 12.2.0.1.0...

Patching component oracle.precomp.common, 12.2.0.1.0...

Patching component oracle.jdk, 1.8.0.91.0...

OPatch found the word "error" in the stderr of the make command.
Please look at this stderr. You can re-run this make command.
Stderr output:
chmod: changing permissions of `/u01/app/oracle/product/12.1.0/db_2/bin/extjobO': Operation not permitted
make: [iextjob] Error 1 (ignored)


Patch 38729239 successfully applied.
OPatch Session completed with warnings.
Log file location: /u01/app/oracle/product/12.1.0/db_2/cfgtoollogs/opatch/opatch2026-03-09_00-30-59AM_1.log

OPatch completed with warnings.
[oracle@wcp12cr2 38729239]$ y
-bash: y: command not found



[oracle@wcp12cr2 38729239]$ opatch lsinventory | grep -E "(^Patch.*applied)|(^Sub-patch)"
Patch  38729239     : applied on Mon Mar 09 00:42:23 PDT 2026




Please check below files !!!!!!!!!!!!

[oracle@wcp12cr2 OPatch]$ ls -l $ORACLE_HOME/sqlpatch
total 276
drwxr-xr-x. 3 oracle oinstall   4096 Mar  9 00:26 38729239
drwxr-xr-x. 7 oracle oinstall   4096 Mar  8 10:11 lib
-rwxr-x---. 1 oracle oinstall   2732 Dec 16 21:35 sqlpatch
-rwxr-x---. 1 oracle oinstall    999 Dec 16 21:35 sqlpatch.bat
-rw-r--r--. 1 oracle oinstall   3516 Aug 16  2016 sqlpatch_bootstrap_driver.sql
-rw-r--r--. 1 oracle oinstall  14454 Dec 16 21:35 sqlpatch_bootstrap.sql
-rwxr-xr-x. 1 oracle oinstall   4803 Dec 16 21:35 sqlpatch.pl
-rwxr-xr-x. 1 oracle oinstall 237260 Dec 16 21:35 sqlpatch.pm
[oracle@wcp12cr2 OPatch]$




[oracle@wcp12cr2 OPatch]$ ls -ltr $ORACLE_HOME/sqlpatch/38729239/28365030
total 3148
-rw-r--r--. 1 oracle oinstall   17199 Dec 16 21:46 38729239.xml
-rw-r--r--. 1 oracle oinstall   34523 Dec 16 21:46 38729239_rollback.sql
-rw-r--r--. 1 oracle oinstall   35939 Dec 16 21:46 38729239_apply.sql
drwxr-xr-x. 4 oracle oinstall    4096 Mar  9 00:26 rollback_files
-rw-r--r--. 1 oracle oinstall 3122440 Mar  9 00:52 38729239.zip
[oracle@wcp12cr2 OPatch]$


[oracle@wcp12cr2 OPatch]$ ls -ltr $ORACLE_HOME/sqlpatch/38729239/28365030/rollback_files
total 8
drwxr-xr-x. 4 oracle oinstall 4096 Mar  9 00:26 rdbms
drwxr-xr-x. 3 oracle oinstall 4096 Mar  9 00:26 ctx
[oracle@wcp12cr2 OPatch]$



======================================================




SQL> startup ;
ORACLE instance started.

Total System Global Area 3707764736 bytes
Fixed Size                  8799320 bytes
Variable Size             855641000 bytes
Database Buffers         2835349504 bytes
Redo Buffers                7974912 bytes
Database mounted.
Database opened.

SQL> alter pluggable database all open; 
 show pdbs

    CON_ID CON_NAME                       OPEN MODE  RESTRICTED
---------- ------------------------------ ---------- ----------
         2 PDB$SEED                       READ ONLY  NO
         3 VIHAAN                         READ WRITE NO   <<<< check !!!
SQL>

<----- altered.="" database="" pluggable="" sql="">[oracle@wcp12cr2 OPatch]$ ./datapatch -verbose
SQL Patching tool version 12.2.0.1.0 Production on Mon Mar  9 00:49:11 2026
Copyright (c) 2012, 2025, Oracle.  All rights reserved.

Log file for this invocation: /u01/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_6311_2026_03_09_00_49_12/sqlpatch_                                                                     invocation.log

Connecting to database...OK
Note:  Datapatch will only apply or rollback SQL fixes for PDBs
       that are in an open state, no patches will be applied to closed PDBs.
       Please refer to Note: Datapatch: Database 12c Post Patch SQL Automation
       (Doc ID 1585822.1)
Bootstrapping registry and package to current versions...done
Determining current state...done

Current state of SQL patches:
Bundle series DBRU:
  ID 260120 in the binary registry and not installed in any PDB

Adding patches to installation queue and performing prereq checks...
Installation queue:
  For the following PDBs: CDB$ROOT PDB$SEED VIHAAN
    Nothing to roll back
    The following patches will be applied:
      38729239 (DATABASE JAN 2026 RELEASE UPDATE 12.2.0.1.260120)

Installing patches...
Patch installation complete.  Total patches installed: 3

Validating logfiles...
Patch 38729239 apply (pdb CDB$ROOT): SUCCESS
  logfile: /u01/app/oracle/cfgtoollogs/sqlpatch/38729239/28365030/38729239_apply_ORCLDB_CDBROOT_2026Mar09_00_5                                                                     2_07.log (no errors)
Patch 38729239 apply (pdb PDB$SEED): SUCCESS
  logfile: /u01/app/oracle/cfgtoollogs/sqlpatch/38729239/28365030/38729239_apply_ORCLDB_PDBSEED_2026Mar09_01_0                                                                     6_31.log (no errors)
Patch 38729239 apply (pdb VIHAAN): WITH ERRORS
  logfile: /u01/app/oracle/cfgtoollogs/sqlpatch/38729239/28365030/38729239_apply_ORCLDB_VIHAAN_2026Mar09_01_06                                                                     _30.log (errors)
    Error at line 132481: ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired

Please refer to MOS Note 1609718.1 and/or the invocation log
/u01/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_6311_2026_03_09_00_49_12/sqlpatch_invocation.log
for information on how to resolve the above errors.

SQL Patching tool complete on Mon Mar  9 01:24:49 2026



again ---


[oracle@wcp12cr2 OPatch]$ ./datapatch -verbose
SQL Patching tool version 12.2.0.1.0 Production on Mon Mar  9 01:34:52 2026
Copyright (c) 2012, 2025, Oracle.  All rights reserved.

Log file for this invocation: /u01/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_7665_2026_03_09_01_34_52/sqlpatch_invocation.log

Connecting to database...OK
Note:  Datapatch will only apply or rollback SQL fixes for PDBs
       that are in an open state, no patches will be applied to closed PDBs.
       Please refer to Note: Datapatch: Database 12c Post Patch SQL Automation
       (Doc ID 1585822.1)
Bootstrapping registry and package to current versions...done
Determining current state...done

Current state of SQL patches:
Bundle series DBRU:
  ID 260120 in the binary registry and ID 260120 in PDB CDB$ROOT, ID 260120 in PDB PDB$SEED, ID 260120 with errors in PDB VIHAAN

Adding patches to installation queue and performing prereq checks...
Installation queue:
  For the following PDBs: CDB$ROOT PDB$SEED
    Nothing to roll back
    Nothing to apply
  For the following PDBs: VIHAAN
    Nothing to roll back
    The following patches will be applied:
      38729239 (DATABASE JAN 2026 RELEASE UPDATE 12.2.0.1.260120)

Installing patches...
Patch installation complete.  Total patches installed: 1

Validating logfiles...
Patch 38729239 apply (pdb VIHAAN): SUCCESS
  logfile: /u01/app/oracle/cfgtoollogs/sqlpatch/38729239/28365030/38729239_apply_ORCLDB_VIHAAN_2026Mar09_01_36_45.log (no errors)
SQL Patching tool complete on Mon Mar  9 01:45:27 2026
[oracle@wcp12cr2 OPatch]$ sqlme

SQL*Plus: Release 12.2.0.1.0 Production on Mon Mar 9 01:46:15 2026

Copyright (c) 1982, 2016, Oracle.  All rights reserved.





set linesize 300
col PDB_NAME for a20
SELECT c.name AS pdb_name,
       r.patch_id,
       r.action,
       r.status,
       r.action_time
FROM   cdb_registry_sqlpatch r
JOIN   v$containers c
ON     r.con_id = c.con_id
ORDER  BY r.action_time;



PDB_NAME               PATCH_ID ACTION          STATUS                    ACTION_TIME
-------------------- ---------- --------------- ------------------------- ---------------------------------------------------------------------------
CDB$ROOT               38729239 APPLY           SUCCESS                   09-MAR-26 01.24.23.154077 AM
VIHAAN                 38729239 APPLY           WITH ERRORS               09-MAR-26 01.24.37.313038 AM
VIHAAN                 38729239 APPLY           SUCCESS                   09-MAR-26 01.45.21.046180 AM




col ACTION_TIME for a30
col name for a15
 SELECT c.name,
       r.patch_id,
       r.status,
       r.action_time
FROM   cdb_registry_sqlpatch r,
       v$containers c
WHERE  r.con_id = c.con_id
AND    r.patch_id = 38729239
ORDER BY r.con_id, r.action_time; 



NAME              PATCH_ID STATUS                    ACTION_TIME
--------------- ---------- ------------------------- ------------------------------
CDB$ROOT          38729239 SUCCESS                   09-MAR-26 01.24.23.154077 AM
VIHAAN            38729239 WITH ERRORS               09-MAR-26 01.24.37.313038 AM
VIHAAN            38729239 SUCCESS                   09-MAR-26 01.45.21.046180 AM






SET LINESIZE 500  PAGESIZE 1000  SERVEROUT ON  LONG 2000000
COLUMN action_time 	FORMAT A12
COLUMN action 		FORMAT A10
COLUMN bundle_series 	FORMAT A4
COLUMN comments 	FORMAT A30
COLUMN description 	FORMAT A70
COLUMN namespace 	FORMAT A20
COLUMN status 		FORMAT A10
COLUMN version 		FORMAT A10


SELECT TO_CHAR(action_time, 'YYYY-MM-DD') AS action_time,
 action,
 status,
 description,
 version,
 patch_id,
 bundle_series
 FROM   sys.dba_registry_sqlpatch
 ORDER by action_time;



SET LINESIZE 500  PAGESIZE 1000  SERVEROUT ON  LONG 2000000
COLUMN action_time 	FORMAT A12
COLUMN action 		FORMAT A15
COLUMN bundle_series 	FORMAT A4
COLUMN comments 	FORMAT A30
COLUMN description 	FORMAT A70
COLUMN namespace 	FORMAT A20
COLUMN status 		FORMAT A17
COLUMN version 		FORMAT A10


SELECT TO_CHAR(action_time, 'YYYY-MM-DD') AS action_time,
 action,
 status,
 description,
 version,
 patch_id,
 bundle_series
 FROM   sys.cdb_registry_sqlpatch
 ORDER by action_time;


2026-03-09   APPLY           WITH ERRORS       DATABASE JAN 2026 RELEASE UPDATE 12.2.0.1.260120                       12.2.0.1     38729239 DBRU
2026-03-09   APPLY           SUCCESS           DATABASE JAN 2026 RELEASE UPDATE 12.2.0.1.260120                       12.2.0.1     38729239 DBRU
2026-03-09   APPLY           SUCCESS           DATABASE JAN 2026 RELEASE UPDATE 12.2.0.1.260120                       12.2.0.1     38729239 DBRU

3 rows selected.

SQL>



SET LINESIZE 500  PAGESIZE 1000  SERVEROUT ON  LONG 2000000
COLUMN action_time 	FORMAT A18
COLUMN action 		FORMAT A15
COLUMN bundle_series 	FORMAT A4
COLUMN comments 	FORMAT A30
COLUMN description 	FORMAT A70
COLUMN namespace 	FORMAT A20
COLUMN status 		FORMAT A17
COLUMN version 		FORMAT A10


SELECT TO_CHAR(action_time, 'dd-mm-yyyy hh24:mi') AS action_time,
con_id,
 action,
 status,
 description,
 version,
 patch_id,
 bundle_series
 FROM   sys.cdb_registry_sqlpatch
 ORDER by action_time;

ACTION_TIME            CON_ID ACTION          STATUS            DESCRIPTION                                                            VERSION      PATCH_ID BUND
------------------ ---------- --------------- ----------------- ---------------------------------------------------------------------- ---------- ---------- ----
09-03-2026 01:24            3 APPLY           WITH ERRORS       DATABASE JAN 2026 RELEASE UPDATE 12.2.0.1.260120                       12.2.0.1     38729239 DBRU
09-03-2026 01:24            1 APPLY           SUCCESS           DATABASE JAN 2026 RELEASE UPDATE 12.2.0.1.260120                       12.2.0.1     38729239 DBRU
09-03-2026 01:45            3 APPLY           SUCCESS           DATABASE JAN 2026 RELEASE UPDATE 12.2.0.1.260120                       12.2.0.1     38729239 DBRU





col COMP_NAME for a35
SELECT comp_name, status, version
FROM dba_registry

COMP_NAME                           STATUS            VERSION
----------------------------------- ----------------- --------------------
Oracle Database Catalog Views       VALID             12.2.0.1.0
Oracle Database Packages and Types  VALID             12.2.0.1.0
JServer JAVA Virtual Machine        VALID             12.2.0.1.0
Oracle XDK                          VALID             12.2.0.1.0
Oracle Database Java Packages       VALID             12.2.0.1.0
OLAP Analytic Workspace             VALID             12.2.0.1.0
Oracle Real Application Clusters    OPTION OFF        12.2.0.1.0
Oracle XML Database                 VALID             12.2.0.1.0
Oracle Workspace Manager            VALID             12.2.0.1.0
Oracle Text                         VALID             12.2.0.1.0
Oracle Multimedia                   VALID             12.2.0.1.0
Spatial                             VALID             12.2.0.1.0
Oracle OLAP API                     VALID             12.2.0.1.0
Oracle Label Security               VALID             12.2.0.1.0
Oracle Application Express          VALID             5.0.4.00.12
Oracle Database Vault               VALID             12.2.0.1.0

16 rows selected.






[oracle@wcp12cr2 OPatch]$ $ORACLE_HOME/perl/bin/perl $ORACLE_HOME/rdbms/admin/catcon.pl -n 1 -e -b utlrp -d $ORACLE_HOME/rdbms/admin utlrp.sql
catcon: ALL catcon-related output will be written to [/u01/app/oracle/product/12.1.0/db_2/OPatch/utlrp_catcon_9048.lst]
catcon: See [/u01/app/oracle/product/12.1.0/db_2/OPatch/utlrp*.log] files for output generated by scripts
catcon: See [/u01/app/oracle/product/12.1.0/db_2/OPatch/utlrp_*.lst] files for spool files, if any
catcon.pl: completed successfully



SELECT con_id,owner, object_type, COUNT(*)
FROM cdb_objects
WHERE status='INVALID'
GROUP BY con_id,owner, object_type;


Connected to:
Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production


SQL> SELECT con_id,owner, object_type, COUNT(*)
FROM cdb_objects
WHERE status='INVALID'
GROUP BY con_id,owner, object_type; 

no rows selected



OracleÂ® Database
Patch 38729239 - Database Jan 2026 Release Update 12.2.0.1.260120
This document is accurate at the time of release. For any changes and additional information regarding Database Jan 2026 Release Update 12.2.0.1.260120, see Section 5, "Known Issues".
This document includes the following sections:
Section 1, "Patch Information"
Section 2, "Prerequisites"
Section 3, "Installation"
Section 4, "Deinstallation"
Section 5, "Known Issues"
Section 6, "References"
Section 7, "Bugs Fixed by This Patch"
Section 8, "Documentation Accessibility"
1 Patch Information
Database Jan 2026 Release Update 12.2.0.1.260120 patches are cumulative. That is, the content of all previous Database bundles is included in the latest Database bundle patch.
To install the Database Jan 2026 Release Update 12.2.0.1.260120 patch, the Oracle home must have the 12.2.0.1.0 Database installed.
This patch is Oracle RAC Rolling Installable.
This patch is Database Vault installable. Review My Oracle Support Document KB653211 for details on how to apply this patch to a Database Vault environment.
This patch is Data Guard Standby-First Installable. See My Oracle Support Document KB137118 Oracle Patch Assurance - Data Guard Standby-First Patch Apply for details on how to remove risk and reduce downtime when applying this patch.
This patch includes the JDK fixes released in the prior cycle and will update the JDK in the Oracle home. For the most recent JDK fixes, a separate patch is available and needs to be installed in addition to this patch. Refer to My Oracle Support document KB106822 Primary Note for Database Quarterly Release Updates for the JDK patch number.
For the latest Update with Security Fixes that should be used on Client-Only installations, please refer to the Critical Patch Update (CPU) Program Patch Availability Document (PAD) section on the Oracle Database, for the cycle you are interested in.
This patch contains fixes for Security Vulnerabilities but none of them are published as part of the CPUJan2026 Advisory announcement.
This patch also includes PERL version 5.38.4 from July 2025 onward.
Beginning with Jul2023, this patch deletes the $ORACLE_HOME/apex directory and, therefore, it is recommended to setup a new APEX version outside the database $ORACLE_HOME directory using the latest version. The latest APEX version with all security fixes included can be downloaded from Oracle APEX Downloads.
Beginning with Jul2023, this patch deletes files from the $ORACLE_HOME/sqldeveloper directory not related to Oracle SQL command line (SQLcl) and, therefore it is recommended that, if the Oracle SQL Developer tool is being actively used, a new version be installed outside the database $ORACLE_HOME directory using the latest version. The latest Oracle SQL Developer can be downloaded from Oracle SQL Developer Downloads.
Beginning with 12.2 Oct2023 RU, the UTL_URI.ESCAPE function is now compliant with RFC 3896 and will treat "#" as a reserved character. See My Oracle Support Note PALRT1208 for more details.
2 Prerequisites
It is highly recommended to take a backup of the Oracle_Home binaries and Central Inventory prior to applying patches. For further information, refer to Note KB137807.
This section includes the following section:
Section 2.1, "OPatch Utility"
2.1 OPatch Utility
You must use the OPatch utility version 12.2.0.1.48 or later to apply this patch. Oracle recommends that you use the latest released OPatch 12.2.0.1.xx version for DB 12.2.0.1.0, which is available for download from My Oracle Support patch 6880880 by selecting "OPatch for DB 12.2.0.1.0" from the Select a Release dropdown. It is recommended that you download the OPatch utility and the patch in a shared location to be able to access them from any node in the cluster for the patch application on each node.
When patching the GI home, a shared locaton on Oracle ACFS only needs to be unmounted on the node where the GI home is being patched.
The new OPatch utility should be updated in all of the Oracle RAC database homes and the GI home that are being patched.
For each Oracle RAC database home and the GI home that are being patched, as the home owner, extract the OPatch utility.
For exact instructions to install OPatch, follow the OPatch readme.
A new feature has been added to OPatch to increase performance by deleting inactive patches. See My Oracle Support document KB104015 OPatch 12.2.0.1.37+ Introduces a New Feature to Delete Inactive Patches in the ORACLE_HOME/.patch_storage directory.
For information about OPatch documentation, including any known issues, see My Oracle Support Document KB133615 Primary Note For OPatch.
3 Installation
These instructions are for all Oracle Database installations.
Section 3.1, "Patch Pre-Installation Instructions"
Section 3.2, "Patch Installation Instructions"
Section 3.3, "Patch Post-Installation Instructions"
Section 3.4, "Patch Post-Installation Instructions for Databases Created or Upgraded after Installation of this patch in the Oracle Home"
3.1 Patch Pre-Installation Instructions
Before you install Database Jan 2026 Release Update 12.2.0.1.260120, perform the following actions to check the environment and to detect and resolve any interim patch conflicts.
Section 3.1.1, "Applying Database RU and the Oracle JavaVM Component 12.2.0.1.x Release Update Patch"
Section 3.1.2, "Environments with Grid Infrastructure"
Section 3.1.3, "Environment Checks"
Section 3.1.4, "Interim Patch Conflict Detection and Resolution"
3.1.1 Applying Database 12.2.0.1.x Updates/Revisions with Oracle JavaVM 12.2.0.1.x Updates
The Oracle JavaVM 12.2.0.1.x Release Update is available as a separate patch. That separate patch has some additional requirements if it is to be installed in a "Conditional Rolling Install" fashion, as detailed in My Oracle Support Document KB137197. For customers who want to install both patches together during a single downtime window, follow one of the Patching Options listed in the My Oracle Support Document KB139124 - Oracle Recommended Patches -- Oracle JavaVM Component Database PSU and RU" (OJVM PSU and OVJM RU) Patches.
3.1.2 Environments with Grid Infrastructure
This patch is not to be installed to an environment that has a Grid Infrastructure (GI) home. Please refer to the following My Oracle Support Document KB106822 to determine the appropriate Grid Infrastructure patch to be installed.
3.1.3 Environment Checks
Ensure that the $PATH definition has the following executables: make, ar, ld, and nm.
The location of these executables depends on your operating system. On many operating systems, they are located in /usr/ccs/bin, in which case you can set your PATH definition as follows:
export PATH=$PATH:/usr/ccs/bin
3.1.4 Interim Patch Conflict Detection and Resolution
The fastest and easiest way to determine whether you have interim patches in the Oracle home that conflict with Database Jan 2026 Release Update 12.2.0.1.260120, and to get the necessary conflict resolution patches, is to use the Patch Recommendations and Patch Plans features on the Patches & Updates tab in My Oracle Support.
However, if you are not using My Oracle Support Patch Plans, the My Oracle Support Conflict Checker tool enables you to upload an OPatch inventory and check the patches that you want to apply to your environment for conflicts.
If no conflicts are found, you can download the patches. If conflicts are found, the tool finds an existing resolution to download. If no resolution is found, it will automatically request a resolution, which you can monitor in the Plans and Patch Requests region of the Patches & Updates tab.
For more information, see Knowledge Document KB135057 How to Use the My Oracle Support Conflict Checker Tool for Patches Installed with OPatch.
Or, use the following steps to manually discover conflicts and resolutions:
Determine whether any currently installed interim patches conflict with the patch being installed, 38729239:
unzip p38729239_<version>_<platform>.zip
cd 38729239
opatch prereq CheckConflictAgainstOHWithDetail -ph ./
The report indicates the patches that conflict and the patches that are a superset.
Use My Oracle Support Document KB145571 Database Patch Conflict Resolution to determine, for each conflicting patch, whether a conflict resolution patch is already available, and if you need to request a new conflict resolution patch or if the conflict may be ignored.
When all the interim patches that you have requested are available at My Oracle Support, proceed with Section 3.2, "Patch Installation Instructions".
3.2 Patch Installation Instructions
Follow these steps:
If you are using a Data Guard Physical Standby database, you must install this patch on both the primary database and the physical standby database, as described by My Oracle Support Document KB147888.
If this is a RAC environment, install this patch using the OPatch rolling (no downtime) installation method as this patch is rolling RAC installable. Refer to My Oracle Support Document KB139091 Rolling Patch - OPatch Support for RAC.
If this is not a RAC environment, shut down all instances and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database Administrator's Guide.
Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:
unzip p38729239_<version>_<platform>.zip
cd 38729239
opatch apply
If there are errors, refer to Section 5, "Known Issues".
3.3 Patch Post-Installation Instructions
On Oracle Database server, after installing the patch, perform the following actions. This is not required on Oracle Database client.
Apply conflict resolution patches, as explained in Section 3.3.1.
Load modified SQL files into the database, as explained in Section 3.3.2.
Upgrade Oracle Recovery Manager Catalog, as explained in Section 3.3.3.
Bug fixes that may change an existing optimizer execution plan, as explained in Section 3.3.4.
3.3.1 Apply Conflict Resolution Patches
Apply the patch conflict resolution interim patches that were determined to be needed when you performed the steps in Section 3.1.4, "interim Patch Conflict Detection and Resolution".
3.3.2 Load Modified SQL Files into the Database
The following steps load modified SQL files into the database. For a RAC environment, perform these steps on only one node.
Datapatch is run to complete the post-install SQL deployment for the patch being installed. For further details about Datapatch, including Known/Conflict Issues and workarounds to common problems, see: Datapatch: Database 12c Post Patch SQL Automation (Doc ID KB148594).
For each separate database running on the same shared Oracle home being patched, run the datapatch utility as described in Table 2.
Table 2 Steps to Run the Datapatch Utility for Non-CDB or Non-PDB Database Versus Multitenant (CDB or PDB) Database
Steps Non-CDB or Non-PDB Database Steps Multitenant (CDB/PDB) Oracle Database
1 sqlplus /nolog 1 sqlplus /nolog
2 SQL> Connect / as sysdba 2 SQL> Connect / as sysdba
3 SQL> startup 3 SQL> startup
4 SQL> quit 4 SQL> alter pluggable database all open;^{Foot 1}
5 cd $ORACLE_HOME/OPatch 5 SQL> quit
6 ./datapatch -verbose 6 cd $ORACLE_HOME/OPatch


7 ./datapatch -verbose
^{Footnote 1} It is recommended the Post Install step be run on all pluggable databases; however, the following command (SQL> alter pluggable database PDB_NAME open) could be substituted to only open certain PDBs in the single/multitenant database. Doing so will result in the Post Install step only being run on the CDB and opened PDB's. To update a pluggable database at a later date (skipped or newly plugged in), open the database using the alter pluggable database command mentioned previously and rerun the datapatch utility.
See My Oracle Support Document KB150931  Multitenant Unplug/Plug Best Practices for more information about the procedure for unplugging/plugging with different patch releases (in both directions).
The datapatch utility runs the necessary apply scripts to load the modified SQL files into the database. An entry is added to the dba_registry_sqlpatch view reflecting the patch application. In the dba_registry_sqlpatch view, verify the Status for the APPLY is "SUCCESS".
For any other status, refer to the following My Oracle Support note for additional information and actions: Document KA1374 Troubleshooting Assistant: 12c Datapatch Issues.
Check the following log files in $ORACLE_BASE/cfgtoollogs/sqlpatch/38729239/<unique patch ID> for errors:
38729239_apply_<database SID>_<CDB name>_<timestamp>.log
where database SID is the database SID, CDB name is the name of the multitenant container database, and timestamp is of the form YYYYMMMDD_HH_MM_SS.
For databases that have invalid objects after the execution of datapatch, run utlrp.sql to revalidate those objects.

Example:
cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @utlrp.sql
3.3.3 Upgrade Oracle Recovery Manager Catalog
If you are using the Oracle Recovery Manager, the catalog needs to be upgraded. Enter the following command to upgrade it. The UPGRADE CATALOG command must be entered twice to confirm the upgrade.
$ rman catalog username/password@alias
RMAN> UPGRADE CATALOG;
RMAN> UPGRADE CATALOG;
RMAN> EXIT;
3.3.4 Bug Fixes That May Change an Existing Optimizer Execution Plan
At the successful conclusion of the patching event, none of the database bug fixes that may change an existing optimizer execution plan are delivered with the bug fix disabled by default. The status of any module bug fixes (which cause an execution plan change) that were in an enabled state prior to starting the patching event are preserved, but no new module bug fixes (which cause an execution plan change) are activated automatically.
Details on this, including the commands to explicitly enable such bug fixes are present in My Oracle Support Document KB148297.
3.4 Patch Post-Installation Instructions for Databases Created or Upgraded after Installation of this patch in the Oracle Home
On Oracle Database server, you must execute the steps in Section 3.3.2, "Loading Modified SQL Files into the Database" for any new database. There are no actions required for databases that have been upgraded. This is not required on Oracle Database client.
For more information, see My Oracle Support, 12.1:DBCA(Database Creation) does not execute â€datapatch (Doc ID KB151278).
4 Deinstallation
These instructions apply if you need to deinstall the patch.
Section 4.1, "Patch Deinstallation Instructions for a Non-RAC Environment"
Section 4.2, "Patch Post-Deinstallation Instructions for a Non-RAC Environment"
Section 4.3, "Patch Deinstallation Instructions for Oracle RAC Environment"
Section 4.4, "Patch Post-Deinstallation Instructions for Oracle RAC Environment"
4.1 Patch Deinstallation Instructions for a Non-RAC Environment
Follow these steps:
Shut down all instances and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database Administrator's Guide.
Run the OPatch utility specifying the rollback argument as follows.
opatch rollback -id 38729239
If there are errors, refer to Section 5, "Known Issues".
4.2 Patch Post-Deinstallation Instructions for a Non-RAC Environment
On Oracle Database server, after deinstalling the patch, perform the following actions. This is not required on Oracle Database client.
Rollback SQL changes from the the Database, as explained in Section 4.2.1.
Upgrade Oracle Recovery Manager Catalog, as explained in Section 4.2.2.
4.2.1 Load Modified SQL Files into the Database
Datapatch is run to complete the post-deinstall SQL deployment for the patch being deinstalled. For further details about Datapatch, including Known/Conflict Issues and workarounds to common problems, see: Database 12c Post Patch SQL Automation (Doc ID KB148594).
Follow these steps:
For each separate database running on the same shared Oracle home being patched, run the datapatch utility as described in Table 3. If this is Oracle RAC, run datapatch on only one instance.
Table 3 Steps to Run the Datapatch Utility for Non-CDB or Non-PDB Database Versus Multitenant (CDB/PDB) Database
Steps Non-CDB or Non-PDB Database Steps Multitenant (CDB/PDB) Oracle Database
1 sqlplus /nolog 1 sqlplus /nolog
2 SQL> Connect / as sysdba 2 SQL> Connect / as sysdba
3 SQL> startup 3 SQL> startup
4 SQL> quit 4 SQL> alter pluggable database all open;^{Foot 1}
5 cd $ORACLE_HOME/OPatch 5 SQL> quit
6 ./datapatch -verbose 6 cd $ORACLE_HOME/OPatch


7 ./datapatch -verbose
^{Footnote 1} It is recommended the Post Install step be run on all pluggable databases; however, the following command (SQL> alter pluggable database PDB_NAME open) could be substituted to only open certain PDBs in the single/multitenant database. Doing so will result in the Post Install step only being run on the CDB and opened PDB's. To update a pluggable database at a later date (skipped or newly plugged in), open the database using the alter pluggable database command mentioned previously and rerun the datapatch utility.
See My Oracle Support Document KB150931 Multitenant Unplug/Plug Best Practices for more information about the procedure for unplugging/plugging with different patch releases (in both directions).
The datapatch utility runs the necessary rollback scripts. An entry is added to the dba_registry_sqlpatch view reflecting the patch application. In the dba_registry_sqlpatch view, verify the Status for the ROLLBACK is "SUCCESS".
For any other status, refer to the following My Oracle Support note for additional information and actions: Document KA1374 Troubleshooting Assistant: 12c Datapatch Issues.
Check the following log files in $ORACLE_BASE/cfgtoollogs/sqlpatch/38729239/<unique patch ID> for errors:
38729239_rollback_<database SID>_<CDB name>_<timestamp>.log
where database SID is the database SID, CDB name is the name of the multitenant container database, and timestamp is of the form YYYYMMMDD_HH_MM_SS.
For databases that have invalid objects after the execution of datapatch, run utlrp.sql to revalidate those objects.

Example:
cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @utlrp.sql
4.2.2 Upgrade Oracle Recovery Manager Catalog
If you are using the Oracle Recovery Manager, the catalog needs to be upgraded. Enter the following command to upgrade it. The UPGRADE CATALOG command must be entered twice to confirm the upgrade.
$ rman catalog username/password@alias
RMAN> UPGRADE CATALOG;
RMAN> UPGRADE CATALOG;
RMAN> EXIT;
4.3 Patch Deinstallation Instructions for Oracle RAC Environment
Patch deinstallation instructions for Oracle RAC includes these environments:
Follow these steps for each node in the cluster, one node at a time.
Shut down the instance on the node.
Run the OPatch utility specifying the rollback argument as follows.
opatch rollback -id 38729239
If there are errors, refer to Section 5, "Known Issues".
Start the instance on the node as follows:
srvctl start instance
4.4 Patch Post-Deinstallation Instructions for Oracle RAC Environment
On Oracle Database server, follow the instructions listed in Section Section 4.2, "Patch Post-Deinstallation Instructions for a Non-RAC Environment" only on the node for which the steps in Section 3.3.2, "Loading Modified SQL Files into the Database" were executed during the patch application. This is not required on Oracle Database client.
All other instances can be started and accessed as usual while you are executing the deinstallation steps.
5 Known Issues
For information about OPatch issues, see My Oracle Support Document KB133615 Primary Note For OPatch.
For legacy issues documented before April 31, 2022, see My Oracle Support document KB858347 Oracle Database 12.2.0.1 Release Update & Release Update Revision January 2022 Known Issues.
Other issues are as follows.
Issue 1   
The following ignorable errors may be encountered while running the datapatch/catbundle.sql script or its rollback script:
ORA-00942: table or view does not exist
ORA-00955: name is already used by an existing object
ORA-01430: column being added already exists in table
ORA-01432: public synonym to be dropped does not exist
ORA-01434: private synonym to be dropped does not exist
ORA-01435: user does not exist
ORA-01917: user or role 'XDB' does not exist
ORA-01920: user name '<user-name>' conflicts with another user or role name
ORA-01921: role name '<role name>' conflicts with another user or role name
ORA-01927: cannot REVOKE privileges you did not grant
ORA-01952: system privileges not granted to 'WKSYS'
ORA-02289: sequence does not exist 
ORA-02303: cannot drop or replace a type with type or table dependents
ORA-02443: Cannot drop constraint - nonexistent constraint
ORA-04043: object <object-name> does not exist
ORA-06512: at line <line number>. If this error follow any of above errors, then can be safely ignored.
ORA-14452: attempt to create, alter or drop an index on temporary table already in use
ORA-29809: cannot drop an operator with dependent objects
ORA-29830: operator does not exist
ORA-29832: cannot drop or replace an indextype with dependent indexes
ORA-29844: duplicate operator name specified 
ORA-29931: specified association does not exist
ORA-65209: signaled during: create lockdown profile ...
6 References
The following documents are references for this patch.
Document 38729239 Database Jan 2026 Release Update 12.2.0.1.260120
Document KB106822 Primary Note for Database Quarterly Release Updates
Document KB148594 Datapatch: Database 12c or later Post Patch SQL Automation
Document KB133615 Primary Note for OPatch
Document KB590650 Impact of Java SE Security Vulnerabilities on Oracle Database and Fusion Middleware Products
Document KB145571 Database Patch Conflict Resolution
Document KB852400 12.2.0.1 Database Release Update - List of Fixes in each RU/RUR
Document KA1376 Troubleshooting Assistant: Patching Oracle Database/Client
7 Bugs Fixed by This Patch
See My Oracle Support Document KB852400 for the list of bugs fixed in this patch.
8 Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id-docacc.
Access to Oracle Support
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.


Rollback database patch in oracle 12c
as per read me !!!
4.1 Patch Deinstallation Instructions for a Non-RAC Environment






[oracle@wcp12cr2 OPatch]$ sqlme

SQL*Plus: Release 12.2.0.1.0 Production on Mon Mar 9 05:19:18 2026

Copyright (c) 1982, 2016, Oracle.  All rights reserved.


Connected to:
Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production

SQL> shutdown immediate ;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> Disconnected from Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production



[oracle@wcp12cr2 OPatch]$ pwd
/u01/app/oracle/product/12.1.0/db_2/OPatch

[oracle@wcp12cr2 OPatch]$ echo $ORACLE_HOME
/u01/app/oracle/product/12.1.0/db_2








[oracle@wcp12cr2 OPatch]$ $ORACLE_HOME/OPatch/opatch rollback -id 38729239
Oracle Interim Patch Installer version 12.2.0.1.49
Copyright (c) 2026, Oracle Corporation.  All rights reserved.


Oracle Home       : /u01/app/oracle/product/12.1.0/db_2
Central Inventory : /oracle/oraInventory
   from           : /u01/app/oracle/product/12.1.0/db_2/oraInst.loc
OPatch version    : 12.2.0.1.49
OUI version       : 12.2.0.1.4
Log file location : /u01/app/oracle/product/12.1.0/db_2/cfgtoollogs/opatch/opatch2026-03-09_05-20-09AM_1.log


Patches will be rolled back in the following order:
   38729239
The following patch(es) will be rolled back: 38729239

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = '/u01/app/oracle/product/12.1.0/db_2')


Is the local system ready for patching? [y|n]
y
User Responded with: Y

Rolling back patch 38729239...

RollbackSession rolling back interim patch '38729239' from OH '/u01/app/oracle/product/12.1.0/db_2'

Patching component oracle.network.rsf, 12.2.0.1.0...

Patching component oracle.rdbms.rsf, 12.2.0.1.0...

Patching component oracle.rdbms.util, 12.2.0.1.0...

Patching component oracle.ctx, 12.2.0.1.0...

Patching component oracle.dbdev, 12.2.0.1.0...

Patching component oracle.dbtoolslistener, 12.2.0.1.0...

Patching component oracle.has.common.cvu, 12.2.0.1.0...

Patching component oracle.ldap.owm, 12.2.0.1.0...

Patching component oracle.ldap.rsf, 12.2.0.1.0...

Patching component oracle.marvel, 12.2.0.1.0...

Patching component oracle.nlsrtl.rsf, 12.2.0.1.0...

Patching component oracle.oracore.rsf, 12.2.0.1.0...

Patching component oracle.oraolap, 12.2.0.1.0...

Patching component oracle.ordim.client, 12.2.0.1.0...

Patching component oracle.perlint, 5.22.0.0.0...

Patching component oracle.rdbms, 12.2.0.1.0...

Patching component oracle.rdbms.crs, 12.2.0.1.0...

Patching component oracle.rdbms.dbscripts, 12.2.0.1.0...

Patching component oracle.rdbms.deconfig, 12.2.0.1.0...

Patching component oracle.rdbms.rsf.ic, 12.2.0.1.0...

Patching component oracle.sdo, 12.2.0.1.0...

Patching component oracle.sdo.locator, 12.2.0.1.0...

Patching component oracle.sdo.locator.jrf, 12.2.0.1.0...

Patching component oracle.swd.oui.core, 12.2.0.1.4...

Patching component oracle.sysman.ccr, 12.1.2.0.0...

Patching component oracle.sysman.ccr.client, 10.3.2.1.0...

Patching component oracle.tfa, 12.2.0.1.0...

Patching component oracle.ldap.client, 12.2.0.1.0...

Patching component oracle.ons, 12.2.0.1.0...

Patching component oracle.ldap.rsf.ic, 12.2.0.1.0...

Patching component oracle.rdbms.rman, 12.2.0.1.0...

Patching component oracle.assistants.deconfig, 12.2.0.1.0...

Patching component oracle.xdk.rsf, 12.2.0.1.0...

Patching component oracle.sqlplus.ic, 12.2.0.1.0...

Patching component oracle.duma, 12.2.0.1.0...

Patching component oracle.duma, 12.2.0.1.0...

Patching component oracle.xdk, 12.2.0.1.0...

Patching component oracle.assistants.server, 12.2.0.1.0...

Patching component oracle.sqlplus, 12.2.0.1.0...

Patching component oracle.rdbms.dv, 12.2.0.1.0...

Patching component oracle.ctx.rsf, 12.2.0.1.0...

Patching component oracle.precomp.rsf, 12.2.0.1.0...

Patching component oracle.assistants.acf, 12.2.0.1.0...

Patching component oracle.xdk.xquery, 12.2.0.1.0...

Patching component oracle.rdbms.hs_common, 12.2.0.1.0...

Patching component oracle.install.deinstalltool, 12.2.0.1.0...

Patching component oracle.xdk.parser.java, 12.2.0.1.0...

Patching component oracle.rdbms.oci, 12.2.0.1.0...

Patching component oracle.rdbms.hsodbc, 12.2.0.1.0...

Patching component oracle.network.listener, 12.2.0.1.0...

Patching component oracle.rdbms.install.plugins, 12.2.0.1.0...

Patching component oracle.ovm, 12.2.0.1.0...

Patching component oracle.ons.ic, 12.2.0.1.0...

Patching component oracle.rdbms.lbac, 12.2.0.1.0...

Patching component oracle.blaslapack, 12.2.0.1.0...

Patching component oracle.rdbms.install.common, 12.2.0.1.0...

Patching component oracle.precomp.lang, 12.2.0.1.0...

Patching component oracle.precomp.common, 12.2.0.1.0...

Patching component oracle.jdk, 1.8.0.91.0...
RollbackSession removing interim patch '38729239' from inventory
Log file location: /u01/app/oracle/product/12.1.0/db_2/cfgtoollogs/opatch/opatch2026-03-09_05-20-09AM_1.log

OPatch succeeded.
[oracle@wcp12cr2 OPatch]$ sqlme

SQL*Plus: Release 12.2.0.1.0 Production on Mon Mar 9 05:28:26 2026

Copyright (c) 1982, 2016, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> startup ;
ORACLE instance started.

Total System Global Area 3707764736 bytes
Fixed Size                  8799320 bytes
Variable Size             855641000 bytes
Database Buffers         2835349504 bytes
Redo Buffers                7974912 bytes
Database mounted.
Database opened.
SQL> alter pluggable database all open;

Pluggable database altered.

SQL> Disconnected from Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
[oracle@wcp12cr2 OPatch]$ pwd
/u01/app/oracle/product/12.1.0/db_2/OPatch
[oracle@wcp12cr2 OPatch]$ ls -ltr datapatch
-rwxr-x---. 1 oracle oinstall 589 Jan  6 02:26 datapatch
[oracle@wcp12cr2 OPatch]$
[oracle@wcp12cr2 OPatch]$ ./datapatch -verbose
SQL Patching tool version 12.2.0.1.0 Production on Mon Mar  9 05:30:12 2026
Copyright (c) 2012, 2017, Oracle.  All rights reserved.

Log file for this invocation: /u01/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_14950_2026_03_09_05_30_12/sqlpatch_invocation.log

Connecting to database...OK
Note:  Datapatch will only apply or rollback SQL fixes for PDBs
       that are in an open state, no patches will be applied to closed PDBs.
       Please refer to Note: Datapatch: Database 12c Post Patch SQL Automation
       (Doc ID 1585822.1)
Bootstrapping registry and package to current versions...done
Determining current state...done

Current state of SQL patches:
Bundle series DBRU:
  Not installed in the binary registry and ID 260120 in PDB CDB$ROOT, ID 260120 in PDB PDB$SEED, ID 260120 in PDB VIHAAN

Adding patches to installation queue and performing prereq checks...
Installation queue:
  For the following PDBs: CDB$ROOT PDB$SEED VIHAAN
    The following patches will be rolled back:
      38729239 (DATABASE JAN 2026 RELEASE UPDATE 12.2.0.1.260120)
    Nothing to apply

Installing patches...



Patch installation complete.  Total patches installed: 3

Validating logfiles...
Patch 38729239 rollback (pdb CDB$ROOT): SUCCESS
  logfile: /u01/app/oracle/cfgtoollogs/sqlpatch/38729239/28365030/38729239_rollback_ORCLDB_CDBROOT_2026Mar09_05_31_34.log (no errors)
Patch 38729239 rollback (pdb PDB$SEED): SUCCESS
  logfile: /u01/app/oracle/cfgtoollogs/sqlpatch/38729239/28365030/38729239_rollback_ORCLDB_PDBSEED_2026Mar09_05_41_31.log (no errors)
Patch 38729239 rollback (pdb VIHAAN): SUCCESS
  logfile: /u01/app/oracle/cfgtoollogs/sqlpatch/38729239/28365030/38729239_rollback_ORCLDB_VIHAAN_2026Mar09_05_41_31.log (no errors)
SQL Patching tool complete on Mon Mar  9 05:50:59 2026




[oracle@wcp12cr2 OPatch]$ opatch lsinventory | grep -E "(^Patch.*applied)|(^Sub-patch)"
--- no row 


[oracle@wcp12cr2 OPatch]$ sqlme

SQL*Plus: Release 12.2.0.1.0 Production on Mon Mar 9 05:55:31 2026

Copyright (c) 1982, 2016, Oracle.  All rights reserved.


Connected to:
Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production

SQL>

set linesize 300
col PDB_NAME for a20
SELECT c.name AS pdb_name,
       r.patch_id,
       r.action,
       r.status,
       r.action_time
FROM   cdb_registry_sqlpatch r
JOIN   v$containers c
ON     r.con_id = c.con_id
ORDER  BY r.action_time;


PDB_NAME               PATCH_ID ACTION          STATUS                    ACTION_TIME
-------------------- ---------- --------------- ------------------------- ---------------------------------------------------------------------------
CDB$ROOT               38729239 APPLY           SUCCESS                   09-MAR-26 01.24.23.154077 AM
VIHAAN                 38729239 APPLY           WITH ERRORS               09-MAR-26 01.24.37.313038 AM
VIHAAN                 38729239 APPLY           SUCCESS                   09-MAR-26 01.45.21.046180 AM
CDB$ROOT               38729239 ROLLBACK        SUCCESS                   09-MAR-26 05.50.42.631032 AM
VIHAAN                 38729239 ROLLBACK        SUCCESS                   09-MAR-26 05.50.50.241946 AM

Steps	Non-CDB or Non-PDB Database	Steps	Multitenant (CDB/PDB) Oracle Database
1	`sqlplus /nolog`	1	`sqlplus /nolog`
2	`SQL> Connect / as sysdba`	2	`SQL> Connect / as sysdba`
3	`SQL> startup`	3	`SQL> startup`
4	`SQL> quit`	4	`SQL> alter pluggable database all` `open;`^{Foot 1}
5	`cd $ORACLE_HOME/OPatch`	5	`SQL> quit`
6	`./datapatch -verbose`	6	`cd $ORACLE_HOME/OPatch`
		7	`./datapatch -verbose`

Steps	Non-CDB or Non-PDB Database	Steps	Multitenant (CDB/PDB) Oracle Database
1	`sqlplus /nolog`	1	`sqlplus /nolog`
2	`SQL> Connect / as sysdba`	2	`SQL> Connect / as sysdba`
3	`SQL> startup`	3	`SQL> startup`
4	`SQL> quit`	4	`SQL> alter pluggable database all` `open;`^{Foot 1}
5	`cd $ORACLE_HOME/OPatch`	5	`SQL> quit`
6	`./datapatch -verbose`	6	`cd $ORACLE_HOME/OPatch`
		7	`./datapatch -verbose`

Anuj Singh Oracle DBA

Search This Blog

Total Pageviews

Monday, 9 March 2026

Oracle 12c Patch 38729239 - Database Jan 2026 Release Update 12.2.0.1.260120

OracleÂ® Database

1 Patch Information

2 Prerequisites

2.1 OPatch Utility

3 Installation

3.1 Patch Pre-Installation Instructions

3.1.1 Applying Database 12.2.0.1.x Updates/Revisions with Oracle JavaVM 12.2.0.1.x Updates

3.1.2 Environments with Grid Infrastructure

3.1.3 Environment Checks

3.1.4 Interim Patch Conflict Detection and Resolution

3.2 Patch Installation Instructions

3.3 Patch Post-Installation Instructions

3.3.1 Apply Conflict Resolution Patches

3.3.2 Load Modified SQL Files into the Database

3.3.3 Upgrade Oracle Recovery Manager Catalog

3.3.4 Bug Fixes That May Change an Existing Optimizer Execution Plan

3.4 Patch Post-Installation Instructions for Databases Created or Upgraded after Installation of this patch in the Oracle Home

4 Deinstallation

4.1 Patch Deinstallation Instructions for a Non-RAC Environment

4.2 Patch Post-Deinstallation Instructions for a Non-RAC Environment

4.2.1 Load Modified SQL Files into the Database

4.2.2 Upgrade Oracle Recovery Manager Catalog

4.3 Patch Deinstallation Instructions for Oracle RAC Environment

4.4 Patch Post-Deinstallation Instructions for Oracle RAC Environment

5 Known Issues

6 References

7 Bugs Fixed by This Patch

8 Documentation Accessibility

Rollback database patch in oracle 12c

4.1 Patch Deinstallation Instructions for a Non-RAC Environment

No comments:

Oracle DBA

anuj blog Archive