Search Results fnd_ops_instances_u1

Overview

APPLSYS.FND_OPS_INSTANCES is an Oracle E-Business Suite configuration table that registers the application-tier service instances available to the concurrent processing infrastructure. Its documented role is to identify each Oracle Parallel Server or Real Application Clusters instance by number and by associated service name, and to flag whether the Conflict Resolution Manager (CRM) or the concurrent Scheduler is permitted to connect to that instance. The table resides in the APPS_TS_ARCHIVE tablespace with a PCT Free of 20, is owned by APPLSYS, and is designated Oracle Internal Use Only; Oracle Corporation does not support direct access except from standard Oracle Applications programs. In Oracle EBS 12.1.1 and 12.2.2 the object is shipped as part of the FND design data (FND.FND_OPS_INSTANCES) and remains VALID.

From a dimensional modeling perspective, the mined relationship data suggests classifying FND_OPS_INSTANCES as a link-style reference entity: it carries a surrogate business identifier, configuration attributes, and Standard Who audit references to FND_USER and FND_LOGINS, but no foreign keys descending from dependent transactional tables.

Key Information Stored

The table documents thirteen columns. The most significant are:

• INSTANCE_NUMBER (NUMBER, mandatory) — the Oracle Parallel Server instance number. This is both the primary key (FND_OPS_INSTANCES_PK) and the business-key candidate enforced by unique index FND_OPS_INSTANCES_U1 on the APPS_TS_ARCHIVE tablespace. Because the primary key and the unique index cover the same single column, the surrogate and business key coincide.
• SERVICE_NAME (VARCHAR2 255) — the primary service name of the instance.
• PRIMARY_SERVICE_NAME (VARCHAR2 255) — the primary service name associated with the instance record.
• SECONDARY_SERVICE_NAME (VARCHAR2 255) — the secondary service name of the instance, used where failover or a supplementary listener service is configured.
• ENABLED (VARCHAR2) — a Y/N flag indicating whether the Conflict Resolution Manager or Scheduler may connect to this instance.
• STATUS (VARCHAR2) and DESCRIPTION (VARCHAR2 255) — operational state and free-text annotation for the instance.
• TIME_STAMP (DATE) — recorded timestamp for the instance record.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the Standard Who audit columns. LAST_UPDATED_BY and CREATED_BY reference FND_USER, while LAST_UPDATE_LOGIN references FND_LOGINS.

Common Use Cases and Queries

Administrators and concurrent-processing specialists query this table to determine which instances are eligible to host the CRM or the concurrent Scheduler, to correlate instance numbers with listener service names during RAC node additions or removals, and to audit when instance eligibility was last changed. A representative query listing enabled instances and their service names is:

• SELECT INSTANCE_NUMBER, SERVICE_NAME, PRIMARY_SERVICE_NAME, SECONDARY_SERVICE_NAME, ENABLED, STATUS FROM APPLSYS.FND_OPS_INSTANCES WHERE ENABLED = 'Y';
• SELECT INSTANCE_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY FROM APPLSYS.FND_OPS_INSTANCES ORDER BY INSTANCE_NUMBER;
• SELECT i.INSTANCE_NUMBER, u.USER_NAME FROM APPLSYS.FND_OPS_INSTANCES i, APPLSYS.FND_USER u WHERE i.LAST_UPDATED_BY = u.USER_ID;

The documented query text projects all thirteen columns from APPLSYS.FND_OPS_INSTANCES. Reporting use is generally limited to DBA-level diagnostics and concurrent manager configuration reviews, since the object is internal-use only.

Related Objects

• APPS.FND_OPS_INSTANCES — the APPS synonym that references this table; it is the only documented dependent object.
• APPLSYS.FND_USER — joined via CREATED_BY and LAST_UPDATED_BY to resolve the user who created or last modified an instance record.
• APPLSYS.FND_LOGINS — joined via LAST_UPDATE_LOGIN to trace the login session associated with the last update.
• FND_OPS_INSTANCES_PK and FND_OPS_INSTANCES_U1 — the primary key constraint and unique index, both keyed on INSTANCE_NUMBER.
• Concurrent processing configuration objects (for example the concurrent manager and Scheduler definitions maintained through standard Oracle Applications programs) consume the ENABLED flag indirectly.

No database object is documented as referenced by FND_OPS_INSTANCES other than the FND_USER and FND_LOGINS audit joins.