What Is Monitored
How It Works
Deploy
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.Request Backlog
Manager Health
Failed Requests
Invalid Objects After Patching
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
Analytics, Alerts and Automation
AI Analysis
Ask AI Explore questions such as “When did pending concurrent requests last exceed 50?” and get the answer without building a report. Outlier detection flags an unusual rise in errored or pending requests.Dashboards and Reports
Build dashboards and reports 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 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 of Pending Concurrent Requests - GermainUX
SLAs and Alerts
The EBS KPIs ship without SLAs, because the right thresholds depend on your workload. Add SLAs 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
Correlation with Other Technologies
Correlate the EBS KPIs with the Oracle Database 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
Before You Start
- A GermainUX Engine can connect to the EBS database over JDBC.
- A database account can run
SELECTonAPPLSYS.FND_CONCURRENT_REQUESTS,APPLSYS.FND_CONCURRENT_PROCESSES,APPLSYS.FND_CONCURRENT_PROGRAMSandAPPLSYS.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 in GermainUX.
Deploy
Open the Database Query Monitor Deployment wizard
Connect to the EBS database
Choose the EBS component

Database Query Monitor Deployment Wizard with the EBS Component - GermainUX
Deploy it to the Engine
Validate
Wait for the first run
0 */5 * * * *.Compare a count with the database
Check the database availability
100.Troubleshooting
No EBS values appear
No EBS values appear
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.Invalid DB Objects always shows 0
Invalid DB Objects always shows 0
user_objects, which lists only the objects the connected schema owns. Connect with the schema that owns the FND objects.The values change only once an hour
The values change only once an hour
0 0 * * * *, runs the queries once an hour. Edit the monitor and set a shorter schedule, for example 0 */5 * * * *.Errored requests never go down
Errored requests never go down
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.KPIs
GenericMetric. See KPIs and SLAs.
Related Documentation
Query Monitoring
Oracle Database
Automation
Get Help
The GermainUX team can help you add queries for the concurrent programs and managers that matter to your business.Contact GermainUX Support
Can't Find What You Need?
The content of this document is proprietary to GERMAIN SOFTWARE.

