Results for “remove_system”

8 results




Overview
Explore in AI Chat

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

Overview

FND_NET_SERVICES is an Oracle E-Business Suite repository package that maintains the topology metadata describing the application tier and database tier nodes belonging to an EBS system. It is the programmatic layer through which the EBS AutoConfig and system registration infrastructure records server definitions, database instances, Oracle home registrations, TNS alias information, and node role assignments into the FND foundation tables. The package is declared AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the calling schema rather than the definer, which allows it to be invoked from contexts where the caller already holds the necessary grants on the underlying FND tables.

In EBS 12.1.1 and 12.2.2, the package underpins the registration of the multi-tier architecture: the database node, the application node, and the mappings between them. The searched term register_dbnode identifies the primary entry point used to declare a database tier node to the EBS system, capturing identifying details such as the system name, server name, owner, CSI number, database name, instance name and number, listener port, service name, host and domain, Oracle home details, interconnect name, instance SID, platform, and optional virtual host and alternate service instance information.

Key Procedures and Functions

  • REGISTER_DBNODE — Registers a database tier node with the EBS system, recording the database identity, instance identity, listener and service configuration, host, domain, Oracle home attributes, cluster and interconnect details, platform, and optional virtual host and alternate service instance values.
  • REGISTER_APPNODE — Registers an application tier node, capturing server and system ownership, host and domain, RPC port, primary and auxiliary Oracle home paths, versions and names, APPL_TOP path and name, shared APPL_TOP designation, and the derived instance aliases (Tools, Web, SID default, JDBC SID) returned as out parameters. Boolean-style flags indicate whether the node acts as a Forms node, a concurrent processing node, a Web node, and an Admin node.
  • REMOVE_DBNODE — Removes a previously registered database node definition.
  • REMOVE_APPNODE — Removes a previously registered application node definition.
  • REMOVE_SERVER — Removes a server (host) definition from the system configuration.
  • REMOVE_SYSTEM — Removes an EBS system definition and its associated registrations.
  • SHOW — Displays or returns the currently registered network services configuration.
  • SHOW_TNSALIAS — Displays or returns TNS alias information registered for the EBS system.

Tables Accessed

The package reads and writes the core FND configuration tables that model an EBS system. FND_APPS_SYSTEM and FND_NODES hold the system-level and per-node records. FND_DATABASES, FND_DATABASE_INSTANCES, FND_DATABASE_SERVICES, FND_DB_SERVICE_MEMBERS, FND_SIDS, and FND_ORACLE_HOMES capture database, instance, service membership, SID, and Oracle home detail for the database tier. FND_APP_SERVERS, FND_APPL_TOPS, FND_SYSTEM_SERVER_MAP, and FND_DATABASE_ASSIGNMENTS capture application tier servers, APPL_TOP definitions, and the mapping of servers to systems and databases. FND_TNS_ALIASES, FND_TNS_ALIAS_ADDRESSES, and FND_TNS_ALIAS_ADDRESS_LISTS store TNS alias and address information.

Usage Notes

FND_NET_SERVICES is not normally invoked directly by end users. It is called by AutoConfig-driven registration logic during the configuration and reconfiguration of an EBS system, and by administrative routines that add or remove application nodes, database nodes, servers, or complete systems. The REMOVE_* procedures are used when decommissioning nodes or systems. SHOW and SHOW_TNSALIAS are diagnostic helpers useful for verifying the stored topology. The package is referenced by no other documented packages, so custom code should call it explicitly when programmatically auditing or repairing EBS node registration data, and should treat it as an internal foundation API whose behavior is tied to the AutoConfig toolset.