Search Results fnd_concurrent_processes




Overview
Explore in AI Chat

Overview

The FND_CONCURRENT_PROCESSES table is a core technical table within the Application Object Library (FND) module of Oracle E-Business Suite (EBS). It functions as the system of record for tracking the active operating system and database processes associated with the concurrent processing framework. Its primary role is to maintain a real-time mapping between logical concurrent manager processes, their physical database sessions (SID), and their corresponding operating system process identifiers (PID). This mapping is essential for system administration, performance monitoring, and troubleshooting the health and activity of concurrent managers in both EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is designed to link process identifiers with their managing entities and execution context. The primary key is CONCURRENT_PROCESS_ID, which uniquely identifies each manager process instance. Critical foreign key columns establish relationships to other central concurrent processing tables: QUEUE_APPLICATION_ID and CONCURRENT_QUEUE_ID link the process to its parent concurrent queue definition in FND_CONCURRENT_QUEUES. The SESSION_ID column links to the active database session in FND_SESSIONS, while NODE_NAME references the application tier node from FND_NODES where the process is running. Other significant columns include the OPERATING_PROCESS_ID (OS PID) and ORACLE_PROCESS_ID (SPID), which are vital for correlating EBS activity with database and server-level metrics.

Common Use Cases and Queries

This table is frequently queried for operational monitoring and diagnostic purposes. A common use case is identifying runaway or long-running manager processes by joining with session and OS performance views. Administrators often use it to find which specific manager process is executing a given concurrent request by joining with FND_CONCURRENT_REQUESTS on the CONTROLLING_MANAGER column. Sample queries include listing all active internal manager processes with their OS PIDs, or diagnosing a non-responsive manager by checking if its session is still active in the database.

  • Sample Query: Active Processes with OS Details
    SELECT fcp.concurrent_process_id, fcp.concurrent_queue_name, fcp.operating_process_id, fs.sid, fs.serial# FROM apps.fnd_concurrent_processes fcp, apps.fnd_sessions fs WHERE fcp.session_id = fs.session_id AND fcp.process_status_code = 'A';

Related Objects

As indicated by its foreign keys, FND_CONCURRENT_PROCESSES has integral relationships with several key FND tables. It is a child table of FND_CONCURRENT_QUEUES, which defines the manager queues. It references FND_SESSIONS for database session information and FND_NODES for the tier topology. Crucially, it is referenced as a parent table by FND_CONCURRENT_REQUESTS via the CONTROLLING_MANAGER column, creating the link between a running request and the specific manager process executing it. This network of relationships positions FND_CONCURRENT_PROCESSES as a central hub for concurrent processing metadata.