How do you check whether a list of bug fixes is included in an RU?

Today, a customer sent me a workaround for the misbehavior they were seeing with the Conflict Checker Tool in the Support portal. They use oradiff to check whether a given fix they have a one-off right now is included in a future Release Update (RU). This works nicely, but I have a recommendation for an even easier check (thanks Rodrigo!).

Photo by Charlotte Wurch on Unsplash

Ask ORAdiff …

I am using this specific customer case as an example. Of course, this will work with your list of fixes as well. Let’s assume that this is the list of one-off patches you have applied to your 23.9.0 database home right now:

37984197;MERGE FAILS WITH ORA-600 [QKSWCCRW 1] WITH FIX 37065327 (19.26 AND ABOVE)
38647204;DIAGNOSTIC PATCH FOR BUG 38154676
38101059;ET23.1ET_UPF - TRC - CTCDA_DELETE_APPLY - ORA-7445 [CTCDA_DELETE_APPLY]
38154568;AIM ORA-600 [IPC ASSERT] - KSIPC_IPCOR_ASSERTCB
37884169;FA 2304 HITTING ORA-600 [KDLFERROR597  UNKNOWN STATUS]  IN FS_IC_GRC AND CRMSVC WORKLOAD
36564549;IMPROVE DIAGNOSTICS FOR ORA 600 [KTSPGSB_RBK-OPC]
38526910;MERGE ON DATABASE RU 23.9.0.25.07 OF 37828476 37858720
37450593;SELECTING FROM DBA_FREE_SPACE TAKES OVER 10 MINUTES TO 3 HOURS TO COMPLETE
36378251;EXCESSIVE TRACING IN SERVER MANAGEABILITY AREA UID 11225
38258371;MERGE ON DATABASE RU 23.9.0.25.07 OF 37583325 37897658
37768542;REMOVE ASSERT ORA-600 [KTATMKREF-RS] WITH  ADG TEMP TABLE REF BASED CLEANUP IS STABLE IN 19C
37393792;ORA-12850 REPORTED AFTER APPLYING DBRU ON FIRST NODE
38171540;DATAPUMP BUNDLE PATCH 23.9.0.25.07
36828756;ORA-01017  INVALID USERNAME/PASSWORD; LOGON DENIED ON MAA WITH ZDLRA ON 21C DATABASES

I use my editor to cut out the bug numbers, and separate them by commas:

37984197,38647204,38101059,38154568,37884169,36564549,38526910,37450593,36378251,38258371,37768542,37393792,38171540,36828756

I am pretty certain somebody will paste a quick awk or vi hack below on how to do this quicker. Or, I could ask my AI tool 😉

In ORAdiff I choose now the newest RU for Oracle AI Database 26ai, 23.26.1.0 since I am going to check which of the above fixes are included in 23.26.1, and which aren’t.

List Mode is the secret sauce

Once you display the 23.26.1 fixes, you need to toggle the switch for LIST mode as indicated in the picture below:

Toggle LIST mode ON 

Now you see the list of all 11,000+ fixes included in 23.26.1.

As next step, you are going to add a FILTER. Click the “Actions” button and choose “Filter”.

Click on “Actions” and choose “Filter”

Add an IN Filter

Then add a “IN” Filter on the “bug ID” column and paste in your list of fixes, in my case the list I did compile above.

Add a “IN” Filter on column “Bug ID” and paste your comma-separated list of fixes

Hit “Apply“, and then you are going to see the list of fixes being included in the given Release Update. The remaining ones not on this list are the ones you need to request now from Oracle Support or download from MOS via AutoUpgrade.

These fixes are included in Release Update 23.26.1. 

These are the 7 fixes which aren’t included in RU 23.26.1.

38647204,37884169,36564549,38526910,38258371,37393792,38171540

I would now run an AutoUpgrade session to check if AutoUpgrade is able to download them as one-off fixes already on top of 23.26.1.

global.global_log_dir=/home/oracle/autoupgrade/log
global.keystore=/home/oracle/autoupgrade/keystore
global.folder=/home/oracle/patch-repository

patch1.patch=RU,DPBP,OPATCH,JDK,OCW,38647204,37884169,36564549,38526910,38258371,37393792,38171540
patch1.target_version=23
patch1.platform=LINUX.X64

Further Links and Information

• Download and install Oracle AI Database 26ai with AutoUpgrade
• oradiff.oracle.com

–Mike