> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Oracle E-Business Suite Monitoring

> Catch a stopped concurrent manager, a growing request backlog or invalid FND objects before users ask where their reports went.

Components
[`Engine`](https://docs.germainux.com/deploy/germain-ux-engine)
[`JS Profiler`](https://docs.germainux.com/deploy/germain-ux-js-profiler)
[`RPA Bot Recorder`](https://docs.germainux.com/deploy/germain-ux-rpa-bot-recorder)
[`RUM JS`](https://docs.germainux.com/deploy/germain-ux-rum-js)
[`RUM Extension`](https://docs.germainux.com/deploy/germain-ux-rum-extension)

Availability
8.6.9 or later

> [card] [What Is Monitored](#what-is-monitored)
>
> Requests, managers, objects

> [card] [How It Works](#how-it-works)
>
> Queries on the FND tables

> [card] [Deploy](#deploy)
>
> One wizard, one component

> [card] [KPIs](#kpis)
>
> 14 concurrent-processing KPIs

## Overview

GermainUX watches the concurrent processing of your Oracle E-Business Suite (EBS). You see how many requests are running, waiting and failing, how many processes each concurrent manager has, and how many FND database objects are invalid. A Standard Manager that stops shows up as a pending backlog that grows while its active processes fall to zero. Your team finds the stopped manager in minutes, instead of from a ticket about a report that never ran.

> [card] Request Backlog
>
> Running and pending concurrent requests over time, so a queue that stops draining stands out.

> [card] Manager Health
>
> Active processes of the Internal, Standard and Conflict Resolution managers, and terminated processes across all managers.

> [card] Failed Requests
>
> Requests that completed with an error or a warning, so a failing interface or report program shows up as a climbing count.

> [card] Invalid Objects After Patching
>
> The number of invalid FND objects, so you know whether a patch left anything to recompile.

### Questions It Answers

* Is the Standard Manager running, and since when has it been down?
* Are concurrent requests piling up in the pending queue?
* Did more requests end in error today than on a normal day?
* Did the last database restart leave terminated processes behind?
* Did the patch we applied last night leave invalid FND objects?
* Is the EBS database reachable from GermainUX right now?

## What Is Monitored

| Area | What GermainUX monitors |
| - | - |
| **Concurrent requests** | All requests, and the requests that are running, pending, completed with an error or completed with a warning |
| **Concurrent processes** | All processes, active processes, terminated processes, and the active processes of the Internal Manager (`FNDICM`), Standard Manager (`STANDARD`) and Conflict Resolution Manager (`FNDCRM`) queues |
| **Configuration** | The number of concurrent programs and concurrent queues, so you see when a patch or a change adds or removes them |
| **Database objects** | Invalid FND objects |
| **Database availability** | Whether GermainUX can connect to the EBS database and run the queries |
| **User experience** | Real-user page performance, JavaScript errors and Session Replay for the EBS pages your users work in, with [RUM JS](https://docs.germainux.com/deploy/germain-ux-rum-js.md) or the [RUM Extension](https://docs.germainux.com/deploy/germain-ux-rum-extension.md) |
| **Host** | CPU, memory, disk and network of the EBS application and database servers. See [Linux monitoring](https://docs.germainux.com/integrations/linux-redhat-suse-monitoring.md). |

## Analytics, Alerts and Automation

### AI Analysis

Ask [AI Explore](https://docs.germainux.com/analytics/ai-driven-insights.md) questions such as "When did pending concurrent requests last exceed 50?" and get the answer without building a report. [Outlier detection](https://docs.germainux.com/analytics/outlier-detection.md) flags an unusual rise in errored or pending requests.

### Dashboards and Reports

Build [dashboards and reports](https://docs.germainux.com/dashboards/dashboard-and-report.md) on the EBS KPIs: the request backlog next to the active processes of each manager, failed requests per day, and invalid objects before and after a patch window.

Click a value to open it in the [Analysis](https://docs.germainux.com/dashboards/analytics-dashboard/4-analysis-dashboard.md) screen. It compares the selected period with the previous days and shows how the KPI moved. In the example below, the Standard Manager stopped: pending requests climbed while its active processes stayed at zero, then drained after the restart.

![Analysis screen for the EBS Query Pending Concurrent Requests KPI, with pending requests climbing while the Standard Manager is down and draining after it restarts](https://mintcdn.com/germain-ux/cSCoMMl7KW61OHIM/images/main/oracle-e-business-suite-monitoring/ebs-pending-requests-analysis.png?fit=max\&auto=format\&n=cSCoMMl7KW61OHIM\&q=85\&s=0cc29420ef835c10342d1b25b5d8924a)

Analysis of Pending Concurrent Requests - GermainUX

### SLAs and Alerts

The EBS KPIs ship without SLAs, because the right thresholds depend on your workload. Add [SLAs](https://docs.germainux.com/analytics/slas.md) on the KPIs that matter to you, for example:

* **EBS Query Pending Concurrent Requests** above your normal backlog
* **EBS Query Active Processes Standard Manager Queue** at `0`
* **EBS Query Terminated Concurrent Processes** above `0`
* **EBS Query Invalid DB Objects** above `0`

Then get an [alert](https://docs.germainux.com/automation/notifications.md) by email, SMS, Slack or Teams when one is breached.

### Correlation with Other Technologies

[Correlate](https://docs.germainux.com/analytics/correlation-and-tracing.md) the EBS KPIs with the [Oracle Database](https://docs.germainux.com/integrations/oracle-db-observability.md) underneath, and with the experience of the users in the EBS pages, to tell a database problem from a concurrent-manager problem.

## How It Works

EBS database
EBS FND Query Component
KPIs
Alerts

| Component | What it does |
| - | - |
| **EBS FND Query Component** | A [query monitor](https://docs.germainux.com/analytics/query-monitoring.md) that runs 14 count queries on the EBS database on a schedule: on `APPLSYS.FND_CONCURRENT_REQUESTS`, `APPLSYS.FND_CONCURRENT_PROCESSES`, `APPLSYS.FND_CONCURRENT_PROGRAMS` and `APPLSYS.FND_CONCURRENT_QUEUES`, and on the invalid objects of the connected schema. Each query stores its count as one value of its KPI. |

The query monitor runs on a GermainUX Engine that can connect to the EBS database. Each run also records whether the database was reachable, in the **Database Availability** KPI.

## Before You Start

* A [GermainUX Engine](https://docs.germainux.com/deploy/germain-ux-engine.md) can connect to the EBS database over JDBC.
* A database account can run `SELECT` on `APPLSYS.FND_CONCURRENT_REQUESTS`, `APPLSYS.FND_CONCURRENT_PROCESSES`, `APPLSYS.FND_CONCURRENT_PROGRAMS` and `APPLSYS.FND_CONCURRENT_QUEUES`.
* For the invalid-objects count, the account is the schema that owns the FND objects. The query reads `user_objects`, so it counts only the objects the connected schema owns.
* The account's user name and password are stored as [credentials](https://docs.germainux.com/management/data-source.md) in GermainUX.

## Deploy

**1. Open the Database Query Monitor Deployment wizard**

In the left menu, go to **Settings > Wizards**. On the **Database Query Monitor Deployment** card, click **Add**.

**2. Connect to the EBS database**

On the **Database** step, fill in the fields, and then click **Next**:

| Field | Value |
| - | - |
| **Database** | The EBS database. Select it, or create a database data source for it. |
| **Credentials** | The credentials of the database account |
| **Monitored Software** | The application the data belongs to, for example `EBS - Oracle E-Business Suite` |

**3. Choose the EBS component**

On the **Component** step, select **EBS FND Query Component** as the **Component**, and then click **Next**.

![Database Query Monitor Deployment wizard on the Component step with EBS FND Query Component selected](https://mintcdn.com/germain-ux/cSCoMMl7KW61OHIM/images/main/oracle-e-business-suite-monitoring/database-query-monitor-ebs-component.png?fit=max\&auto=format\&n=cSCoMMl7KW61OHIM\&q=85\&s=8f7096f108035ee3d017bdf5d20f7b1b)

Database Query Monitor Deployment Wizard with the EBS Component - GermainUX

**4. Deploy it to the Engine**

On the **Deployment** step, fill in the fields, and then finish the wizard:

| Field | Value |
| - | - |
| **Monitor Name** | A name you recognize, for example `EBS FND Query - PROD` |
| **Monitoring Node** | The Monitoring Node and Engine that can reach the EBS database |
| **Schedule on which to run this component** | How often to run the queries. The default, `0 0 * * * *`, runs once an hour. To see a stopped manager within minutes, use `0 */5 * * * *` (every five minutes). |

Repeat the wizard for each EBS instance you want to monitor.

## Validate

**1. Wait for the first run**

The first values arrive after the first scheduled run, for example within five minutes with `0 */5 * * * *`.

**2. Compare a count with the database**

In GermainUX Workspace, open the **EBS Query Pending Concurrent Requests** KPI. In SQL\*Plus or SQL Developer, run the same count with the monitoring account:

```sql theme={null}
select count(1) from APPLSYS.FND_CONCURRENT_REQUESTS where PHASE_CODE = 'P';
```

The KPI shows the same value for the last run.

**3. Check the database availability**

Open the **Database Availability** KPI and check that the EBS database shows `100`.

## Troubleshooting

> [accordion] No EBS values appear
>
> Open the **Database Availability** KPI. If the EBS database shows `0`, the Engine can't connect: check the host, port and service name of the database, the credentials, and the network path from the Engine. If it shows `100`, check that the account can run `select count(1) from APPLSYS.FND_CONCURRENT_REQUESTS`.

> [accordion] Invalid DB Objects always shows 0
>
> The invalid-objects query reads `user_objects`, which lists only the objects the connected schema owns. Connect with the schema that owns the FND objects.

> [accordion] The values change only once an hour
>
> The wizard's default schedule, `0 0 * * * *`, runs the queries once an hour. Edit the monitor and set a shorter schedule, for example `0 */5 * * * *`.

> [accordion] Errored requests never go down
>
> The error and warning counts include every request still in `FND_CONCURRENT_REQUESTS`. They fall when old requests are purged. Watch the change from one run to the next, or add an SLA on the increase, rather than on the total.

## Security and Privacy

Oracle E-Business Suite monitoring stores counts only: the number of requests, processes, programs, queues and invalid objects. It doesn't read request parameters, user names or business data. When the database can't be reached, the **Database Availability** KPI stores the connection error, which can include the database host and the account name. Treat it as possibly containing personal or customer data.

To mask, anonymize or exclude this data, see [Data Privacy](https://docs.germainux.com/management/compliance-privacy-and-security/data-privacy.md).

## KPIs

| KPI | What it holds |
| - | - |
| **EBS Query Concurrent Requests** | All requests in `FND_CONCURRENT_REQUESTS` |
| **EBS Query Running Concurrent Requests** | Requests in the running phase |
| **EBS Query Pending Concurrent Requests** | Requests in the pending phase |
| **EBS Query Concurrent Requests With Error** | Requests that completed with an error |
| **EBS Query Concurrent Requests With Warning** | Requests that completed with a warning |
| **EBS Query Concurrent Processes** | All concurrent processes |
| **EBS Query Active Concurrent Processes** | Active concurrent processes |
| **EBS Query Terminated Concurrent Processes** | Terminated concurrent processes |
| **EBS Query Active Processes Internal Manager Queue** | Active processes of the Internal Manager (`FNDICM`) |
| **EBS Query Active Processes Standard Manager Queue** | Active processes of the Standard Manager (`STANDARD`) |
| **EBS Query Active Processes Conflict Manager Queue** | Active processes of the Conflict Resolution Manager (`FNDCRM`) |
| **EBS Query Concurrent Programs** | Concurrent programs |
| **EBS Query Concurrent Queues** | Concurrent queues |
| **EBS Query Invalid DB Objects** | Invalid objects whose name starts with `FND` |
| **Database Availability** | Whether the EBS database was reachable on each run. Default SLA: OK at `97.5` % or more, per database. |

All EBS KPIs are data model `GenericMetric`. See [KPIs](https://docs.germainux.com/analytics/kpis.md) and [SLAs](https://docs.germainux.com/analytics/slas.md).

## Related Documentation

> [card] [Query Monitoring](https://docs.germainux.com/analytics/query-monitoring.md)
>
> How query monitors work

> [card] [Oracle Database](https://docs.germainux.com/integrations/oracle-db-observability.md)
>
> The database underneath EBS

> [card] [Automation](https://docs.germainux.com/automation.md)
>
> More Automation Features

## Get Help

The GermainUX team can help you add queries for the concurrent programs and managers that matter to your business.

> [card] [Contact GermainUX Support](https://docs.germainux.com/getting-started/support.md)
>
> The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

> [card] Can't Find What You Need?
>
> Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.