# 🩹 EBS Patches

Patch inventory across all Oracle Homes — FMW, WLS, 10.1.2, Apps, AD/TXK, ATG/PCU, ETCC

🔌

EBS Patches require an EBS-enabled connection (is_ebs = true).
Select an EBS connection or use the DB Ops → Patches tab for RDBMS patch analysis.

⚠ FMW home mismatch detected
In oracle_common — missing from Oracle_Home
In Oracle_Home — missing from oracle_common
✅ FMW homes are in sync — all patches match between oracle_common and Oracle_Home
Run `opatch lsinventory` on both FMW homes to detect patch mismatches and check WLS CPU currency. Runs via the app-tier agent (no SSH required); falls back to an SSH target if no agent is online.
DB ORACLE_HOME
?
The RDBMS Oracle Home (e.g. `/u01/install/APPS/19.0.0`). Contains the Oracle Database binaries. Patched via OPatch with Release Updates (RU/RUR) and CPU patches. Separate from the FMW homes — DB patching requires database shutdown.
🗄️
DB ORACLE_HOME $ORACLE_HOME
Oracle Database binaries — patched with RU/RUR and CPU patches
The RDBMS Oracle Home (typically `/u01/install/APPS/19.0.0` for a 19c EBS instance). Contains the Oracle DB kernel. CPU/RU patches applied here require database shutdown and datapatch.
$ORACLE_HOME/OPatch/opatch lsinventory -oh $ORACLE_HOME
Output
FMW oracle_common
?
The shared FMW infrastructure home (e.g. `/u01/install/APPS/fs1/FMW_Home/oracle_common`). Contains OPSS (security framework), MDS (metadata services), and JRF (Java Required Files). All FMW components depend on this home. Patches here must match Oracle_Home to avoid JRF/OPSS version skew.
🗂️
oracle_common Shared FMW
OPSS, MDS, JRF — shared by all FMW components
The `oracle_common` home under `$FMW_HOME` is the shared FMW infrastructure home. Patches here cover OPSS security framework, MDS metadata services, and JRF (Java Required Files). Must be in sync with Oracle_Home — a mismatch causes WLS startup failures.
$FMW_HOME/oracle_common/OPatch/opatch lsinventory -oh $FMW_HOME/oracle_common
Output
FMW WLS Home
?
The WebLogic Server home. EBS 12.2 ships WLS 10.3.6 at `$FMW_HOME/wlserver_10.3` (patched via BSU / Smart Update). Sites that took Oracle's optional upgrade to WLS 12.2.1.x use `$FMW_HOME/Oracle_Home` (patched via OPatch). Must be kept in sync with oracle_common. Under online patching (ADOP), fs1 and fs2 have separate FMW homes.
⚙️
WLS Home WLS
WebLogic Server binaries — WLS PSUs and JVM patches
The EBS 12.2 default uses WLS 10.3.6 at `$FMW_HOME/wlserver_10.3` (BSU-patched — see the WLS tab's BSU report). Sites that upgraded to WLS 12.2.1.x use `$FMW_HOME/Oracle_Home` (OPatch). The Run button probes both. Silent failure mode: on the OPatch stack, a patch applied to oracle_common but missing here (or vice versa) causes JRF dependency mismatches that can prevent WLS from starting after an ADOP cutover.
# EBS 12.2 default — WLS 10.3.6 (BSU-patched; see WLS → BSU report): $FMW_HOME/wlserver_10.3 # Upgraded stack — WLS 12.2.1.x (OPatch): $FMW_HOME/Oracle_Home/OPatch/opatch lsinventory -oh $FMW_HOME/Oracle_Home
Output
webtier (OHS)
?
The Oracle HTTP Server home (e.g. `/u01/install/APPS/fs1/FMW_Home/webtier`). Contains OHS (Apache-based HTTP server) and `mod_wl_ohs` — the WLS proxy module. Patches here fix web-tier TLS/SSL vulnerabilities. Not directly involved in the oracle_common ↔ Oracle_Home mismatch — checked separately.
🌐
webtier OHS / mod_wl
Oracle HTTP Server, mod_wl_ohs, SSL configuration
The `webtier` home contains Oracle HTTP Server (OHS) and `mod_wl_ohs`. This is distinct from Oracle_Home/WLS — it is the HTTP layer in front of WLS, not the WLS server itself.
$FMW_HOME/webtier/OPatch/opatch lsinventory -oh $FMW_HOME/webtier
Output
WebLogic Server (WLS) — $FMW_HOME/wlserver
⚙️
WebLogic Server $FMW_HOME/wlserver
12.2.1.3+: OPatch · Pre-12.2.1.3: BSU (BEA Smart Update)
WLS patching depends on version: 12.2.1.3 and later use OPatch; older versions use BSU (`bsu.sh -report`).
OPatch (12.2.1.3+)
$FMW_HOME/wlserver/OPatch/opatch lsinventory -oh $FMW_HOME/wlserver
Output
BSU (Pre-12.2.1.3)
$MW_HOME/utils/bsu/bsu.sh -report
Output
10.1.2 Oracle Home — Forms & Reports (legacy tech stack)
📝
Forms 10.1.2 / Reports 10.1.2 Legacy
Still critical in EBS 12.2 — Forms 10.1.2.x and Reports 10.1.2.x
The 10.1.2 tech stack is legacy but still ships in EBS 12.2. This Oracle Home contains Forms and Reports. Patches are applied via OPatch against the 10.1.2 home, separate from the FMW tier.
$ORACLE_HOME/OPatch/opatch lsinventory -detail
⚠ Substitute `$ORACLE_HOME` with the actual 10.1.2 Oracle Home path (not the DB home). On EBS 12.2 dual-filesystem this is under the run edition, e.g. `/u01/install/APPS/fs1/EBSapps/10.1.2`
Output
Apps Patches — applied via adpatch (pre-R12.2) or adop (R12.2 online patching)
🔌

### Select a connection to load Apps patch history

Queries AD_APPLIED_PATCHES and AD_BUGS for the applied patch record.

AD/TXK Codelevels — from AD_TRACKABLE_ENTITIES
🔌

### Select a connection to load AD/TXK codelevels

Queries AD_TRACKABLE_ENTITIES for AD and TXK codelevel strings.

ATG/PCU — ATG_PF rollup and Platform Cumulative Update status
🔌

### Select a connection to load ATG/PCU status

Queries ATG_PF patch level and last PCU applied from AD_APPLIED_PATCHES.

ATG_PF Patch Level — SSH verification
Verify ATG_PF codelevel from the application tier using the maintained FMW version file.
cat $FMW_HOME/oracle_common/common/templates/jrf/version.properties | grep "oracle.fmw.patchversion"
ETCC — Enterprise Technology Codelevel Checker
ETCC validates that all technology stack components meet Oracle's minimum codelevel requirements. Run both scripts for full compliance. See MOS Doc 1594274.1 for ETCC documentation.
🗄️
checkDBpatch.sh DB Tier
Database-tier technology compliance check
Validates the RDBMS Oracle Home against Oracle's minimum codelevel requirements for EBS compatibility. Run as oracle OS user from the DB tier.
$ETCC_HOME/checkDBpatch.sh
Output
🏗️
checkMTpatch.sh Middle Tier
Application middle-tier technology compliance check
Validates the FMW, WLS, and 10.1.2 technology stack homes against Oracle's minimum codelevel requirements. Run as applmgr OS user from the apps tier.
$ETCC_HOME/checkMTpatch.sh
Output
Need help? support@tunevault.app