Anuj Singh Oracle DBA

Friday, 27 February 2026

Oracle database patch 38632161 >>>>> 19.30.0.0.0

 

Old Post !!!!
https://anuj-singh.blogspot.com/search?q=patch+Info


Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.30.0.0.0  <<< patch no 38632161


[oracle@localhost db_1]$
 
p38632161_190000_Linux-x86-64.zip  2.2gb !!!

patch size !!!

[root@localhost media]# du -sh */
4.8G    38632161/

export PATH=$ORACLE_HOME/OPatch:$PATH
/u01/app/oracle/product/version/db_1

mv OPatch OPatch.`date +"%Y"-"%m"-"%d"`

unzip -oq /home/oracle/p6880880_190000_Linux-x86-64.zip

[oracle@localhost db_1]$ ls -ld OPatch*
drwxr-x--- 15 oracle oinstall 4096 Jan  6 05:30 OPatch
drwxr-x--- 14 oracle oinstall 4096 Feb 27 05:27 OPatch.2026-02-27

opatch version
OPatch Version: 12.2.0.1.49  --- check the version!!!!

OPatch succeeded.



===========

[oracle@localhost 38632161]$ $ORACLE_HOME/OPatch/opatch lsinventory | grep -E "(^Patch.*applied)|(^Sub-patch)"
Patch  29585399     : applied on Thu Apr 18 03:21:33 EDT 2019
Patch  29517242     : applied on Thu Apr 18 03:21:17 EDT 2019
[oracle@localhost 38632161]$

===========


cd /media/38632161
opatch prereq CheckConflictAgainstOHWithDetail -ph ./


[oracle@localhost 38632161]$ 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/19.0.0/db_1
Central Inventory : /u01/app/oraInventory
   from           : /u01/app/oracle/product/19.0.0/db_1/oraInst.loc
OPatch version    : 12.2.0.1.49
OUI version       : 12.2.0.7.0
Log file location : /u01/app/oracle/product/19.0.0/db_1/cfgtoollogs/opatch/opatch2026-02-27_05-56-31AM_1.log

Invoking prereq "checkconflictagainstohwithdetail"

Prereq "checkConflictAgainstOHWithDetail" passed.

OPatch succeeded.
[oracle@localhost 38632161]$


--- Shutdown !!!
SQL> shutdown immediate ;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production


[oracle@localhost 38632161]$ pwd
/media/38632161


[oracle@localhost 38632161]$ 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/19.0.0/db_1
Central Inventory : /u01/app/oraInventory
   from           : /u01/app/oracle/product/19.0.0/db_1/oraInst.loc
OPatch version    : 12.2.0.1.49
OUI version       : 12.2.0.7.0
Log file location : /u01/app/oracle/product/19.0.0/db_1/cfgtoollogs/opatch/opatch2026-02-27_06-14-04AM_1.log

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

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

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


Is the local system ready for patching? [y|n]
y
User Responded with: Y
Backing up files...
Applying interim patch '38632161' to OH '/u01/app/oracle/product/19.0.0/db_1'
ApplySession: Optional component(s) [ oracle.network.gsm, 19.0.0.0.0 ] , [ oracle.assistants.asm, 19.0.0.0.0 ] , [ oracle.crypto.rsf, 19.0.0.0.0 ] , [ oracle.datamining, 19.0.0.0.0 ] , [ oracle.oraolap.mgmt, 19.0.0.0.0 ] , [ oracle.pg4appc, 19.0.0.0.0 ] , [ oracle.pg4mq, 19.0.0.0.0 ] , [ oracle.precomp.companion, 19.0.0.0.0 ] , [ oracle.rdbms.ic, 19.0.0.0.0 ] , [ oracle.rdbms.tg4db2, 19.0.0.0.0 ] , [ oracle.sdo.companion, 19.0.0.0.0 ] , [ oracle.tfa, 19.0.0.0.0 ] , [ oracle.rdbms.tg4msql, 19.0.0.0.0 ] , [ oracle.ons.eons.bwcompat, 19.0.0.0.0 ] , [ oracle.options.olap.api, 19.0.0.0.0 ] , [ oracle.rdbms.tg4sybs, 19.0.0.0.0 ] , [ oracle.net.cman, 19.0.0.0.0 ] , [ oracle.options.olap, 19.0.0.0.0 ] , [ oracle.network.cman, 19.0.0.0.0 ] , [ oracle.pg4mq, 19.0.0.0.0 ] , [ oracle.oraolap.mgmt, 19.0.0.0.0 ] , [ oracle.java.sqlj.sqljruntime, 19.0.0.0.0 ] , [ oracle.datamining, 19.0.0.0.0 ] , [ oracle.xdk.companion, 19.0.0.0.0 ] , [ oracle.rdbms.tg4tera, 19.0.0.0.0 ] , [ oracle.ldap.ztk, 19.0.0.0.0 ] , [ oracle.ons.cclient, 19.0.0.0.0 ] , [ oracle.oid.client, 19.0.0.0.0 ] , [ oracle.rdbms.tg4ifmx, 19.0.0.0.0 ] , [ oracle.jdk, 1.8.0.191.0 ] , [ oracle.jdk, 1.8.0.391.11 ]  not present in the Oracle Home or a higher version is found.

Patching component oracle.rdbms.rsf, 19.0.0.0.0...
Patching component oracle.rdbms, 19.0.0.0.0...
Patching component oracle.rdbms.util, 19.0.0.0.0...
Patching component oracle.assistants.acf, 19.0.0.0.0...
Patching component oracle.assistants.deconfig, 19.0.0.0.0...
Patching component oracle.assistants.server, 19.0.0.0.0...
Patching component oracle.blaslapack, 19.0.0.0.0...
Patching component oracle.buildtools.rsf, 19.0.0.0.0...
Patching component oracle.ctx, 19.0.0.0.0...
Patching component oracle.dbdev, 19.0.0.0.0...
Patching component oracle.dbjava.ic, 19.0.0.0.0...
Patching component oracle.dbjava.jdbc, 19.0.0.0.0...
Patching component oracle.dbjava.ucp, 19.0.0.0.0...
Patching component oracle.duma, 19.0.0.0.0...
Patching component oracle.javavm.client, 19.0.0.0.0...
Patching component oracle.ldap.client, 19.0.0.0.0...
Patching component oracle.ldap.owm, 19.0.0.0.0...
Patching component oracle.ldap.rsf, 19.0.0.0.0...
Patching component oracle.ldap.security.osdt, 19.0.0.0.0...
Patching component oracle.marvel, 19.0.0.0.0...
Patching component oracle.network.rsf, 19.0.0.0.0...
Patching component oracle.odbc.ic, 19.0.0.0.0...
Patching component oracle.ons, 19.0.0.0.0...
Patching component oracle.ons.ic, 19.0.0.0.0...
Patching component oracle.oracore.rsf, 19.0.0.0.0...
Patching component oracle.perlint, 5.28.1.0.0...
Patching component oracle.precomp.common.core, 19.0.0.0.0...
Patching component oracle.precomp.rsf, 19.0.0.0.0...
Patching component oracle.rdbms.crs, 19.0.0.0.0...
Patching component oracle.rdbms.dbscripts, 19.0.0.0.0...
Patching component oracle.rdbms.deconfig, 19.0.0.0.0...
Patching component oracle.rdbms.install.common, 19.0.0.0.0...
Patching component oracle.rdbms.oci, 19.0.0.0.0...
Patching component oracle.rdbms.rsf.ic, 19.0.0.0.0...
Patching component oracle.rdbms.scheduler, 19.0.0.0.0...
Patching component oracle.rhp.db, 19.0.0.0.0...
Patching component oracle.rsf, 19.0.0.0.0...
Patching component oracle.sdo, 19.0.0.0.0...
Patching component oracle.sdo.locator.jrf, 19.0.0.0.0...
Patching component oracle.sqlj.sqljruntime, 19.0.0.0.0...
Patching component oracle.sqlplus, 19.0.0.0.0...
Patching component oracle.sqlplus.ic, 19.0.0.0.0...
Patching component oracle.tfa.db, 19.0.0.0.0...
Patching component oracle.wwg.plsql, 19.0.0.0.0...
Patching component oracle.xdk.rsf, 19.0.0.0.0...
Patching component oracle.xdk.parser.java, 19.0.0.0.0...
Patching component oracle.rdbms.lbac, 19.0.0.0.0...
Patching component oracle.ldap.ssl, 19.0.0.0.0...
Patching component oracle.network.aso, 19.0.0.0.0...
Patching component oracle.xdk, 19.0.0.0.0...
Patching component oracle.nlsrtl.rsf.core, 19.0.0.0.0...
Patching component oracle.odbc, 19.0.0.0.0...
Patching component oracle.rdbms.rat, 19.0.0.0.0...
Patching component oracle.rdbms.dv, 19.0.0.0.0...
Patching component oracle.oraolap.dbscripts, 19.0.0.0.0...
Patching component oracle.rdbms.hs_common, 19.0.0.0.0...
Patching component oracle.ldap.rsf.ic, 19.0.0.0.0...
Patching component oracle.oraolap, 19.0.0.0.0...
Patching component oracle.install.deinstalltool, 19.0.0.0.0...
Patching component oracle.mgw.common, 19.0.0.0.0...
Patching component oracle.rdbms.rman, 19.0.0.0.0...
Patching component oracle.xdk.server, 19.0.0.0.0...
Patching component oracle.oraolap.api, 19.0.0.0.0...
Patching component oracle.rdbms.hsodbc, 19.0.0.0.0...
Patching component oracle.ctx.atg, 19.0.0.0.0...
Patching component oracle.nlsrtl.rsf, 19.0.0.0.0...
Patching component oracle.nlsrtl.rsf.core, 19.0.0.0.0...
Patching component oracle.nlsrtl.rsf.ic, 19.0.0.0.0...
Patching component oracle.sqlj.sqljruntime, 19.0.0.0.0...
Patching component oracle.wwg.plsql, 19.0.0.0.0...
Patching component oracle.network.client, 19.0.0.0.0...
Patching component oracle.dbtoolslistener, 19.0.0.0.0...
Patching component oracle.rdbms.install.plugins, 19.0.0.0.0...
Patching component oracle.ctx.rsf, 19.0.0.0.0...
Patching component oracle.nlsrtl.rsf.lbuilder, 19.0.0.0.0...
Patching component oracle.rdbms.drdaas, 19.0.0.0.0...
Patching component oracle.sdo.locator, 19.0.0.0.0...
Patching component oracle.rdbms.locator, 19.0.0.0.0...
Patching component oracle.network.listener, 19.0.0.0.0...
Patching component oracle.ovm, 19.0.0.0.0...
Patching component oracle.javavm.server, 19.0.0.0.0...
Patching component oracle.xdk.xquery, 19.0.0.0.0...
Patching component oracle.precomp.common, 19.0.0.0.0...
Patching component oracle.precomp.lang, 19.0.0.0.0...

Patching component oracle.jdk, 1.8.0.201.0...
Patch 38632161 successfully applied.
Sub-set patch [29517242] has become inactive due to the application of a super-set patch [38632161].
Please refer to Doc ID 2161861.1 for any possible further required actions.
Log file location: /u01/app/oracle/product/19.0.0/db_1/cfgtoollogs/opatch/opatch2026-02-27_06-14-04AM_1.log

OPatch succeeded.


before 
[oracle@localhost 38632161]$ $ORACLE_HOME/OPatch/opatch lsinventory | grep -E "(^Patch.*applied)|(^Sub-patch)"
Patch  29585399     : applied on Thu Apr 18 03:21:33 EDT 2019
Patch  29517242     : applied on Thu Apr 18 03:21:17 EDT 2019
[oracle@localhost 38632161]$

after 
[oracle@localhost 38632161]$ $ORACLE_HOME/OPatch/opatch lsinventory | grep -E "(^Patch.*applied)|(^Sub-patch)"
Patch  38632161     : applied on Fri Feb 27 06:37:40 EST 2026
Patch  29585399     : applied on Thu Apr 18 03:21:33 EDT 2019


===
[oracle@localhost 38632161]$ sqlplus /nolog

SQL*Plus: Release 19.0.0.0.0 - Production on Fri Feb 27 06:54:45 2026
Version 19.30.0.0.0

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

SQL> Connect / as sysdba
Connected to an idle instance.

SQL> startup;
ORACLE instance started.

Total System Global Area  838856872 bytes
Fixed Size                  9183400 bytes
Variable Size             230686720 bytes
Database Buffers          595591168 bytes
Redo Buffers                3395584 bytes
Database mounted.
Database opened.



SQL> alter pluggable database all open;
Pluggable database altered.





SQL> show pdbs

    CON_ID CON_NAME                       OPEN MODE  RESTRICTED
---------- ------------------------------ ---------- ----------
         2 PDB$SEED                       READ ONLY  NO
         3 ORCL                           READ WRITE NO
	
cd $ORACLE_HOME/OPatch
	
./datapatch -sanity_checks (optional)


[oracle@localhost OPatch]$ ./datapatch -sanity_checks   ----<<<<<<<<<<<<<<<<<   
SQL Patching sanity checks version 19.30.0.0.0 on Fri 27 Feb 2026 06:57:55 AM EST
Copyright (c) 2021, 2026, Oracle.  All rights reserved.

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

Running checks
JSON report generated in /u01/app/oracle/cfgtoollogs/sqlpatch/sanity_checks_20260227_065755_13794/sqlpatch_sanity_checks_summary.json file
Checks completed. Printing report:

Check: Database component status - OK
Check: PDB Violations - OK
Check: Invalid System Objects - OK
Check: Tablespace Status - OK
Check: Backup jobs - OK
Check: Temp file exists - OK
Check: Temp file online - OK
Check: Data Pump running - OK
Check: Container status - OK
Check: Oracle Database Keystore - OK
Check: Dictionary statistics gathering - OK
Check: Scheduled Jobs - OK
Check: GoldenGate triggers - OK
Check: Logminer DDL triggers - OK
Check: Check sys public grants - OK
Check: Statistics gathering running - OK
Check: Optim dictionary upgrade parameter - OK
Check: Symlinks on oracle home path - OK
Check: Central Inventory - OK
Check: Java Virtual Machine Enable - OK
Check: Oracle Database Vault Enabled - OK
Check: Queryable Inventory database directories - OK
Check: Queryable Inventory locks - OK
Check: Queryable Inventory package - OK
Check: Queryable Inventory external table - OK
Check: Imperva processes - OK
Check: Guardium processes - OK
Check: Locale - OK

SQL Patching sanity checks completed on Fri 27 Feb 2026 07:00:18 AM EST


======
	
./datapatch -verbose



=====

if required !!!

alert log !!!

  Current log# 2 seq# 8 mem# 0: /u01/app/oracle/oradata/ORCLCDB/redo02.log
2026-02-27T07:24:22.313401-05:00
ARC3 (PID:13432): Archived Log entry 14 added for B-1124854827.T-1.S-7 LOS:0x0000000000412871 NXS:0x0000000000423ff8 NAB:356004 ID 0xac9b7a55 LAD:1
2026-02-27T07:25:37.932436-05:00
PL/SQL package SYS.DBMS_BACKUP_RESTORE version  is not current
PL/SQL package SYS.DBMS_RCVMAN version 19.03.00.00 is too old
2026-02-27T07:30:04.307939-05:00


sys user in the CDB$ROOT.
SQL> @$ORACLE_HOME/rdbms/admin/dbmsrman.sql
SQL> @$ORACLE_HOME/rdbms/admin/dbmsbkrs.sql
SQL> @$ORACLE_HOME/rdbms/admin/prvtrmns.plb
SQL> @$ORACLE_HOME/rdbms/admin/prvtbkrs.plb



alert log !!!

ORA-12012: error on auto execute of job "SYS"."CLEANUP_ONLINE_IND_BUILD"

select owner,job_name,start_date,repeat_interval,state 
from dba_scheduler_jobs where job_name = 'CLEANUP_ONLINE_IND_BUILD';



export PATH=$PATH:$ORACLE_HOME/bin
cd $ORACLE_HOME/rdbms/admin
$ORACLE_HOME/perl/bin/perl $ORACLE_HOME/rdbms/admin/catcon.pl -n 1 -e -b utlrp -d $ORACLE_HOME/rdbms/admin utlrp.sql

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

README file

Patch 38632161 - Database Release Update 19.30.0.0.0(REL-JAN260130)


This document is accurate at the time of release. For any changes and additional information regarding Database Release Update 19.30.0.0.260120, see these related documents that are available at My Oracle Support (http://support.oracle.com/):
Document KB860153 Oracle DB/GI/OJVM Update/Revision R19 Jan 2026 Known Issues
Document KB188772 Oracle Database 19c and Oracle AI Database 26ai Important Recommended One-off Patches
Document KB106822 Primary Note for Database Quarterly Release Updates
Document KA19 19c Database Upgrade - Self Guided Assistance with Best Practices
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 Release Update 19.30.0.0.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 Release Update 19.30.0.0.260120 patch, the Oracle home must have Oracle Database release 19c installed.
This patch is Oracle RAC Rolling Installable.
This patch is Database Vault installable. See My Oracle Support document KB653211 Primary Note For Oracle Database Vault 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. See My Oracle Support document KB106822 Primary Note for Database Quarterly Release Updates for the JDK patch number.
Beginning with 19.27 Apr2025 DBRU, Small Pages are not allowed for RDBMS SGA in Exadata. See My Oracle Support Document KB174916 for more details.
Beginning with 19.21 Oct2023 RU, the UTL_URI.ESCAPE function is now compliant with RFC 3896 and will treat "#" as a reserved character. See My Oracle Support Document PALRT1208 for more details.
Beginning with 19.22 Jan2024 RU, the 19c database is now certified on Oracle Linux 9.x and RHEL9.x.
Beginning with 19.18 Jan2023 RU, the DBRU contains the CORE DST Time Zone patches. Applying this Release Update (RU) does not change the DST version in any of your databases. The DST patches are only copied into $ORACLE_HOME/oracore/zoneinfo and no DST upgrade is performed. You can decide to upgrade the DST version in your database to a newer DST version independently of applying the RU at any time. Be aware that this incurs downtime.
You can decide to upgrade the DST version in your database to a newer DST version independently of applying the RU at any time. Be aware that this incurs downtime.
If you plan to adjust the DST version of your databases, Oracle recommends adjusting it to the latest available DST version. Follow the instructions in the Oracle 19c Oracle Database Upgrade Guide. For more information on various DST patch releases, see My Oracle Support document KB151444 Primary Note DST FAQ: Updated DST Transitions and New Time Zones in Oracle RDBMS and OJVM Time Zone File Patches.
This DBRU contains the following CORE DST patches:
Patch Numbers Patches
28852325 DSTV33 UPDATE - TZDATA2018G
29997937 DSTV34 UPDATE - TZDATA2019B
31335037 DSTV35 UPDATE - TZDATA2020A
32327201 DSTV36 UPDATE - TZDATA2020E
33613829 DSTV37 UPDATE - TZDATA2021E
34006614 DSTV38 UPDATE - TZDATA2022A
34533061 DSTV39 UPDATE - TZDATA2022C
34698179 DSTV40 UPDATE - TZDATA2022E
35099667 DSTV41 UPDATE - TZDATA2022G
35220732 DSTV42 UPDATE - TZDATA2023C
36260493 DSTV43 UPDATE - TZDATA2024A
37537949 DSTV44 UPDATE - TZDATA2025A
Any new or changed database initialization parameters that might be included into a quarterly patch bundle would be documented in the Oracle Database Reference manual section on initialization parameters. For Oracle Database 19c, see Oracle Database Reference.
For the latest Update with Security Fixes that should be used on Client-Only installations, see the Critical Patch Update (CPU) Program Patch Availability Document (PAD) section on the Oracle Database, for the cycle in which you are interested.
Applying Database Release Update Database Release Update 19.30.0.0.260120 with Oracle JavaVM 19.x Updates
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 Update" (OJVM PSU and OJVM Update) Patches.
The Oracle JavaVM 19.x Release Update is available as a separate patch. That separate patch has some additional requirements if it is to be installed in a RAC Rolling fashion, as detailed in My Oracle Support document:KB137197 - RAC Rolling Install Process for the "Oracle JavaVM Component Database PSU/RU" (OJVM PSU/RU) Patches.
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, see My Oracle Support document KB137807 How to Perform ORACLE_HOME Backup?.
For SUSE Linux Enterprise Server (SLES) 15 SP3, and above, install the compat-libpthread-nonshared package. See section 5.5.12 in SUSE's release notes (for SLES 15 SP3) and Note KB117927.
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 version for 19c, which is available for download from My Oracle Support patch 6880880 by selecting "OPatch for DB 19.0.0.0.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 Release Update 19.30.0.0.260120, perform the following actions to check the environment and to detect and resolve any interim patch conflicts.
3.1.1 Environments with Grid Infrastructure
This patch is not to be installed to an environment that has a Grid Infrastructure home. See the following My Oracle Support document KB106822 to determine the appropriate Grid infrastructure patch to be installed.
3.1.2 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.3 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 Release Update 19.30.0.0.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, 38632161:
Step Command
1. unzip p38632161_<version>_<platform>.zip
2. cd 38632161
3. 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 How To Apply DBRU in a Data Guard Physical Standby Configuration (Non Standby-First Installable).
If this is an Oracle RAC environment, install this patch using the OPatch rolling (no downtime) installation method as this patch is rolling RAC installable. See 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 Command:
Step Command
1. unzip -d <PATCH_TOP_DIR> p38632161_<version>_<platform>.zip
2. cd <PATCH_TOP_DIR> 38632161
3. 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.
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 an Oracle 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 Issues and workarounds to common problems, see My Oracle Support document KB148594 Datapatch: Database 12c or later Post Patch SQL Automation and My Oracle Support document KB123801 Datapatch User Guide.
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) Oracle 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 -sanity_checks (optional) 6 cd $ORACLE_HOME/OPatch
7 ./datapatch -verbose 7 ./datapatch -sanity_checks (optional)


8 ./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 or 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).
Recommended: The datapatch -sanity_checks optional step runs a series of environment and database checks to validate if conditions are optimal for patching. Results are shown on screen with severity and potential actions to take.
For more information, see My Oracle Support document KB123801 Datapatch User Guide for additional information and actions. Oracle highly recommends that you perform this step.
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 that the status for the APPLY is SUCCESS.
For any other status, see My Oracle Support document KA1374 Troubleshooting Assistant: 12c Datapatch Issues for additional information and actions.
Check the following log files in $ORACLE_BASE/cfgtoollogs/sqlpatch/38632161/<unique patch ID> for errors:
38632161_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.
Any (pluggable) database that has invalid objects after the execution of datapatch should have catcon.pl run to revalidate those objects. For example:
Step Command
1. export PATH=$PATH:$ORACLE_HOME/bin
2. cd $ORACLE_HOME/rdbms/admin
3. $ORACLE_HOME/perl/bin/perl $ORACLE_HOME/rdbms/admin/catcon.pl -n 1 -e -b utlrp -d $ORACLE_HOME/rdbms/admin 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.
Step Command
1. $ rman catalog username/password@alias
2. RMAN> UPGRADE CATALOG;
3. RMAN> UPGRADE CATALOG;
4. 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 Managing "installed but disabled" bug fixes in Database Release Updates using DBMS_OPTIM_BUNDLE.
3.3.5 Update Permissions for extjob
Database release update patch installation involves relinking of libraries and executables to be updated. This can sometimes result in permissions changing and needing to be updated. Execute the following as root user:
Step Command
1. # chown root $ORACLE_HOME/bin/extjob
2. # chmod 4750 $ORACLE_HOME/bin/extjob
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, "Load 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.
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 38632161
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 Issues and workarounds to common problems, see My Oracle Support document KB148594 Datapatch: Database 12c or later Post Patch SQL Automation and My Oracle Support document KB123801 Datapatch User Guide.
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 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 -sanity_checks (optional) 6 cd $ORACLE_HOME/OPatch
7 ./datapatch -verbose 7 ./datapatch -sanity_checks (optional)


8 ./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).
Recommended: The datapatch -sanity_checks optional step runs a series of environment and database checks to validate if conditions are optimal for patching. Results are shown on screen with severity and potential actions to take.
For more information, see the My Oracle Support document KB123801 Datapatch User Guide for additional information and actions. Oracle highly recommends that you perform this step.
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, see My Oracle Support document KA1374 Troubleshooting Assistant: 12c Datapatch Issues for additional information and actions.
Check the following log files in $ORACLE_BASE/cfgtoollogs/sqlpatch/38632161/<unique patch ID> for errors:
38632161_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.
Any (pluggable) database that has invalid objects after the execution of datapatch should have catcon.pl run to revalidate those objects. For example:
Step Command
1. cd $ORACLE_HOME/rdbms/admin
2. $ORACLE_HOME/perl/bin/perl $ORACLE_HOME/rdbms/admin/catcon.pl -n 1 -e -b utlrp -d $ORACLE_HOME/rdbms/admin 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.
Step Command
1. $ rman catalog username/password@alias
2. RMAN> UPGRADE CATALOG;
3. RMAN> UPGRADE CATALOG;
4. 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 38632161
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, "Load 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 issues documented after the release of this patch, see My Oracle Support document KB860153 Oracle DB/GI/OJVM Update/Revision R19 Jan 2026 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
6 References
The following documents are references for this patch.
Document 38632161 Database Release Update 19.30.0.0.0(REL-JAN260130)
Document KA19 19c Database Upgrade - Self Guided Assistance with Best Practices
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 KB151444 Primary Note DST FAQ: Updated DST Transitions and New Time Zones in Oracle RDBMS and OJVM Time Zone File Patches
Document KB145571 Database Patch Conflict Resolution
Document KB850150 Database 19 Release Updates and Revisions Bugs Fixed Lists
Document KA1376 Troubleshooting Assistant: Patching Oracle Database/Client
7 Bugs Fixed by This Patch
See My Oracle Support document KB850150 Database 19 Release Updates and Revisions Bugs Fixed Lists 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.
Patch 38632161 - Database Release Update 19.30.0.0.0(REL-JAN260130)
Copyright © 2026, Oracle and/or its affiliates.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract. The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle®, Java, MySQL, and NetSuite are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

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 -sanity_checks (optional)`	6	`cd $ORACLE_HOME/OPatch`
7	`./datapatch -verbose`	7	`./datapatch -sanity_checks (optional)`
		8	`./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 -sanity_checks (optional)`	6	`cd $ORACLE_HOME/OPatch`
7	`./datapatch -verbose`	7	`./datapatch -sanity_checks (optional)`
		8	`./datapatch -verbose`

Anuj Singh Oracle DBA

Search This Blog

Total Pageviews

Friday, 27 February 2026

Oracle database patch 38632161 >>>>> 19.30.0.0.0

1 Patch Information

2 Prerequisites

2.1 OPatch Utility

3 Installation

3.1 Patch Pre-Installation Instructions

3.1.1 Environments with Grid Infrastructure

3.1.2 Environment Checks

3.1.3 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.3.5 Update Permissions for extjob

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

Oracle DBA

anuj blog Archive

Patch Numbers	Patches
28852325	DSTV33 UPDATE - TZDATA2018G
29997937	DSTV34 UPDATE - TZDATA2019B
31335037	DSTV35 UPDATE - TZDATA2020A
32327201	DSTV36 UPDATE - TZDATA2020E
33613829	DSTV37 UPDATE - TZDATA2021E
34006614	DSTV38 UPDATE - TZDATA2022A
34533061	DSTV39 UPDATE - TZDATA2022C
34698179	DSTV40 UPDATE - TZDATA2022E
35099667	DSTV41 UPDATE - TZDATA2022G
35220732	DSTV42 UPDATE - TZDATA2023C
36260493	DSTV43 UPDATE - TZDATA2024A
37537949	DSTV44 UPDATE - TZDATA2025A

Step	Command
1.	unzip p38632161_<version>_<platform>.zip
2.	cd 38632161
3.	opatch prereq CheckConflictAgainstOHWithDetail -ph ./

Step	Command
1.	unzip -d <PATCH_TOP_DIR> p38632161_<version>_<platform>.zip
2.	cd <PATCH_TOP_DIR> 38632161
3.	opatch apply

Step	Command
1.	export PATH=$PATH:$ORACLE_HOME/bin
2.	cd $ORACLE_HOME/rdbms/admin
3.	$ORACLE_HOME/perl/bin/perl $ORACLE_HOME/rdbms/admin/catcon.pl -n 1 -e -b utlrp -d $ORACLE_HOME/rdbms/admin utlrp.sql

Step	Command
1.	$ rman catalog username/password@alias
2.	RMAN> UPGRADE CATALOG;
3.	RMAN> UPGRADE CATALOG;
4.	RMAN> EXIT;

Step	Command
1.	# chown root $ORACLE_HOME/bin/extjob
2.	# chmod 4750 $ORACLE_HOME/bin/extjob