EBSDB

Oracle 19c (19.0.0.0.0) EBS R12.2 Linux x86_64 prod-ebs-db.example.com:1521 🏭 EBS R12

Overall Score

Storage

Wait Events

SQL

Sessions

Memory

✦ TuneVault AI Summary

This Oracle 19c EBS database has 3 critical findings requiring immediate attention. Log file sync at 38.7% of DB time indicates redo log contention — likely caused by undersized or slow redo log groups. DCM tablespace is at 89.9% with autoextend disabled, and RMAN backup is not configured, leaving no recovery point.

⚡

Top Action Now

Configure RMAN backup immediately — no recovery point exists. Add datafiles to DCM and APPS_TS_TX_DATA tablespaces. Move redo log groups to faster storage to resolve log file sync contention.

DB Name

EBSDB

Version

19.0.0.0.0

Edition

Enterprise

Platform

Linux x86_64

Host

prod-ebs-db

Uptime

14d 0h

SGA Size

2 GB

PGA Target

1 GB

CPU Cores

8 vCPU

Check Results 🔴 3 critical ⚠ 2 warnings ✓ 46 passed

🔴 Critical DCM tablespace near capacity — autoextend OFF

89.9% used ▾

DCM tablespace has autoextend disabled and is at 89.9% utilization. With no headroom and no auto-growth, any burst activity will trigger ORA-01653 and halt all DCM-related DML. Add a new datafile or enable autoextend immediately.

ALTER TABLESPACE DCM ADD DATAFILE '/u02/app/oracle/oradata/EBSDB/dcm02.dbf' SIZE 4096M AUTOEXTEND ON NEXT 512M MAXSIZE UNLIMITED;

🔴 Critical RMAN backup not configured

No backups found ▾

No RMAN backup jobs have ever run on this instance. There is no recovery point. A disk failure or data corruption event would result in complete, unrecoverable data loss. Configure and run an initial RMAN full backup immediately.

RMAN TARGET / RUN { CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS; CONFIGURE DEFAULT DEVICE TYPE TO DISK; CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backup/EBSDB/%U'; BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG DELETE INPUT; BACKUP CURRENT CONTROLFILE; }

🔴 Critical Log file sync — 38.7% of DB time

27.42 ms avg wait ▾

Log file sync at 38.7% of DB time with 27.42 ms average wait is well above the 5–8 ms acceptable threshold. This indicates the redo log files are on slow storage or being written in competition with data files. Move redo logs to dedicated fast disks (SSD or separate spindle). Also verify COMMIT_WRITE is configured for optimal performance.

-- Check current redo log file locations: SELECT l.group#, lf.member, l.bytes/1024/1024 size_mb, l.status FROM v$log l JOIN v$logfile lf ON l.group# = lf.group# ORDER BY l.group#; -- Add new log group on fast storage, then drop old: ALTER DATABASE ADD LOGFILE GROUP 4 ('/u04/fast/redo/EBSDB_redo04a.log') SIZE 300M; ALTER DATABASE DROP LOGFILE GROUP 1;

⚠ Warning APPS_TS_TX_DATA at 81.7% — autoextend OFF

81.7% used ▾

⚠ Warning Workflow Mailer in DEACTIVATED_SYSTEM state

1,044 pending notifications ▾

🔴

Immediate action required: DCM and ODM_DATA tablespaces above 89% with autoextend disabled. APPS_TS_TX_DATA at 81.7% — add datafiles before the next batch window.

Tablespace Usage

Tablespace	Used	Total	Used %	Autoext	Status
DCM	8.01 GB	8.91 GB	89.9%	OFF	CRITICAL
ODM_DATA	7.94 GB	8.91 GB	89.1%	OFF	WARNING
APPS_TS_TX_DATA	7.28 GB	8.91 GB	81.7%	OFF	WARNING
SYSTEM	6.57 GB	8.91 GB	73.8%	ON	OK
APPS_TS_TX_IDX	5.36 GB	8.91 GB	60.1%	ON	OK
APPS_TS_SEED	3.86 GB	8.91 GB	43.4%	ON	OK
SYSAUX	3.76 GB	8.91 GB	42.2%	ON	OK
APPS_TS_ARCHIVE	1.37 GB	8.91 GB	15.4%	ON	OK
APPS_TS_QUEUES	1.04 GB	8.91 GB	11.7%	ON	OK
APPS_TS_NOLOGGING	0.86 GB	8.91 GB	9.6%	ON	OK
APPS_TS_SUMMARY	0.81 GB	8.91 GB	9.1%	ON	OK
APPS_UNDOTS1	0.28 GB	8.91 GB	3.1%	ON	OK
TEMP	0.00 GB	9.00 GB	0%	ON	OK

Undo Tablespace

Tablespace	APPS_UNDOTS1
Used	0.28 GB / 8.91 GB (3.1%)
Retention	900 seconds
Guarantee	NOGUARANTEE
Status	OK

Temp Tablespace

Tablespace	TEMP
Used	0.5 GB / 9.0 GB (5.2%)
Free	8.5 GB
Sort Usage	0 active sorts
Status	OK

🔴

Log file sync at 38.7% of DB time — 27.42 ms average wait is 3–5× above normal. Redo logs are on slow storage. Move to dedicated SSD or separate disk spindle. SQL 00f34kc6pr2wn averages 5.16 seconds per execution.

Top Wait Events (DB time, current snapshot)

Wait Event	Class	% DB Time	Total Waits	Avg Wait (ms)
log file sync	Commit	38.7%	76,312	27.42
db file sequential read	User I/O	28.2%	207,541	4.89
direct path read	User I/O	3.9%	31,628	4.45
control file parallel write	System I/O	2.6%	18,904	4.97
db file scattered read	User I/O	2.3%	14,218	5.83

Top SQL by Elapsed Time

#	SQL_ID	Executions	Elapsed / Exec	CPU / Exec	SQL Text (sample)	Flag
1	00f34kc6pr2wn	318	5,160 ms	210 ms	SELECT * FROM FND_RESPONSIBILITY_VL WHERE...	High Elapsed
2	g7k2w9n4p1m8x	5,412	249 ms	48 ms	SELECT request_id, phase_code FROM FND_CONCURRENT_REQUESTS WHERE...	Monitor
3	8s6unu0n34g0t	12,847	216 ms	55 ms	SELECT * FROM FND_USER WHERE USER_ID = :b1	OK
4	t5r1h8v3j6c9q	89,312	49.9 ms	8 ms	SELECT activity_result_code FROM WF_ITEM_ACTIVITY_STATUSES WHERE...	OK

⚡ AI Recommendation — SQL 00f34kc6pr2wn HIGH ELAPSED

▾

SQL 00f34kc6pr2wn queries FND_RESPONSIBILITY_VL with 5.16 seconds average elapsed time across 318 executions. The high elapsed vs low CPU ratio (5.16s / 0.21s) indicates an I/O-bound execution plan, likely a full table scan on a large view. Check if an index on RESPONSIBILITY_KEY or APPLICATION_ID is missing.

-- Capture current execution plan: SELECT * FROM TABLE(DBMS_XPLAN.DISPLAY_CURSOR('00f34kc6pr2wn', NULL, 'ALLSTATS LAST')); -- Check existing indexes on base tables: SELECT index_name, column_name, column_position FROM dba_ind_columns WHERE table_name IN ('FND_RESPONSIBILITY','FND_RESPONSIBILITY_TL') ORDER BY index_name, column_position;

🔴

No RMAN backup has ever been configured. There is no recovery point for this database. A disk failure or accidental data loss would be unrecoverable. Configure and run an initial full backup immediately.

RMAN Status

NOT CONFIGURED

No backup jobs found

Recovery Point

NONE

Zero RPO guarantee

Archivelog Mode

ENABLED

~0.5 GB/day rate

FRA Usage

12.8%

12.8 / 100 GB

Redo Log Groups

Group#	Members	Size	Status	Archived
1	1	300 MB	INACTIVE	YES
2	1	300 MB	CURRENT	NO
3	1	300 MB	INACTIVE	YES

Block Corruptions

✓

0 corruptions detected. V$DATABASE_BLOCK_CORRUPTION shows no entries. DB_BLOCK_CHECKSUM is enabled.

🔴 Fix: Configure RMAN Backup CRITICAL

▾

Run as oracle OS user. This configures a basic RMAN policy and runs the initial full backup. Adjust FORMAT path to match your backup storage mount.

RMAN TARGET / CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS; CONFIGURE DEFAULT DEVICE TYPE TO DISK; CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backup/EBSDB/%U'; CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backup/EBSDB/cf_%F'; RUN { BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG DELETE INPUT; BACKUP CURRENT CONTROLFILE; } -- Verify: LIST BACKUP SUMMARY;

⚠

Workflow Notification Mailer is in DEACTIVATED_SYSTEM state with 147 workflow errors and 1,044 pending notifications backlogged. Concurrent Manager has 1 pending request. Mailer reset required.

Concurrent Manager Status

Manager Name	Status	Target	Active	Pending	Completed (24h)
Internal Manager (ICM)	Active	1	1	0	—
Standard Manager	Backlogged	5	5	1	87
Conflict Resolution Mgr	Active	1	1	0	—
Output Post Processor	Active	1	1	0	42
Scheduler Agent	Active	2	2	0	—
Receiving Transaction Mgr	Active	1	1	0	14
Workflow Agent Listener	Active	2	2	0	—
Material Transactions Mgr	Active	1	1	0	312
Cost Management Worker	Active	2	2	0	28
Report Manager	Active	2	2	0	156

Total managers: 10 defined · 21 target processes · 20 active · 1 pending request

Workflow Notification Mailer

⚠

DEACTIVATED_SYSTEM — Mailer was stopped by the system (typically due to mail server connectivity failure). 147 workflow errors accumulated. 1,044 notifications are queued and cannot be delivered until mailer is restarted.

Reset steps:
1. System Admin → Oracle Applications Manager → Workflow → Service Components
2. Find "Workflow Notification Mailer" → Actions → Start
3. If still DEACTIVATED_SYSTEM, use Stop then Start (2-step reset)
4. Verify OUTBOUND_SERVER connectivity in WF_MAILER_PARAMETERS

Component	Status	Startup Mode	Last Updated
Workflow Notification Mailer	DEACTIVATED_SYSTEM	AUTOMATIC	2026-06-24 03:12
Workflow Agent Listener — Deferred	RUNNING	AUTOMATIC	2026-06-24 00:01
Workflow Agent Listener — Error	RUNNING	AUTOMATIC	2026-06-24 00:01
Workflow Agent Listener — Inbound	RUNNING	AUTOMATIC	2026-06-24 00:01
Workflow Document Web Services	RUNNING	AUTOMATIC	2026-06-24 00:01
Workflow Business Event System	RUNNING	AUTOMATIC	2026-06-24 00:01

🔴

4 accounts with Oracle default passwords and 2 DBA grants in the last 30 days. Both require immediate review — default passwords are the #1 vector for Oracle database compromise.

Accounts with Default Passwords

Username	Account Status	Default Password	Last Login	Recommendation
DBSNMP	OPEN	dbsnmp	Never	Lock or rotate — monitoring agent should use dedicated account
SCOTT	OPEN	tiger	2024-11-14	Lock — demo account, should not be active in production
HR	OPEN	hr	2025-01-03	Lock — sample schema, not needed in production
OUTLN	OPEN	outln	Never	Lock — legacy stored outlines account, unused

DBA Role Grants — Last 30 Days

Grantee	Granted By	Grant Date	Admin Option	Risk
WIDGET_REPORT	SYS	2026-04-28	NO	⚠ Review — reporting user with DBA role
ACME_TEMP_ADMIN	SYS	2026-04-19	YES	🔴 Critical — temp account with ADMIN OPTION

REVOKE DBA FROM WIDGET_REPORT; GRANT SELECT ANY TABLE TO WIDGET_REPORT; GRANT CREATE SESSION TO WIDGET_REPORT; REVOKE DBA FROM ACME_TEMP_ADMIN; ALTER USER ACME_TEMP_ADMIN ACCOUNT LOCK;

⚠

Buffer cache hit ratio at 83.8% — below the 95% target for OLTP. Free RAM at 0.1 GB is critically low; consider adding RAM or reducing SGA_TARGET. Hard parses at 45.2/sec indicate insufficient shared pool or cursor sharing issues.

SGA Total

2.0 GB

Buffer + shared pool

Buffer Cache Hit %

83.8%

Target: ≥95% for OLTP

Shared Pool Free

8.2%

49 MB of 614 MB

Hard Parses / sec

45.2

Bind variables recommended

SGA Component Breakdown

Component	Allocated	Metric	Value	Status
Buffer Cache	1.2 GB	Hit Ratio	83.8%	LOW — target ≥95%
Shared Pool	0.6 GB	Library Cache Hit	96.4%	Free 8.2% — monitor
Large Pool	0.1 GB	RMAN Usage	0 MB	OK
Java Pool	0.05 GB	Used	42%	OK

PGA Statistics

PGA Target

1.0 GB

PGA Allocated

0.8 GB

80% of target

Optimal Executions

81.2%

Target: ≥90%

Multipass Executions

4.5%

Disk spill occurring

ASMM Auto-resize History (last resize ops)

Component	Final Size	Last Op	Reason
Shared Pool	1.03 GB	STATIC	SGA_TARGET managed
DEFAULT buffer cache	0.75 GB	STATIC	SGA_TARGET managed

Key Initialization Parameters

Parameter	Value	Default	Notes
SGA_TARGET	2147483648 (2 GB)	0	ASMM enabled
PGA_AGGREGATE_TARGET	1073741824 (1 GB)	0	Automatic PGA management
DB_BLOCK_SIZE	8192	8192	Standard 8K block
PROCESSES	500	100	EBS recommended
SESSIONS	772	derived	= PROCESSES * 1.5 + 22
OPEN_CURSORS	600	50	EBS requires ≥500
UNDO_RETENTION	900	900	Default — consider 3600 for long reports
LOG_BUFFER	16777216 (16 MB)	derived	Consider 32 MB given log sync issues
DB_FILES	200	200	OK for current datafile count
NLS_CHARACTERSET	AL32UTF8	—	EBS Unicode standard
OPTIMIZER_MODE	ALL_ROWS	ALL_ROWS	EBS default

Instance Information

Instance Name

EBSDB

DB Version

19.0.0.0.0

Host Name

prod-ebs-db

Arch Mode

ARCHIVELOG

Log Mode

ARCHIVELOG

Platform

Linux x86_64

DB Created

2026-06-11

Uptime

14d 0h

OS Statistics

CPU Cores

vCPU

CPU Avg

2.3%

Max: 3.1%

I/O Wait

4.7%

Acceptable

RAM Total

3.6 GB

Free: 0.1 GB

✓

No index fragmentation detected. All indexes are within normal bloat thresholds. Index score: 100/100.

Index Score

100 / 100

No action required

Indexes Analyzed

2,847

APPS schema indexes

Fragmented

>30% deleted entries

Unusable

All indexes VALID

Index Health Summary

Category	Count	Status	Action
Unusable indexes	0	OK	None required
Indexes with >30% deleted leaf rows	0	OK	None required
Function-based indexes (disabled)	0	OK	None required
Indexes on NOLOGGING tablespace	14	Expected	Normal for EBS staging tables
Total APPS schema indexes	2,847	VALID	All valid and usable

AI Analysis

GPT-4o powered

## SUMMARY

EBSDB is an Oracle 19c EBS R12.2 production database running on an 8-core Linux server with a 2 GB SGA. Overall health score is 72/100, reflecting functional operation with three critical issues that require attention within 24–48 hours. The database has never had RMAN configured, redo log contention is consuming 38.7% of DB time, and two tablespaces are above 80% capacity with autoextend disabled.

The highest-urgency issue is the complete absence of any RMAN backup configuration. There is no recovery point. A disk failure, accidental truncation, or data corruption event would result in complete, permanent data loss. This is a production EBS instance — the risk is existential. Configure RMAN tonight with at minimum a 7-day retention window, and run the initial full backup before any other maintenance activity.

Log file sync at 38.7% of DB time with a 27.42 ms average wait is the dominant performance issue. For an OLTP EBS environment, log file sync should be under 5–8 ms. The most likely cause is redo log files sharing the same physical spindle as data files. Moving the three 300 MB log groups to dedicated fast storage (SSD or a separate disk group) will eliminate this bottleneck and reduce overall DB time significantly. A secondary contributing factor may be the LOG_BUFFER at 16 MB — increasing to 32 MB can reduce redo write frequency for the current workload.

## TOP_RISKS

1. RMAN not configured — no recovery point, zero RPO guarantee. Configure RMAN and run initial full backup immediately.

2. Log file sync 38.7% DB time — 27.42 ms avg wait is 3–5× above OLTP threshold. Move redo logs to dedicated fast storage.

3. DCM tablespace 89.9% — autoextend OFF — approaching ORA-01653. Add datafile immediately.

4. Buffer cache hit ratio 83.8% — below 95% OLTP target. SGA_TARGET at 2 GB may be undersized for the current workload; consider increasing to 4 GB if OS RAM allows.

5. Workflow Mailer DEACTIVATED_SYSTEM — 1,044 notifications queued, 147 errors accumulated. Restart mailer and verify OUTBOUND_SERVER connectivity.

## TOP_ACTION

Configure RMAN backup tonight. Move redo log groups to fast storage and expand DCM tablespace before the next business day. These three actions address all three critical risks in a single maintenance window.

EBSDB

Tablespace Usage

Undo Tablespace

Temp Tablespace

Top Wait Events (DB time, current snapshot)

Top SQL by Elapsed Time

⚡ AI Recommendation — SQL 00f34kc6pr2wn HIGH ELAPSED

Redo Log Groups

Block Corruptions

🔴 Fix: Configure RMAN Backup CRITICAL

Concurrent Manager Status

Workflow Notification Mailer

Accounts with Default Passwords

DBA Role Grants — Last 30 Days

SGA Component Breakdown

PGA Statistics

ASMM Auto-resize History (last resize ops)

Key Initialization Parameters

Instance Information

OS Statistics

Index Health Summary

AI Analysis

## SUMMARY

## TOP_RISKS

## TOP_ACTION

Take the full report with you

Ready to run this on your Oracle instance?