Batch Monitor

February 12th, 2025

1 min read

Currently Running

View all active jobs or search for a specific one. The Currently Running table provides details including the current and average runtime (duration) per job. A big difference in these numbers could mean there is an issue.

UBE Analysis – Top 10 Jobs

Scan the Top 10 Jobs table for opportunities to index on a specific table and improve performance. You should always keep an eye out for jobs running longer than they should because it could be a sign of trouble.

Search the UBE Analysis table and export to data to csv with the Search/Export button.

Trending – Total Jobs

Gauge the average load on your system by day and hour in Clarity's Trending-Total Jobs bar graph. You can also hover over the bars to view details. Trending data is useful when scheduling maintenance windows.

Trending – Successful Jobs/Trending – Failed Jobs

Use Clarity's Trending-Successful and Trending-Failed graphs to quickly verify your jobs are running without error. This displays data for the last 30 days.

Topics:

ERP Suites Clarity 23A

Batch Monitor

Currently Running

UBE Analysis – Top 10 Jobs

Trending – Total Jobs

Trending – Successful Jobs/Trending – Failed Jobs

Related Articles

How to resolve a Java Out of Memory alert

Clarity Dashboard

Log Monitor stopped collecting

Application Monitor

How to resolve a Server CPU Utilized per Instance alert

Log Monitor

Reinstalling/Updating the Clarity Collector

How to resolve a JDE Net Invalid Request Exception

Database Monitor stopped collecting

Batch Monitor stopped collecting

How to resolve an ORA-03113 alert

Installing the Clarity Collector

How to resolve a KNT000086 alert

How to resolve a Manual Open JDB Transactions alert

Exporting Reports in Clarity

Application Analytics

Finding expensive database queries

How to resolve a OCI0000064 alert

Maintenance Windows

Finding your slowest applications

How to resolve an ODB0000162 alert

How to resolve an ORA-03114 alert

How to resolve an OALL8 alert

How to resolve a [COULD NOT START SCHEDULER] alert