Results for “last_monitored_time”

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

Overview

FND_NODES is the Oracle E-Business Suite Applications Object Library table that registers the servers, hosts, and machines used to install and run an Oracle EBS environment. It is owned by the APPLSYS schema and identified by the primary key constraint FND_NODES_PK on the NODE_NAME column. In a 12.1.1 or 12.2.2 deployment, every middle-tier, concurrent-processing, and database-tier node that participates in the application topology is expected to appear here as a row. This makes FND_NODES the authoritative registry of node identity and node capability against which the concurrent manager infrastructure validates job placement, log file locations, and on-site program execution.

From a data-modeling perspective, the mined relationship structure suggests FND_NODES behaves as a hub rather than a link or satellite. It has no foreign keys pointing outward; instead, it is referenced by multiple dependent tables through the NODE_NAME column. The heuristic Data Vault classification of "hub-leaning" reflects this: NODE_NAME is a durable business key, and the surrounding descriptive attributes are largely stable reference data describing the node. A dependent satellite would naturally carry the mutable monitoring attributes such as STATUS and LAST_MONITORED_TIME.

Key Information Stored

The documented physical schema contains 26 columns. The most functionally significant are the following.

• NODE_NAME — the primary key and the business key enforced by unique index FND_NODES_U1. It is the value stored in every referencing foreign key column across the concurrent processing tables.
• NODE_ID and SERVER_ID — surrogate identifiers used internally and by the Admin/Server infrastructure.
• PLATFORM_CODE — the operating system platform for the node, used to select compatible concurrent programs.
• DESCRIPTION — a human-readable description of the node.
• BASEPATH — the base filesystem path on the node, relevant to log and output file resolution.
• SUPPORT_CP, SUPPORT_FORMS, SUPPORT_WEB, SUPPORT_ADMIN, SUPPORT_DB — capability flags indicating whether the node supports concurrent processing, Forms, web, administration, or database services.
• STATUS, PING_RESPONSE, LAST_MONITORED_TIME, NODE_MODE — operational state and monitoring attributes maintained by the node monitoring and ping services.
• SERVER_ADDRESS, HOST, DOMAIN, WEBHOST, VIRTUAL_IP — network addressing and hostname identity attributes.
• APPLTOP_ID — identifier relating the node to its application topology entry.

Standard audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) are also present.

Common Use Cases and Queries

FND_NODES is most frequently queried to enumerate active application nodes, to filter nodes by supported service, and to resolve log or output file locations for concurrent requests. A typical enumeration of nodes supporting concurrent processing is:

• SELECT node_name, platform_code, status, support_cp FROM fnd_nodes WHERE support_cp = 'Y';

Because log and output files are stored on the node defined in FND_CONCURRENT_REQUESTS, a common reporting query joins the request table back to the node registry to determine where a given concurrent request produced its files:

• SELECT r.request_id, r.node_name1, r.logfile_node_name, r.outfile_node_name, n.status FROM fnd_concurrent_requests r, fnd_nodes n WHERE r.logfile_node_name = n.node_name;

Administrators also use the monitoring columns to audit node health, comparing PING_RESPONSE and LAST_MONITORED_TIME to detect nodes that have stopped responding. Because the concurrent processing and administration framework both depend on this registry, discrepancies between configured nodes and rows in FND_NODES are a frequent source of concurrent manager startup and job execution failures.

Related Objects

FND_NODES is referenced by several dependent tables through the NODE_NAME column, forming the join path to the concurrent processing infrastructure.

• FND_CONCURRENT_PROCESSES — joins on NODE_NAME, identifying the node running each concurrent process.
• FND_CONCURRENT_QUEUES — joins on NODE_NAME, defining which nodes may service a given concurrent queue.
• FND_CONCURRENT_REQUESTS — joins on four separate columns: NODE_NAME1, NODE_NAME2, LOGFILE_NODE_NAME, and OUTFILE_NODE_NAME.
• FND_CONC_PROG_ONSITE_INFO — joins on NODE_NAME1 and NODE_NAME2, controlling where on-site programs may run.

Together these relationships make FND_NODES the central reference point for node-based routing of concurrent programs and for resolving the physical location of request output and log files.