Results for “alert_long_running_enabled”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_CONC_PROG_ONSITE_INFO is an Application Object Library (FND) table owned by the APPLSYS schema. It stores site-level runtime information about concurrent programs, effectively acting as a per-program performance and alerting profile on a given Oracle E-Business Suite instance. Whereas FND_CONCURRENT_PROGRAMS defines what a concurrent program is, this table records how that program has actually behaved and how it should be monitored — last execution outcome, historical run-time statistics, shelf life, and the thresholds that trigger long-running or long-pending alerts.

The table is present and valid in both Oracle EBS 12.1.1 and 12.2.2, with the documented physical schema listing 31 columns. Its foreign keys to FND_NODES via NODE_NAME1 and NODE_NAME2 indicate that certain monitoring behaviour is node-aware, which is relevant in multi-node (RAC or multi-tier) deployments where run-time characteristics differ by application tier node. From a Data Vault modeling perspective, the FK metadata suggests a heuristic classification of link — the table ties concurrent program definitions to node entities while carrying descriptive runtime attributes — though functionally it behaves more like a satellite capturing run-time and monitoring state per program.

Key Information Stored

The table is uniquely keyed by the index FND_CONC_PROG_ONSITE_INFO_U1 on the composite (PROGRAM_APPLICATION_ID, CONCURRENT_PROGRAM_ID), which constitutes the true business key. There is no separate single-column surrogate; the composite pair identifies one row per concurrent program. The most significant columns are:

• PROGRAM_APPLICATION_ID / CONCURRENT_PROGRAM_ID — the business-key pair identifying which concurrent program the row profiles.
• LAST_RUN_DATE, LAST_RUN_REQUEST_ID, OUTCOME — when the program last executed, the concurrent request that ran it, and the resulting completion status.
• MIN_RUN_TIME, MAX_RUN_TIME, AVG_RUN_TIME — observed execution durations, used as a baseline for performance comparison.
• SHELF_LIFE — the acceptable age of output before it is considered stale.
• MONITOR_ENABLED, REQUEST_SCH_INTERVAL, RESET_DATE — whether monitoring is active, the review interval, and when statistics were last reset.
• SUCCESSFUL_COMPLETION, WARNING_COMPLETION, ERROR_COMPLETION — flags governing how each completion class is treated.
• ALERT_LONG_RUNNING_ENABLED, ALERT_LONG_RUNNING_THRESHOLD, ALERT_LONG_RUNNING_TOLERANCE — long-running job alerting configuration.
• ALERT_LONG_PENDING_ENABLED, ALERT_LONG_PENDING_TOLERANCE — long-pending alerting configuration.
• NODE_NAME1, NODE_NAME2, CONNSTR1, CONNSTR2 — the nodes and connection strings associated with the program's runtime.
• ON_FAILURE_LOG_LEVEL, BUSINESS_EVENT_MAP — failure logging verbosity and business event mapping.
• Audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) — standard WHO columns.

Common Use Cases and Queries

Administrators and DBAs use this table to review which concurrent programs are under monitoring, identify chronically slow programs, and tune alert thresholds. A typical query joins to FND_CONCURRENT_PROGRAMS to resolve program names:

• List monitored programs whose AVG_RUN_TIME exceeds MIN_RUN_TIME by a wide margin.
• Identify programs with MONITOR_ENABLED = 'Y' and an overdue LAST_RUN_DATE relative to SHELF_LIFE.
• Audit alert configuration by reporting ALERT_LONG_RUNNING_ENABLED and ALERT_LONG_PENDING_ENABLED programs.
• Diagnose programs where OUTCOME is repeatedly error or warning, correlated with LAST_RUN_REQUEST_ID in FND_CONCURRENT_REQUESTS.

Related Objects

• FND_NODES — referenced via NODE_NAME1 and NODE_NAME2; supplies node identity for node-aware monitoring.
• FND_CONCURRENT_PROGRAMS — parent definition resolved through PROGRAM_APPLICATION_ID and CONCURRENT_PROGRAM_ID.
• FND_CONCURRENT_REQUESTS — joined via LAST_RUN_REQUEST_ID for run outcome detail.
• FND_CONCURRENT_PROGRAMS_TL — provides translated program names for reporting.
• FND_CONCURRENT_WORKER / concurrent manager runtime tables — contextual runtime performance data.
• FND_APPLICATION — resolves PROGRAM_APPLICATION_ID to the owning application.