Results for “cpu_usage”

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

Overview

FND_OAM_FORMS_RTI is a runtime metadata table in the Oracle E-Business Suite Application Object Library (FND) product family, owned by the APPLSYS schema. Its name reflects its purpose: the FND_OAM prefix associates it with the Oracle Applications Manager (OAM) monitoring framework, FORMS identifies the Forms Listener tier, and RTI denotes runtime information. The table captures a point-in-time snapshot of Forms Listener runtime processes, allowing administrators and OAM dashboards to observe which Forms sessions are active, on which nodes and ports they are running, and how much memory and CPU each process consumes.

In EBS 12.1.1 the Forms Listener is typically a standalone process managed on the application tier; in 12.2.2, the Forms server topology remains fundamentally similar but is commonly administered through a WebLogic-managed environment. In both releases, FND_OAM_FORMS_RTI provides the underlying data for OAM diagnostic pages such as the Forms Runtime Monitor. The table is classified as VALID and holds 14 documented columns in the 12.2.2 physical schema.

The ETRM metadata assigns this object a heuristic Data Vault classification of standalone. As a modeling suggestion, this implies the table is not treated as a hub, link, or satellite in a formal Data Vault model; it is a self-contained snapshot/state table. Its single-column primary key, RTI_ID, makes it a natural candidate for an insertion-only or periodically truncated operational table rather than a dimension-bearing entity.

Key Information Stored

The table is governed by two unique indexes: the primary key constraint FND_OAM_FORMS_RTI_PK and the unique index FND_OAM_FORMS_RTI_U1, both defined on RTI_ID. RTI_ID is therefore the sole documented surrogate primary key and business-key candidate. It is a system-generated identifier that uniquely distinguishes each captured Forms runtime record.

• RTI_ID – Surrogate primary key; unique identifier for each runtime snapshot row.
• CONCURRENT_QUEUE_ID – Identifier of the concurrent queue associated with the Forms runtime process.
• QUEUE_APPLICATION_ID – Application identifier qualifying the concurrent queue; together with CONCURRENT_QUEUE_ID it anchors the process to a specific queue definition.
• PID – Operating-system process ID of the Forms Listener child process, useful for correlating the record with OS-level tools.
• THREADID – Internal thread identifier within the Forms process, distinguishing multiple sessions handled by one listener.
• IPADDRESS – Client or host IP address associated with the runtime process.
• NODE – The application-tier node on which the Forms process executes.
• PORT – The network port bound by the Forms Listener or process, enabling connection tracing.
• USERNAME – The EBS user logged into the Forms session.
• CONNECT_TIME – Timestamp when the user session connected, supporting session-duration analysis.
• MEM_USAGE – Memory consumed by the process, in the units recorded by OAM.
• CPU_USAGE – CPU consumed by the process, used for load and performance trending.
• FILENAME – The Forms executable or resource file name associated with the process.
• LAST_UPDATE_TIME – Timestamp of the most recent refresh of the row, identifying snapshot freshness.

Common Use Cases and Queries

The primary use case is Forms runtime monitoring. Administrators query this table to identify long-running or resource-heavy Forms sessions, to detect blocked or orphaned processes, and to report on concurrent user load per node. Typical patterns include:

• Listing the most recent snapshot per user or node, ordering by LAST_UPDATE_TIME.
• Aggregating MEM_USAGE and CPU_USAGE by NODE to spot overloaded application tiers.
• Joining NODE and PORT to connection descriptors to trace which listener served a given session.
• Computing session duration from CONNECT_TIME to LAST_UPDATE_TIME for capacity reporting.
• Filtering by PID to correlate an EBS session with an operating-system process for troubleshooting.

A representative query selects RTI_ID, USERNAME, NODE, PORT, PID, MEM_USAGE, CPU_USAGE, and LAST_UPDATE_TIME, filtering on the current snapshot timestamp. Because the table is a snapshot store, reports should join to the latest LAST_UPDATE_TIME to avoid mixing stale records.

Related Objects

The metadata classifies FND_OAM_FORMS_RTI as standalone, meaning no foreign keys are documented pointing into or out of it. The following related objects are the most significant in practice:

• FND_CONCURRENT_QUEUES – Referenced conceptually through CONCURRENT_QUEUE_ID and QUEUE_APPLICATION_ID to resolve queue definitions.
• FND_APPLICATION – Resolves QUEUE_APPLICATION_ID to an application name.
• FND_USER – Provides the identity behind the USERNAME column.
• FND_NODES – Supplies authoritative node metadata for the NODE column.
• FND_OAM_FORMS_RTI_PK / FND_OAM_FORMS_RTI_U1 – The primary key constraint and unique index over RTI_ID.
• OAM Forms monitoring pages – The Oracle Applications Manager UI reads this table to render runtime diagnostics.

Related OAM runtime tables (such as Forms session or metrics stores) may share the RTI lifecycle and should be consulted for a complete runtime picture.