Search Results fnd_nodes




Overview
Explore in AI Chat

Overview

The FND_NODES table is a core repository within the Oracle E-Business Suite Application Object Library (FND). It serves as the master registry for all physical and logical server nodes, or machines, that constitute an EBS deployment. Its primary role is to define and manage the topology of the application's technology stack, enabling the system to identify where specific services, such as concurrent managers and application tier services, are installed and executed. This table is fundamental to the operation and administration of a multi-node EBS environment, providing the necessary reference for job routing, service discovery, and system configuration across both releases 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is centered on identifying and characterizing each node. The primary key, NODE_NAME, uniquely identifies a server within the Applications context. While the full column list is not detailed in the provided metadata, based on its described purpose, it typically stores critical configuration data for each node. This commonly includes the server's network address (HOST_NAME, DOMAIN), the physical operating system path for application binaries and log files (APPL_TOP, LOG_DIRECTORY), and status indicators controlling whether the node is active for processing concurrent requests. The NODE_NAME column is the central reference point used by numerous other concurrent processing tables.

Common Use Cases and Queries

Administrators interact with FND_NODES for system monitoring, troubleshooting, and reporting. Common operational queries include listing all configured nodes and checking the assignment of concurrent managers. For example, to identify which nodes are active and running concurrent managers, a DBA might execute a join with FND_CONCURRENT_PROCESSES. Another critical use case is during the cloning process or when adding a new application tier node, where entries must be correctly populated or updated in this table. Reporting on the distribution of concurrent requests across the node topology often requires queries joining FND_NODES with FND_CONCURRENT_REQUESTS on the various node name columns (NODE_NAME1, NODE_NAME2, OUTFILE_NODE_NAME) to trace where a request was processed and where its output resides.

Related Objects

As indicated by the foreign key relationships, FND_NODES is heavily referenced by the core concurrent processing tables, forming the backbone of the job execution framework. The documented foreign keys show dependencies from:

  • FND_CONCURRENT_PROCESSES: Links managers to their execution node.
  • FND_CONCURRENT_QUEUES: Associates manager work shifts with specific nodes.
  • FND_CONCURRENT_REQUESTS: References nodes for the execution and output of individual jobs (via NODE_NAME1, NODE_NAME2, LOGFILE_NODE_NAME, OUTFILE_NODE_NAME).
  • FND_CONC_PROG_ONSITE_INFO: Tracks node-specific information for concurrent programs.
This web of relationships underscores that FND_NODES is a pivotal parent table for managing the distributed processing architecture of Oracle E-Business Suite.