Search Results icm_alive

Overview

FND_CONC is a core Oracle E-Business Suite package in the APPS schema that supports the Concurrent Manager subsystem of the Oracle EBS application tier. Concurrent processing in EBS orchestrates the execution of reports, programs, and background jobs through one or more Concurrent Managers, which are OS-level processes that poll the FND tables for pending requests. FND_CONC provides the supporting programmatic primitives used by the Concurrent Manager infrastructure: liveness testing of managers and service processes, diagnostics, phase and status interrogation of concurrent requests, and cancellation of patch-related requests.

The package is classified in the ETRM metadata as OTHER under the Concurrent Processing domain. Its documented status is VALID, and it exposes eight documented program units. FND_CONC itself depends upon the SYS.STANDARD package and is referenced by a small set of internal packages — FND_AMP_PRIVATE, FND_CONC_SSWA, and OKL_VIEW_CONCURRENT_PVT, as well as a recursive reference to itself — confirming its role as a lower-level utility that supports higher-level concurrent manager and self-service administration flows rather than an end-user API.

Key Procedures and Functions

The ETRM documentation identifies the following eight program units. Parameter signatures are not published in the ETRM record and should not be assumed; only the functional intent is described here.

• DIAGNOSE — Provides diagnostic output for the concurrent processing environment; typically used to inspect manager state, queue health, or configuration issues during troubleshooting.
• PROCESS_ALIVE — Determines whether a given concurrent manager (or worker) OS process is still alive and responsive. Used by the Internal Concurrent Manager to detect dead or hung managers.
• ICM_ALIVE — Verifies that the Internal Concurrent Manager (ICM) itself is alive. Critical to the survivability and failover logic of the concurrent tier.
• SERVICE_ALIVE — Checks the liveness of concurrent manager service processes registered in the FND tables, complementing PROCESS_ALIVE for service-level monitoring.
• MANAGER_CHECK — Performs a validation or consistency check against a concurrent manager's recorded configuration and runtime state.
• GET_PHASE — Returns the current phase of a concurrent request (for example, Pending, Running, Completed), translating the internal phase code into a usable value.
• GET_STATUS — Returns the status of a concurrent request, complementing GET_PHASE by exposing the disposition within a phase (Normal, Warning, Error, etc.).
• CANCEL_PATCH_REQUESTS — Cancels concurrent requests associated with an active patch/ADOP operation, allowing an administrator to abort in-flight jobs tied to patching.

Tables Accessed

ETRM records that FND_CONC references the following tables through APPS synonyms:

• FND_CONCURRENT_PROCESSES — Registry of concurrent manager and service processes; the source for liveness and manager-check logic.
• FND_CONCURRENT_PROGRAMS — Definitions of executable concurrent programs invoked by requests.
• FND_CONCURRENT_REQUESTS — The central request queue; used by GET_PHASE, GET_STATUS, and CANCEL_PATCH_REQUESTS.
• FND_CONC_PP_ACTIONS — Concurrent manager process/priority actions; consulted during manager processing.
• FND_CONC_STAT_SUMMARY — Concurrent processing throughput and statistics summary.
• FND_CONFLICTS_DOMAIN — Defines incompatibility domains that restrict which programs may run simultaneously.
• FND_USER — Application user definitions, used to attribute or authorize request activity.
• DATABASE_PROPERTIES — Database-level properties, often used to read the database name or instance identifiers during diagnostics.

Usage Notes

FND_CONC is an infrastructure-level package and is not intended as a public end-user API. It is invoked indirectly by the Concurrent Manager processes and by internal packages such as FND_CONC_SSWA (which supports the self-service concurrent manager administration screens) and FND_AMP_PRIVATE. The GET_PHASE and GET_STATUS utilities are also useful in custom SQL and PL/SQL when reporting on request disposition, though developers should prefer documented public APIs where available. Because the package relies on APPS synonyms and references SYS.STANDARD, it is installed and versioned with the core EBS application objects and behaves consistently across releases 12.1.1 and 12.2.2. Administrators and developers troubleshooting concurrent manager hangs, ICM failovers, or stuck patch jobs will typically encounter this package in trace files and diagnostic output rather than calling it directly.