Search Results ieo_svr_rt_info




Overview
Explore in AI Chat

Overview

IEO_SVR_RT_INFO is a table owned by the IEO schema within the Interaction Center Technology product family of Oracle E-Business Suite. Its documented purpose is to store real-time information about servers participating in an Interaction Center deployment. In EBS 12.1.1 and 12.2.2, this table functions as a runtime telemetry store that records the current operational state and load characteristics of each registered server node, complementing the more static server definitions held in IEO_SVR_SERVERS.

The Foreign Key relationships show that IEO_SVR_RT_INFO.SERVER_ID references IEO_SVR_SERVERS, and SECURITY_GROUP_ID references FND_SECURITY_GROUPS. Because the table is keyed on SERVER_ID and carries descriptive measures such as status and load factors, it is best understood as dependent, server-scoped data. The heuristic Data Vault classification derived from the FK structure is satellite-leaning; that is, the table behaves like a satellite attached to the IEO_SVR_SERVERS hub, with SERVER_ID acting as the effective parent key. This classification is a modeling suggestion only and should be validated against the actual ETRM data model for the target release.

Key Information Stored

The documented physical schema for 12.2.2 lists nine columns. The most significant are:

  • SERVER_ID — Surrogate primary key column of the IEO_SVR_RT_INFO_PK constraint, and the foreign key to IEO_SVR_SERVERS. It ties each real-time row to its parent server definition.
  • STATUS — Runtime status indicator for the server at the time of the record.
  • MAJOR_LOAD_FACTOR and MINOR_LOAD_FACTOR — Load measurements used to gauge the server's relative capacity or utilization.
  • LAST_UPDATE_DATE — Standard EBS audit column recording when the row was last modified.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the EBS framework to prevent concurrent update conflicts.
  • SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, restricting row visibility by security group.
  • NODE_ID — Identifier of the node associated with the server.
  • EXTRA — A generic attribute column reserved for additional runtime context.

The unique index IEO_SVR_RT_INFO_U1 on SERVER_ID reinforces SERVER_ID as the business-key candidate; no alternate unique business key beyond this is documented.

Common Use Cases and Queries

Typical uses center on monitoring Interaction Center server health. Administrators and reporting queries join this table to IEO_SVR_SERVERS to resolve server names while inspecting current status and load. A representative pattern:

  • Identifying loaded or overloaded servers: SELECT s.server_id, r.status, r.major_load_factor, r.minor_load_factor FROM ieo.ieo_svr_rt_info r JOIN ieo.ieo_svr_servers s ON s.server_id = r.server_id WHERE r.status = 'Y';
  • Listing servers updated within a window: SELECT * FROM ieo.ieo_svr_rt_info WHERE last_update_date > SYSDATE - 1;
  • Security-group filtered reporting: join on SECURITY_GROUP_ID to FND_SECURITY_GROUPS to constrain results by operating unit or group context.
  • Change tracking audits: use OBJECT_VERSION_NUMBER and LAST_UPDATE_DATE to detect concurrent modifications.

Related Objects

The principal related objects, drawn from the documented FK relationships, are:

  • IEO_SVR_SERVERS — parent table; join via IEO_SVR_RT_INFO.SERVER_ID = IEO_SVR_SERVERS.SERVER_ID.
  • FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for row-level security grouping.
  • IEO_SVR_RT_INFO_PK and IEO_SVR_RT_INFO_U1 — the primary key and unique index constraints enforcing SERVER_ID integrity.
  • IEO schema objects such as server configuration and node tables that consume NODE_ID and load-factor data for Interaction Center runtime decisions.

Because IEO_SVR_RT_INFO is closely coupled to IEO_SVR_SERVERS, any query or report should be authored with that join as the anchor, applying security-group predicates where multi-group access is configured.