Here are real OEM UI visuals (based on Oracle docs & actual console layouts) so you can understand how screens look in Oracle Enterprise Manager 13c.
I’ll walk you through the main screens with visual-style explanation (like screenshots) 👇
🖥️ 1. OEM Dashboard (Home Page)
----------------------------------------------------------
| Enterprise Manager Console |
----------------------------------------------------------
| Targets Status | Incidents | Alerts | Performance |
----------------------------------------------------------
| DB1 ✅ Up | Incidents: 3 🔴 |
| DB2 ⚠ Warning | CPU High |
| HOST1 ✅ | Tablespace 90% |
----------------------------------------------------------
| Top Activity | CPU | Memory | Sessions |
----------------------------------------------------------
| Graphs showing load, sessions, SQL activity |
----------------------------------------------------------
🔍 What you see:
Overall DB status
Alerts summary
Performance graphs
👉 This is your first landing page
🚨 2. Incident Manager Screen (MOST IMPORTANT)
📍 Navigation:Enterprise → Monitoring → Incident Manager
----------------------------------------------------------
| Incident Manager |
----------------------------------------------------------
| Summary: |
| Open: 12 | Critical: 3 🔴 | Warning: 5 ⚠ |
----------------------------------------------------------
| Charts: |
| - Incidents by Severity |
| - Incidents by Target |
----------------------------------------------------------
| Incident List: |
----------------------------------------------------------
| Time | Target | Message | Severity |
----------------------------------------------------------
| 11:05 | DB1 | Tablespace Full | CRITICAL 🔴 |
| 11:06 | DB1 | Tablespace Full | CRITICAL 🔴 |
| 11:07 | DB1 | Tablespace Full | CRITICAL 🔴 |
----------------------------------------------------------
💡 Key Point:
👉 With alert compression enabled
These 3 rows → become 1 incident
📌 OEM groups events into incidents automatically (Oracle Documentation)
📊 3. Incident Dashboard (Graph View)
----------------------------------------------------------
| Incident Dashboard |
----------------------------------------------------------
| 🔴 Critical: 3 ⚠ Warning: 5 ℹ Info: 4 |
----------------------------------------------------------
| Pie Chart: |
| DB Issues: 50% |
| Host Issues: 30% |
| Listener: 20% |
----------------------------------------------------------
| Actions: |
| [Acknowledge] [Assign] [Escalate] |
----------------------------------------------------------
🔍 What this gives:
Visual distribution of issues
Quick filtering
👉 Dashboard auto-refreshes every ~30 sec (Oracle Documentation)
⚙️ 4. Metric & Threshold Configuration Screen
📍 Navigation:Target → Monitoring → Metric and Collection Settings
----------------------------------------------------------
| Metric Settings: CPU Utilization |
----------------------------------------------------------
| Warning Threshold: 80% |
| Critical Threshold: 90% |
| Occurrences: 3 |
----------------------------------------------------------
| Corrective Action: |
| Script: restart_service.sh |
----------------------------------------------------------
| [Save] |
----------------------------------------------------------
💡 Important:
Occurrences = key for alert suppression
Prevents alert flapping
🔁 5. Incident Rules (Alert Compression Engine)
📍 Navigation:Setup → Incidents → Incident Rules
----------------------------------------------------------
| Rule Set: DB_ALERT_COMPRESSION |
----------------------------------------------------------
| Condition: |
| Target Type = Database |
| Severity = Critical |
----------------------------------------------------------
| Actions: |
| ✔ Create Incident |
| ✔ Add to existing open incident (IMPORTANT) |
| ✔ Send Notification |
----------------------------------------------------------
🔥 This is the feature:
👉 That actually performs alert grouping/compression
🔕 6. Notification Rules Screen
📍 Navigation:Setup → Notifications → Notification Rules
----------------------------------------------------------
| Notification Rule |
----------------------------------------------------------
| Target: All Databases |
| Event Type: Metric Alert |
| Severity: Critical Only |
----------------------------------------------------------
| Actions: |
| Send Email: dba@company.com |
----------------------------------------------------------
💡 Result:
No spam emails
Only critical alerts sent
⛔ 7. Blackout Screen (Maintenance Mode)
📍 Navigation:Enterprise → Monitoring → Blackouts
----------------------------------------------------------
| Create Blackout |
----------------------------------------------------------
| Target: DB1 |
| Start Time: 10:00 |
| Duration: 2 Hours |
----------------------------------------------------------
| Options: |
| ✔ Stop Monitoring |
| ✔ Suppress Alerts |
----------------------------------------------------------
🎯 How It All Connects (Architecture Flow)
DB Metric → Threshold Breach → Event Generated
↓
Incident Rule Applied
↓
Event Grouped (Compression)
↓
Incident Created
↓
Notification Sent (if needed)
👉 OEM uses agents + rules to convert events into incidents (Oracle)
🧠 Real DBA Understanding
When you see OEM UI:
| Screen | Purpose |
|---|---|
| Dashboard | Overall health |
| Incident Manager | Actual issues |
| Metric Settings | Control alerts |
| Incident Rules | Reduce noise |
| Notifications | Alert delivery |
🚀 Pro Tip (From Production)
Most DBAs fail because:
They only look at Incidents
But never configure:
Thresholds
Rules
👉 Result = Alert storm
No comments:
Post a Comment