Oracle Database Appliance

ODA Patch Downloads

The exact My Oracle Support patches to download for each Oracle Database Appliance release, 19.29 through 19.32. Come back to this site for future updates.

How ODA patching downloads work

1 Server Patch

One file for the whole system: Oracle Linux, the DCS stack, Appliance Manager, ILOM, BIOS, firmware, HMP, JRE, ASR, IPMI and NIC patches. The patch number changes every release.

2 GI clone

The Grid Infrastructure image. ODA patches out of place, so Grid Infrastructure arrives as an image rather than an in-place patch. Patch 30403673 across these releases.

3 DB clone

The database image, patch 30403662. Download one per Oracle Database version you run, so 19c and 18c homes need two DB clones.

Use only these ODA patches. Do not apply generic Oracle Grid Infrastructure or Oracle Linux patches, individual firmware patches, or OPatch. Anything outside the ODA bundle desyncs the metadata and breaks future patching.

Quick reference

ReleaseReleasedServer PatchGI cloneDB clone
19.29.0.0.0Oct 2025384272513040367330403662
19.30.0.0.0Jan 2026387760743040367330403662
19.31.0.0.0Apr 2026392338783040367330403662
19.32.0.0.0Jul 2026396626303040367330403662

Release dates track the quarterly Oracle Database Release Update each bundle carries (October, January, April, July). Confirm the exact build date in the release’s My Oracle Support entry.

By release

19.2919.29.0.0.0
ReleasedOctober 2025
Server Patch38427251
GI clone30403673
DB clone30403662
Server fileoda-sm-19.29.0.0.0-<date>-server.zip
19.3019.30.0.0.0
ReleasedJanuary 2026
Server Patch38776074
GI clone30403673
DB clone30403662
Server fileoda-sm-19.30.0.0.0-<date>-server.zip
19.3119.31.0.0.0
ReleasedApril 2026
Server Patch39233878
GI clone30403673
DB clone30403662
Server fileoda-sm-19.31.0.0.0-<date>-server.zip
19.3219.32.0.0.0
ReleasedJuly 2026
Server Patch39662630
GI clone30403673
DB clone30403662
Server fileoda-sm-19.32.0.0.0-<date>-server.zip

Getting the files onto the appliance

Download from My Oracle Support

In MOS, open Patches & Updates, find the patch (for example 39662630), click Download, then Download wget Script. The script needs a MOS access token: while signed in to MOS, open updates.oracle.com/Orion/GenToken/get_token and copy the token, then pass it with -T <tokenfile>. Run the script on the appliance, or download on your workstation and copy the zip over with scp. The token is time-limited, and one token covers all three patches.

Unzip before you stage

The p…zip you download is only a wrapper (a README plus the real file). Unzip it first and stage the inner file, not the p…zip. This is the step most people miss.

# the download is a wrapper — unzip it to get the file update-repository wants
unzip p39662630_1932000_Linux-x86-64.zip     # -> oda-sm-19.32.0.0.0-<date>-server.zip
unzip p30403673_1932020_Linux-x86-64.zip     # -> odacli-dcs-…-GI-…zip
unzip p30403662_1932020_Linux-x86-64.zip     # -> odacli-dcs-…-DB-…zip

Patching order on the appliance

Stage the server patch, update the DCS framework, then stage the clones, precheck, and apply. Run update-dcscomponents on the first node of a High Availability system.

# 1. stage the server patch
odacli update-repository -f /tmp/oda-sm-19.32.0.0.0-<date>-server.zip
# 2. update the DCS framework (first HA node)
odacli update-dcsadmin -v 19.32.0.0.0
odacli update-dcscomponents -v 19.32.0.0.0
# 3. stage the GI and DB clone images
odacli update-repository -f /tmp/odacli-dcs-19.32.0.0.0-<date>-GI-19.32.0.0.0.zip
odacli update-repository -f /tmp/odacli-dcs-19.32.0.0.0-<date>-DB-19.32.0.0.0.zip
# 4. precheck, then apply (-nr keeps the node from rebooting)
odacli create-prepatchreport -sc -v 19.32.0.0.0
odacli update-servercomponents -nr -v 19.32.0.0.0

Oracle AI Database 26ai (DB Systems)

26ai runs as a DB System (KVM), not on the bare-metal ODACLI/DCS stack that your 19c databases use. Provisioning or patching a 26ai DB System uses its own clone set (base version 23.26.3.x), downloaded separately from the 19c bare-metal clones.

26ai component (for DB Systems)MOS patch
Database clone36524642
GI clone36524627
DB System KVM image (deploy template)36524660

Notes

Patch numbers

The Server Patch number is different for every release. The GI clone (30403673) and DB clone (30403662) are long-lived patch IDs that Oracle refreshes in place, so the same number gives you the current image.

Confirm against the Release Notes

Each release’s Release Notes list the exact component versions in the bundle and the supported update paths. Treat them as the source of truth before you patch.

Source: Oracle Database Appliance Deployment and User’s Guide, Patching chapter. docs.oracle.com → Oracle Database Appliance