Patching Oracle Access Manager 14c with the October 2026 IDM Stack Patch Bundle (SPBAT Walkthrough)
Oracle's recommended way to patch Oracle Access Manager (OAM) 14c is the IDM Stack Patch Bundle (SPB), applied with the SPB automation tool, SPBAT. This post walks through applying the October 2026 SPB (14.1.2.1.261008,
Oracle's recommended way to patch Oracle Access Manager (OAM) 14c is the IDM Stack Patch Bundle (SPB), applied with the SPB automation tool, SPBAT. This post walks through applying the October 2026 SPB (14.1.2.1.261008, patch 40131416) to an OAM 14.1.2.1 home. A second post covers Oracle Internet Directory (OID).
Why the SPB and not individual patches
Oracle's support documentation recommends applying the latest IDM Stack Patch Bundle to OAM. The bundle collects the latest mandatory patches for the whole IDM 14.1.2.1 stack, including the WebLogic and Fusion Middleware layers underneath OAM. 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 home had 13.9.4.2.24.
- Patch as the OS user that installed OAM. SPBAT checks that the patching user matches the install user.
- Set
ORACLE_HOMEto the OAM 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 inventory showed IDM Stack Patch Bundle 14.1.2.1.260906, applied on 7 October 2026.
Figure 1. Patch level before the update: IDM Stack Patch Bundle 14.1.2.1.260906.
Step 2: Check the OPatch version
cd $ORACLE_HOME/OPatch
./opatch version
bash-4.2$ ./opatch version
OPatch Version: 13.9.4.2.17
OPatch succeeded.
OPatch 13.9.4.2.24 in the OAM 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. If you run ./spbat.sh from the top of the bundle, you get "No such file or directory".
cd /u02/stage/CPUOCTPatch/IDM_SPB_14.1.2.1.261008/tools/spbat/generic/SPBAT
./spbat.sh -type OAM -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 2. PreStop phase. The first attempt from the bundle's top directory failed. The second, from the SPBAT directory, completed successfully.
Step 4: Stop the services and run the Downtime phase
Stop AdminServer, oam_policy_mgr1 and oam_server1 with your usual stop scripts, then run:
./spbat.sh -type OAM -phase Downtime -mw_home $ORACLE_HOME -spb_download_dir /u02/stage/CPUOCTPatch/IDM_SPB_14.1.2.1.261008
Figure 3. Downtime phase completed successfully.
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 same run applied the OAM bundle patch 14.1.2.1.260928 and the WebLogic patch set update 14.1.2.0.260922. 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.
Figure 4. Patch level after the update: the SPB 14.1.2.1.261008 entry, applied on 23 October 2026.
Step 6: Clear the cache and tmp directories
The README says to clear the cache, tmp and stage directories under each server directory before starting the servers. It lists no post-install actions after startup. I renamed the directories instead of deleting them, which leaves a copy to fall back on:
cd $DOMAIN_HOME/servers/AdminServer
mv cache cache_23OCT2026
mv tmp tmp_23OCT2026
I repeated this for oam_policy_mgr1 and oam_server1. Delete the renamed copies once you are happy with the result, since they use disk space.
Figure 5. Renaming the cache and tmp directories under all three server directories.
Step 7: Start the services and run PostStart
Start AdminServer and the managed servers, then run:
./spbat.sh -type OAM -phase PostStart -mw_home $ORACLE_HOME -spb_download_dir /u02/stage/CPUOCTPatch/IDM_SPB_14.1.2.1.261008
PostStart phase completed successfully.
Step 8: Verify the servers
In the WebLogic Remote Console, all three servers showed RUNNING with health ok. The README also says to restart and verify the environment and URLs after patching, so I'd add a real login through OAM to this check.
Figure 6. AdminServer, oam_policy_mgr1 and oam_server1 all RUNNING with health ok.
What I learned
- Patch with the SPB, not individual CPU patches. It keeps the stack on a combination Oracle has certified together.
-
Run SPBAT from its own directory. The top of the bundle doesn't contain
spbat.sh. - Rename instead of delete. It costs a little disk space and gives you a way back.
- Use the status report command. It lets you watch a long phase from a second terminal.
References
- My Oracle Support: KA754, Stack Patch Bundle for Oracle Identity Management Products
- My Oracle Support: PALRT2206, OAM Bundle Patch Release History
- 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.
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.




