This post applies the October 2026 IDM Stack Patch Bundle (SPB) 14.1.2.1.261008, patch 40131416, to an Oracle Internet Directory (OID) 14.1.2.1 home using SPBAT, the SPB automation tool. It is the companion to my Oracle Access Manager patching post: [link to your OAM post]. My first Downtime run failed with an OPatch error, which I cover in a separate post: [link to the error 137 post].
Why the SPB and not individual patches
Oracle's support documentation recommends applying the latest IDM Stack Patch Bundle to IDM 14.1.2.1 environments. The bundle collects the latest mandatory patches for the whole stack, including the WebLogic and Fusion Middleware layers underneath OID. Picking individual CPU patches by hand risks drifting away from the combination Oracle has certified together. My Oracle Support article KA754 tracks the latest bundle.
Before you start
- Download and unzip the SPB into a stage directory. Mine was
/u02/stage/CPUOCTPatch/IDM_SPB_14.1.2.1.261008. - Check OPatch. The README asks for 13.9.4.2.17 or higher, and my OID home had 13.9.4.2.24.
- Patch as the OS user that installed OID. SPBAT checks that the patching user matches the install user.
- Set
ORACLE_HOMEto the OID Oracle home. - Back up the Oracle home, the domain home and the schema database first.
Step 1: Record the current patch level
$ORACLE_HOME/OPatch/opatch lsinventory | grep -E "Patch|Unique Patch ID"
Before the update, the OID home showed IDM Stack Patch Bundle 14.1.2.1.260906, applied on 6 October 2026, with OID bundle patch 14.1.2.1.0 (ID:260814.2147).
Figure 1. Patch level of the OID home before the update.
Step 2: Check the OPatch version
cd $ORACLE_HOME/OPatch
./opatch version
Figure 2. OPatch 13.9.4.2.24 in the OID Oracle home, above the minimum the README asks for.
Step 3: Run the PreStop phase
SPBAT lives under the bundle's tools/spbat/generic/SPBAT directory. Run it from there, not from the top of the bundle.
cd /u02/stage/CPUOCTPatch/IDM_SPB_14.1.2.1.261008/tools/spbat/generic/SPBAT
./spbat.sh -type OID -phase PreStop -mw_home $ORACLE_HOME -spb_download_dir /u02/stage/CPUOCTPatch/IDM_SPB_14.1.2.1.261008
SPBAT prints the log location and a -status report command you can run from a second terminal. Keep the first terminal open while the phase runs.
Figure 3. PreStop phase completed successfully.
Step 4: Stop the OID components and WebLogic servers, then run Downtime
Stop the OID components (oid1 and oid2), the OID WebLogic server and AdminServer with your usual stop scripts, then run:
./spbat.sh -type OID -phase Downtime -mw_home $ORACLE_HOME -spb_download_dir /u02/stage/CPUOCTPatch/IDM_SPB_14.1.2.1.261008
My first run of this phase failed with OPatch error code 137. After applying the fix described in [link to the error 137 post], the rerun completed successfully.
Figure 4. The Downtime phase completed successfully after the rerun.
Step 5: Verify the patch level
Run the same lsinventory command again.
$ORACLE_HOME/OPatch/opatch lsinventory | grep -E "Patch|Unique Patch ID"
The new bundle appears as inventory entry 40131551, with a description naming SPB 14.1.2.1.261008 (patch 40131416). That is the entry to look for. The OID bundle patch moved to 14.1.2.1.0 (ID:260911.0510), and OPatch itself moved from 13.9.4.2.24 to 13.9.4.2.25 during the run. The bundle ships its own opatch folder, which is likely why.
The "Picked up _JAVA_OPTIONS" line at the top of the output comes from the fix in the error 137 post. That post also explains how to clear it.
Figure 5. Patch level after the update: the SPB 14.1.2.1.261008 entry, applied on 23 October 2026.
Step 6: Start the OID components
The README lists no post-install configuration steps for OID, so after the Downtime phase the next step is starting the services. I started the two OID system components through Node Manager:
$DOMAIN_HOME/bin/startComponent.sh oid1
$DOMAIN_HOME/bin/startComponent.sh oid2
Figure 6. Starting oid1 and oid2 with startComponent.sh through Node Manager.
Step 7: Run the PostStart phase
./spbat.sh -type OID -phase PostStart -mw_home $ORACLE_HOME -spb_download_dir /u02/stage/CPUOCTPatch/IDM_SPB_14.1.2.1.261008
Figure 7. PostStart phase completed successfully.
Step 8: Verify the environment
I checked the environment in two places. The WebLogic Remote Console showed AdminServer and wls_ods1 RUNNING with health ok.
Figure 8. WebLogic Remote Console: AdminServer and wls_ods1 RUNNING with health ok.
Fusion Middleware Control showed the two WebLogic servers Running with health OK, and the oid1 and oid2 components registered under Identity and Access.
And there is no Post installation steps for OID.
What I learned
- Patch with the SPB, not individual CPU patches. It keeps the stack on a combination Oracle has certified together.
- OID's README lists no post-install configuration. After the Downtime phase, starting the services and running PostStart was all that was left.
-
OID components start through Node Manager.
startComponent.shhandled bothoid1andoid2. - Check more than one place. The Remote Console and Fusion Middleware Control each showed the environment from a different angle.
- If a phase fails, read the exit code first. Mine is explained in the error 137 post.
References
- My Oracle Support: KA754, Stack Patch Bundle for Oracle Identity Management Products
- Patch 40131416, IDM Stack Patch Bundle 14.1.2.1.261008
Kumaran Murugan is an Oracle Apps DBA and OCI Cloud Administrator with 5+ years of experience in Oracle E-Business Suite, database migrations, and OCI infrastructure. Connect on LinkedIn.









Top comments (0)