Oracle has released Patch 39222882, the Oracle JavaVM Component Release Update (OJVM RU) 19.32.0.0.260721 for Oracle Database 19c as part of the July 2026 Critical Patch Update (CPU).
This update contains security fixes for the embedded Java Virtual Machine (OJVM) inside Oracle Database and should be applied alongside the Oracle Database 19.32 Release Update (Patch 39472050).
In this article, we’ll walk through the complete installation process including prerequisite checks, OPatch installation, Datapatch execution, and verification.
What is OJVM Release Update?
Oracle JavaVM (OJVM) allows Java programs to run directly inside the Oracle Database.
The OJVM Release Update provides:
- Security fixes
- JavaVM bug fixes
- Database CPU security content
- Cumulative fixes from previous OJVM updates
- OJVM DST (Daylight Saving Time) files
Beginning with 19.23, Oracle states that OJVM Release Updates are FIPS compliant when installed together with Database Release Update 19.23 or later. Beginning with 19.24, OJVM RUs also include the latest OJVM DST files (no database DST upgrade is automatically performed).
Patch Information
| Item | Value |
|---|---|
| Patch Number | 39222882 |
| Patch Name | Oracle JavaVM Component Release Update |
| Version | 19.32.0.0.260721 |
| Release | Oracle Database 19c |
| Type | Interim Patch |
| Requires | Database RU 19.32 |
| Installation | OPatch + Datapatch |
Prerequisites
Before installing the OJVM patch:
- Oracle Database 19c
- Database RU 19.32 already installed
- Latest OPatch (12.2.0.1.51 or later)
- Valid Oracle Inventory
- Backup of Oracle Home and Database
- Shutdown database before applying binaries (unless following supported RAC rolling procedures)
- Verify there are no patch conflicts
Verify Current Patches
$ opatch lspatchesExample:
39472050; Database Release Update : 19.32.0.0.260721
29585399; OCW RELEASE UPDATEUnzip the Patch
Download Patch 39472050 from My Oracle Support.
DOWNLOAD PATCH : Critical Patch Update (CPU) Jul 2026 for Oracle Database Products
unzip -d <PATCH_TOP_DIR> p39222882_190000_<PLATFORM_NAME>.zip
cd <PATCH_TOP_DIR>/39222882Verify OPatch Version
Before patching, confirm the installed OPatch version satisfies Oracle’s requirement.
For more informations: How To Download And Install The Latest OPatch
./opatch prereq CheckMinimumOPatchVersionOracle recommends OPatch 12.2.0.1.51 or later.
Check Patch Conflicts
Before installation run:
cd 39222882
opatch prereq CheckConflictAgainstOHWithDetail -ph ./Example output:
/u01/app/oracle/product/19.0.0/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -ph ./
Oracle Interim Patch Installer version 12.2.0.1.52
Copyright (c) 2026, Oracle Corporation. All rights reserved.
PREREQ session
Oracle Home : /u01/app/oracle/product/19.0.0
Central Inventory : /u01/app/oraInventory
from : /u01/app/oracle/product/19.0.0/oraInst.loc
OPatch version : 12.2.0.1.52
OUI version : 12.2.0.7.0
Log file location : /u01/app/oracle/product/19.0.0/cfgtoollogs/opatch/opatch2026-07-23_10-20-43AM_1.log
Invoking prereq "checkconflictagainstohwithdetail"
Prereq "checkConflictAgainstOHWithDetail" passed.
OPatch succeeded.This confirms the patch has no conflicts with the current Oracle Home.
Apply the OJVM Patch
cd <PATCH_TOP_DIR>/39222882
opatch applyDuring installation Oracle will request confirmation.
Do you want to proceed? y
Is the local system ready for patching? yExpected output:
/u01/app/oracle/product/19.0.0/OPatch/opatch apply
Oracle Interim Patch Installer version 12.2.0.1.52
Copyright (c) 2026, Oracle Corporation. All rights reserved.
Oracle Home : /u01/app/oracle/product/19.0.0
Central Inventory : /u01/app/oraInventory
from : /u01/app/oracle/product/19.0.0/oraInst.loc
OPatch version : 12.2.0.1.52
OUI version : 12.2.0.7.0
Log file location : /u01/app/oracle/product/19.0.0/cfgtoollogs/opatch/opatch2026-07-23_10-24-34AM_1.log
Verifying environment and performing prerequisite checks...
OPatch continues with these patches: 39222882
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')
Is the local system ready for patching? [y|n]
y
User Responded with: Y
Backing up files...
Applying interim patch '39222882' to OH '/u01/app/oracle/product/19.0.0'
Patching component oracle.javavm.server, 19.0.0.0.0...
Patching component oracle.javavm.server.core, 19.0.0.0.0...
Patching component oracle.rdbms.dbscripts, 19.0.0.0.0...
Patching component oracle.rdbms, 19.0.0.0.0...
Patching component oracle.javavm.client, 19.0.0.0.0...
Patch 39222882 successfully applied.
Log file location: /u01/app/oracle/product/19.0.0/cfgtoollogs/opatch/opatch2026-07-23_10-24-34AM_1.log
OPatch succeeded.The binary patch updates the Oracle Home with the new OJVM components.
Verify Binary Installation
opatch lspatchesExpected output:
39222882; OJVM RELEASE UPDATE: 19.32.0.0.260721
39472050; Database Release Update
29585399; OCW RELEASE UPDATEStart the Database
sqlplus "/as sysdba"
SQL*Plus: Release 19.0.0.0.0 - Production on Thu Jul 23 10:31:36 2026
Version 19.32.0.0.0
Copyright (c) 1982, 2026, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup;
ORACLE instance started.
Total System Global Area 2415916584 bytes
Fixed Size 9180712 bytes
Variable Size 754974720 bytes
Database Buffers 1644167168 bytes
Redo Buffers 7593984 bytes
Database mounted.
Database opened.
SQL>
SQL>
SQL> show pdbs;
CON_ID CON_NAME OPEN MODE RESTRICTED
---------- ------------------------------ ---------- ----------
2 PDB$SEED READ ONLY NO
3 PDB MOUNTED
SQL> alter pluggable database PDB open;
Pluggable database altered.
SQL> show pdbs;
CON_ID CON_NAME OPEN MODE RESTRICTED
---------- ------------------------------ ---------- ----------
2 PDB$SEED READ ONLY NO
3 PDB READ WRITE NO
SQL>
For Multitenant databases, ensure every PDB that should receive SQL updates is open before running Datapatch. Closed PDBs are skipped.
Run Datapatch Sanity Checks
Oracle recommends checking the environment before applying SQL changes.
datapatch -sanity_checksTypical checks include:
- Component status
- PDB violations
- Invalid objects
- Tablespace status
- Temp files
- Scheduler jobs
- Database Vault
- Oracle JVM
- GoldenGate triggers
Sample warnings that may appear:
- Dictionary statistics older than 7 days
- Scheduled jobs currently running
./datapatch -sanity_checks
SQL Patching sanity checks version 19.32.0.0.0 on Thu 23 Jul 2026 10:35:14 AM +0530
Copyright (c) 2021, 2026, Oracle. All rights reserved.
Log file for this invocation: /u01/app/oracle/cfgtoollogs/sqlpatch/sanity_checks_20260723_103514_16853/sanity_checks_20260723_103514_16853.log
Running checks
JSON report generated in /u01/app/oracle/cfgtoollogs/sqlpatch/sanity_checks_20260723_103514_16853/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 - WARNING
Patching the database without recent data dictionary statistics gathered may lead to performance issues.
Data dictionary statistics are older than 7 days.
Run the following queries to start gathering the dictionary statistics:
EXEC DBMS_STATS.GATHER_DICTIONARY_STATS;
EXEC DBMS_SYSTEM.GATHER_FIXED_OBJECTS_STATS;
Refer to MOS 457926.1 for more details.
PDB$SEED:
| LATEST | OPERATION | STATUS |
|-----------------+-------------------------+-----------|
| 14-OCT-25 11:46 | gather_dictionary_stats | COMPLETED |
|-----------------+-------------------------+-----------|
Check: Scheduled Jobs - WARNING
Execution of scheduler jobs while database patching is running may lead to failures and/or performance issues.
There are jobs currently running or scheduled to be executed during next hour.
If you experience Datapatch errors caused by locking in the database, consider patching the database when jobs are not running or preventing jobs from starting.
To check for jobs that are running or scheduled to run:
SELECT owner as schema_name, job_name, state, next_run_date
FROM sys.all_scheduler_jobs
WHERE state = 'RUNNING'
UNION
SELECT owner as schema_name, job_name, state, next_run_date
FROM sys.all_scheduler_jobs
WHERE state = 'SCHEDULED'
and cast(next_run_date as date) > sysdate
and cast(next_run_date as date) < sysdate + 1/24;
PDB:
| SCHEMA_NAME | JOB_NAME | STATE | NEXT_RUN_DATE |
|-------------+-----------------------------+-----------+-------------------------------------|
| SYS | OBJNUM_REUSE_MAINTAIN_JOB$$ | SCHEDULED | 23-JUL-26 11.32.34.981210 AM +05:30 |
|-------------+-----------------------------+-----------+-------------------------------------|
| SYS | ORA$AT_OS_OPT_SY_1 | RUNNING | |
|-------------+-----------------------------+-----------+-------------------------------------|
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
Refer to MOS Note 2975965.1 and debug log
/u01/app/oracle/cfgtoollogs/sqlpatch/sanity_checks_20260723_103514_16853/sanity_checks_debug_20260723_103514_16853.log
SQL Patching sanity checks completed on Thu 23 Jul 2026 10:35:26 AM +0530These warnings are informational and should be reviewed before continuing.
Execute Datapatch
datapatch -verboseOracle installs the SQL portion into:
- CDB$ROOT
- PDB$SEED
- All open PDBs
./datapatch -verbose
SQL Patching tool version 19.32.0.0.0 Production on Thu Jul 23 10:35:38 2026
Copyright (c) 2012, 2026, Oracle. All rights reserved.
Log file for this invocation: /u01/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_16933_2026_07_23_10_35_38/sqlpatch_invocation.log
Connecting to database...OK
Gathering database info...done
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 interim SQL patches:
Interim patch 39222882 (OJVM RELEASE UPDATE: 19.32.0.0.260721 (39222882)):
Binary registry: Installed
PDB CDB$ROOT: Not installed
PDB PDB: Not installed
PDB PDB$SEED: Not installed
Current state of release update SQL patches:
Binary registry:
19.32.0.0.0 Release_Update 260705220710: Installed
PDB CDB$ROOT:
Applied 19.32.0.0.0 Release_Update 260705220710 successfully on 23-JUL-26 09.57.10.179059 AM
PDB PDB:
Applied 19.32.0.0.0 Release_Update 260705220710 successfully on 23-JUL-26 10.01.23.098763 AM
PDB PDB$SEED:
Applied 19.32.0.0.0 Release_Update 260705220710 successfully on 23-JUL-26 10.01.23.088584 AM
Adding patches to installation queue and performing prereq checks...done
Installation queue:
For the following PDBs: CDB$ROOT PDB$SEED PDB
No interim patches need to be rolled back
No release update patches need to be installed
The following interim patches will be applied:
39222882 (OJVM RELEASE UPDATE: 19.32.0.0.260721 (39222882))
Installing patches...
Patch installation complete. Total patches installed: 3
Validating logfiles...done
Patch 39222882 apply (pdb CDB$ROOT): SUCCESS
logfile: /u01/app/oracle/cfgtoollogs/sqlpatch/39222882/28830205/39222882_apply_CDB_CDBROOT_2026Jul23_10_37_48.log (no errors)
Patch 39222882 apply (pdb PDB$SEED): SUCCESS
logfile: /u01/app/oracle/cfgtoollogs/sqlpatch/39222882/28830205/39222882_apply_CDB_PDBSEED_2026Jul23_10_39_36.log (no errors)
Patch 39222882 apply (pdb PDB): SUCCESS
logfile: /u01/app/oracle/cfgtoollogs/sqlpatch/39222882/28830205/39222882_apply_CDB_PDB_2026Jul23_10_39_36.log (no errors)
SQL Patching tool complete on Thu Jul 23 10:40:44 2026
[oracle@prod OPatch]$
Example:
Patch installation complete.
Patch 39222882 apply (CDB$ROOT): SUCCESS
Patch 39222882 apply (PDB$SEED): SUCCESS
Patch 39222882 apply (PDB): SUCCESSRemember: Datapatch only updates open PDBs. If a PDB is closed during execution, open it later and rerun Datapatch.
Verify SQL Patch
SET LINESIZE 200
COL description FORMAT A60
COL status FORMAT A10
SELECT patch_id,
patch_type,
action_time,
description,
status
FROM dba_registry_sqlpatch
WHERE UPPER(description) LIKE '%OJVM%'
ORDER BY action_time DESC;Example:
PATCH_ID DESCRIPTION STATUS
39222882 OJVM RELEASE UPDATE 19.32.0.0.260721 SUCCESS
A SUCCESS status confirms the SQL changes were applied successfully.
Recommended Post-Installation Tasks
Oracle recommends the following after patching:
EXEC DBMS_STATS.GATHER_DICTIONARY_STATS;
EXEC DBMS_SYSTEM.GATHER_FIXED_OBJECTS_STATS;Recompile invalid objects if necessary:
@?/rdbms/admin/utlrp.sql
Session altered.
TIMESTAMP
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_BGN 2026-07-23 11:00:44
DOC> The following PL/SQL block invokes UTL_RECOMP to recompile invalid
DOC> objects in the database. Recompilation time is proportional to the
DOC> number of invalid objects in the database, so this command may take
DOC> a long time to execute on a database with a large number of invalid
DOC> objects.
DOC>
DOC> Use the following queries to track recompilation progress:
DOC>
DOC> 1. Query returning the number of invalid objects remaining. This
DOC> number should decrease with time.
DOC> SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
DOC>
DOC> 2. Query returning the number of objects compiled so far. This number
DOC> should increase with time.
DOC> SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
DOC>
DOC> This script automatically chooses serial or parallel recompilation
DOC> based on the number of CPUs available (parameter cpu_count) multiplied
DOC> by the number of threads per CPU (parameter parallel_threads_per_cpu).
DOC> On RAC, this number is added across all RAC nodes.
DOC>
DOC> UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel
DOC> recompilation. Jobs are created without instance affinity so that they
DOC> can migrate across RAC nodes. Use the following queries to verify
DOC> whether UTL_RECOMP jobs are being created and run correctly:
DOC>
DOC> 1. Query showing jobs created by UTL_RECOMP
DOC> SELECT job_name FROM dba_scheduler_jobs
DOC> WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>
DOC> 2. Query showing UTL_RECOMP jobs that are running
DOC> SELECT job_name FROM dba_scheduler_running_jobs
DOC> WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>#
PL/SQL procedure successfully completed.
TIMESTAMP
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_END 2026-07-23 11:01:18
DOC> The following query reports the number of invalid objects.
DOC>
DOC> If the number is higher than expected, please examine the error
DOC> messages reported with each object (using SHOW ERRORS) to see if they
DOC> point to system misconfiguration or resource constraints that must be
DOC> fixed before attempting to recompile these objects.
DOC>#
OBJECTS WITH ERRORS
-------------------
0
DOC> The following query reports the number of exceptions caught during
DOC> recompilation. If this number is non-zero, please query the error
DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
DOC> are due to misconfiguration or resource constraints that must be
DOC> fixed before objects can compile successfully.
DOC> Note: Typical compilation errors (due to coding errors) are not
DOC> logged into this table: they go into DBA_ERRORS instead.
DOC>#
ERRORS DURING RECOMPILATION
---------------------------
0
Function created.
PL/SQL procedure successfully completed.
Function dropped.
PL/SQL procedure successfully completed.
These steps help optimize performance and return invalid packages to a valid state.
Best Practices
- Always install the matching Database RU before applying the OJVM RU.
- Perform a full RMAN backup before patching.
- Run
opatch prereqbefore every installation. - Ensure all required PDBs are open before Datapatch.
- Review Datapatch logs after completion.
- Verify
DBA_REGISTRY_SQLPATCHreports SUCCESS. - Test applications after patching before returning the system to production.
Conclusion
Patch 39222882 (Oracle JavaVM Component Release Update 19.32.0.0.260721) is the July 2026 OJVM security update for Oracle Database 19c. Applying it alongside Database Release Update 19.32 ensures your Oracle Java Virtual Machine remains current with the latest security fixes and cumulative updates. Following the standard sequence—conflict check, binary patching, opening PDBs, running Datapatch, and verifying the SQL registry—provides a reliable and repeatable patching process.
