Agresso reports queue
Job details
| Name: | Agresso reports queue |
| Platform: | Oracle |
| Category: | Agresso |
| Description: | Monitors and checks pending or running reports. Returns warning or alarm if the elapsed time exceeds defined threshold. |
| Long description: | Monitors and checks pending or running reports. Returns warning or alarm if the elapsed time exceeds defined thresholds. |
| Version: | 1.3 |
| Default schedule: | 4,9,14,19,24,29,34,39,44,49,54,59 7-17 * * |
| Requires engine install: | Yes |
| Compatibility tag: | .[type=‘instance’ & databasetype=‘oracle’]/.[hasengine=‘YES’ & maj_version > 11] |
Parameters
| Name | Default value | Description |
|---|---|---|
| Agresso schema owner | AGR | Name of the schema where the Agresso application is installed. You can specify a list of schemaas (separated by comma). You can use % (percent sign) to represent wild card characters. |
| warning threshold | 60 | Elapsed time warning threshold for running reports (in minutes). |
| alarm threshold | 180 | Elapsed time alarm threshold for running reports (in minutes). |
| time threshold | 24 | Only reports started within the “time threshold” (in hours) will be checked. |
Job Summary
- Purpose: Monitors pending or running Agresso reports, issuing warnings or alarms based on the duration these reports have been running against predefined thresholds.
- Why: Ensures operational efficiency by actively managing the duration of report processes and preventing prolonged running times that could indicate problems or inefficiencies within the databases.
- Manual checking: Check the current state of Agresso reports by querying the respective tables directly in the database:
select report_name, client, date_started, duration, server_queue, user_id, sch_name, status from agr_acrrepord_tab order by date_started desc;Dependency Details
- Main Procedure: Monitors the core operational logic.
- Schema Info: Checks for schema-related information crucial for monitoring.
- Reports Statistics: Stores statistics of the reporting, crucial for assessments and historical comparisons.
Database Implementation
“Implementation” includes creation and maintenance of:
- Tables:
- “agr_acrrepord_schema_info”: stores schema information and schema checking statuses. – “agr_acrrepord_tab”: records details about the Agresso reports including name, client, start time, duration, etc. - Procedure: – “agr_acrrepord_check”: contains the logic to populate both tables and apply business rules like warning and alarm thresholds on report durations.
Monitoring Schedule
Scheduled to run at every minute ending in 4 and 9 from 7 AM to 5 PM, ensuring frequent checks during normal business hours which can be deemed as high-activity periods.
Reporting Proficiency
Reports generated will:
- Showcase the running status and duration of Agresso reports.
- Display schemas actively monitored, highlighting any issues such as missing privileges or non-existing tables crucial for report generations.
Job Dependency Execution
Includes conditional logic for:
- Table existence verification: Ensures necessary tables are present for operations.
- Access rights verification: Check for adequate privileges to perform necessary operations on the database objects.
- Dynamic checking of schema configurations and report statuses: Adjusts monitoring mechanisms according to active database environments.
This comprehensive approach to managing and reporting on the Agresso reports provides vital insights and operational control to system administrators, enhancing the overall performance and reliability of the database systems.