Results for “node_mode”

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

Overview

FND_OAM_FNDNODES_VL is a view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the FND (Application Object Library) product family and exposes node-level configuration data that Oracle Applications Manager (OAM) uses to describe the servers, hosts, and middleware tiers registered in an EBS environment. The view is defined over the FND_NODES base table and carries a "VL" suffix, indicating it presents a translated or validated list-style projection of node records rather than a pure physical table.

In practice, FND_OAM_FNDNODES_VL functions as a reporting and integration surface for administrators, database administrators, and monitoring tools that need to enumerate the application tier nodes and their declared capabilities. Because it is a view and not a table, it inherits the security and consistency characteristics of its underlying base object while allowing OAM and third-party integrations to query node metadata without touching the base table directly.

The SUPPORT_FORMS column, which appears in the documented view text, is the attribute most commonly searched by administrators investigating Oracle Forms Services availability. It records whether a given node advertises support for the Forms runtime, and is frequently joined against other FND OAM views to map Forms servers to their hosting nodes.

Underlying Base Objects

The ETRM documentation for release 12.2.2 records a single referenced base object for this view: FND_NODES, accessed through a synonym. Every column projected by FND_OAM_FNDNODES_VL originates from that base table. The view text selects from FND_NODES and returns identifiers, audit columns, platform descriptors, and a set of support flags — SUPPORT_CP, SUPPORT_FORMS, SUPPORT_WEB, SUPPORT_ADMIN, and SUPPORT_DB — that describe the roles a node is permitted to perform.

No additional joins to lookup tables, node configuration tables, or OAM repository tables are documented in the extracted view definition. Consequently, the view is effectively a column-projected, readability-oriented facade over FND_NODES rather than a denormalized aggregation. Systems that already hold SELECT privileges on the base table will see the same row population unless row-level or schema-level security restricts access.

Key Columns

• NODE_NAME — The logical name of the application tier or database tier node as registered in FND_NODES.
• PLATFORM_CODE — The hardware or operating system platform identifier for the node.
• SUPPORT_FORMS — Flag indicating whether the node supports Oracle Forms Services. Central to any query investigating Forms server distribution.
• SUPPORT_CP, SUPPORT_WEB, SUPPORT_ADMIN, SUPPORT_DB — Companion flags declaring support for concurrent processing, the web tier, administration services, and the database tier respectively.
• STATUS — Current status of the node record.
• HOST, DOMAIN, WEBHOST — Physical host name, network domain, and web host alias used for URL and connectivity resolution.
• NODE_MODE — Mode in which the node operates, distinguishing tiers or deployment roles.
• DESCRIPTION — Free-text description maintained by administrators.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard EBS auditability. The ROWID is exposed as ROW_ID.

Common Use Cases and Queries

The primary practical use is auditing which nodes support Forms, especially during upgrades from 12.1.1 to 12.2.2 where the introduction of the WebLogic-managed application tier changes node topology. A representative query is:

SELECT node_name, host, domain, platform_code, node_mode, status
FROM   apps.fnd_oam_fndnodes_vl
WHERE  support_forms = 'Y'
ORDER  BY node_name;

A second common scenario enumerates all nodes and their support matrix, useful for capacity reviews and for confirming that at least one node carries SUPPORT_ADMIN or SUPPORT_DB:

SELECT node_name, support_forms, support_web, support_cp,
       support_admin, support_db
FROM   apps.fnd_oam_fndnodes_vl;

Because the view is a thin projection of FND_NODES, queries may be extended with joins to FND_NODES or to other OAM views using NODE_NAME as the correlation key. Access should be granted through the APPS schema or via a custom synonym, and responsibility-level security policies in production environments should be reviewed before exposing results to non-administrative users.