Sample EBS App Tier Health Report

TuneVault AI Summary GPT-4o powered

This EBS 12.2 application tier has 2 critical findings. Workflow Notification Mailer is in DEACTIVATED_SYSTEM state — 1,044 notifications are stuck in queue and 147 workflow errors are accumulating. APPS schema has 734 invalid objects which may indicate a failed patch application or incomplete compile step. All other components are healthy: Apache/OHS, OPMN, WebLogic AdminServer, Node Manager, Forms, OACore, and Concurrent Manager (21/21 worker processes at target).

⚡

Top Action Now

Restart Workflow Notification Mailer via OAM: System Admin → Oracle Applications Manager → Workflow → Service Components → Activate. Then run @$AD_TOP/sql/adcompsc.sql as APPS to recompile invalid objects.

Check Results 🔴 2 critical ⚠ 2 warnings ✓ 11 passed

🔴 Critical Workflow Notification Mailer — DEACTIVATED_SYSTEM

1,044 pending ▾

The Workflow Notification Mailer has been deactivated by the system — typically caused by repeated SMTP connection failures. 1,044 notifications are queued but undeliverable, and 147 workflow errors are accumulating.

Resolution steps:
1. OAM: System Admin → Oracle Applications Manager → Workflow → Service Components
2. Select Workflow Notification Mailer → Actions → Start
3. If still DEACTIVATED_SYSTEM: Stop → Start (2-step reset)
4. Verify OUTBOUND_SERVER SMTP connectivity in mailer configuration

-- Reset component status and restart (run as APPS): UPDATE fnd_svc_components SET component_status = 'STOPPED', component_status_info = NULL WHERE component_type = 'WF_MAILER'; COMMIT; -- Then use OAM to Start, or via PL/SQL: DECLARE l_retcode VARCHAR2(100); l_errbuf VARCHAR2(4000); l_cid NUMBER; BEGIN SELECT component_id INTO l_cid FROM fnd_svc_components WHERE component_type = 'WF_MAILER' AND ROWNUM = 1; fnd_svc_component.start_component(l_cid, l_retcode, l_errbuf); DBMS_OUTPUT.PUT_LINE('retcode: ' || l_retcode); END; /

🔴 Critical APPS Schema — 734 Invalid Objects

734 objects ▾

734 objects in the APPS schema are INVALID. This typically indicates a failed or incomplete patch application, or a DDL change to a base object that invalidated dependent objects. Invalid objects cause ORA-04063 errors at runtime when the affected code path is executed.

-- Check count by type: SELECT object_type, COUNT(*) cnt FROM dba_objects WHERE owner = 'APPS' AND status = 'INVALID' GROUP BY object_type ORDER BY cnt DESC; -- Recompile via AD utility (as applmgr): -- sqlplus apps/<pwd> @$AD_TOP/sql/adcompsc.sql APPS -- Or via DBMS_UTILITY: EXEC DBMS_UTILITY.COMPILE_SCHEMA('APPS', FALSE);

⚠ Warning Optional Managed Servers — Not Running

OAFM not started ▾

⚠ Warning DB Tablespace — APPS_TS_TX_DATA at 81.7%

autoextend OFF ▾

EBS App Tier Check Results

Check	Status	Detail
Apache / OHS	RUNNING	adapcctl.sh status — OK, PID 12481
OPMN	RUNNING	adopmnctl.sh status — alive (PID 12523)
Apps Listener (adalnctl)	RUNNING	lsnrctl TCP status — LISTENER: ready
Node Manager	RUNNING	adnodemgrctl.sh status — running (PID 13012)
WLS AdminServer	RUNNING	WLST domain runtime — AdminServer: RUNNING
OACore Managed Servers	RUNNING	oacore_server1 RUNNING, oacore_server2 RUNNING
Forms Managed Servers	RUNNING	forms_server1 RUNNING, forms_server2 RUNNING
Concurrent Manager (adcmctl)	RUNNING	21/21 worker processes at target, 1 pending request
Workflow Notification Mailer	DEACTIVATED_SYSTEM	147 errors, 1,044 pending — restart required

EBS DB Health (from paired DB connection)

Check	Status	Detail
APPS Invalid Objects	CRITICAL	734 invalid APPS objects — recompile required
APPS_TS_TX_DATA Tablespace	WARNING	81.7% used, autoextend disabled

System Resources

✅

Disk Usage

68% — OK

✅

Memory

72% used — OK

✅

CPU

Avg 4.1% — OK

✅

I/O Wait

3.2% — OK

prod-ebs-app.example.com

EBS App Tier Check Results

EBS DB Health (from paired DB connection)

System Resources

Take the full EBS report with you

Ready to run this on your EBS instance?