Results for “ieo_icsm_node_pub”

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

Overview

The APPS.IEO_ICSM_NODE_PUB package is a public PL/SQL API within the Oracle E-Business Suite Internet Computing Server (ICS) / iSupport infrastructure layer. Its role is administrative rather than transactional: it provides a programmatic entry point for removing all node definitions registered in the EBS deployment. Nodes, in this context, represent the application-tier or server-tier machines (web nodes, forms nodes, concurrent processing nodes, and similar ICS-managed servers) that participate in a distributed EBS installation. The package header carries the standard AUTHID CURRENT_USER declaration, meaning that any executing caller invokes the affected DML under its own schema privileges rather than those of the package owner, which is consistent with APPS-owned public APIs that must be run under the EBS application context.

The package is deliberately narrow in scope. The packaged source identifies it as ieonodes.pls, version 115.0, last modified in February 2003, which indicates that it is a legacy utility retained for backward compatibility across the 12.1.1 and 12.2.2 releases rather than a functional component that has evolved with the product line. Its stated business purpose, per the embedded comment, is to purge all node records after cloning.

Key Procedures and Functions

The ETRM metadata documents exactly one public procedure for this package:

• DELETE_ALL_NODES — Removes every node row from the ICS node registration tables. The procedure is a bulk cleanup routine with no selective filtering: it is intended to be invoked when the entire node inventory must be cleared, most notably immediately after a database or application-tier clone produces a duplicate or stale set of node records. Because the runtime signature is not part of the documented metadata, callers should not assume any parameters; the procedure is a standalone, no-argument cleanup operation.

No functions, overloads, or additional procedures are documented. The package body contains only the implementation of this single entry point.

Tables Accessed

Although the package body itself is not reproduced in the ETRM excerpt, the documented referenced tables identify the transactional footprint of the delete operation. All access occurs through APPS synonyms:

• IEO_NODES — The primary node registry; the driving table that holds one row per registered ICS node. DELETE_ALL_NODES truncates or deletes this table's contents first or last depending on dependency order.
• IEO_NODE_ADDRS — Address and connectivity details for each node, deleted as a dependent child of IEO_NODES.
• IEO_SVR_NODE_ASSIGNMENTS — The mapping between servers and nodes; removed so that no orphaned assignments remain after the node purge.
• IEO_SVR_NODE_RT_INFO — Runtime information associated with server-node combinations, cleared to prevent stale runtime data from being reapplied to newly created nodes.

Together these four tables constitute the complete ICS node configuration model. The delete sequence must respect referential relationships, which explains why the API groups them into a single unit of work instead of exposing separate delete calls.

Usage Notes

Because the package is an APPS-owned public API with no documented dependents (referenced by zero other packages), it is not part of any internal call chain and is expected to be invoked explicitly by an administrator or a controlled script. Typical invocation scenarios include:

• Post-clone cleanup — The primary intended use. After cloning an EBS environment, the cloned database inherits node records that point to the source system's hostnames and services. Running APPS.IEO_ICSM_NODE_PUB.DELETE_ALL_NODES from SQL*Plus, a SQL script, or a custom concurrent program clears that inherited configuration so the cloned environment can re-register its own nodes.
• Custom code or installation scripts — Third-party or Oracle-supplied scripts that rebuild the ICS topology may call this procedure as a preparatory step before re-inserting corrected node definitions.
• Diagnostic and recovery tasks — When node records become corrupted or duplicated, administrators may use this API as a reset mechanism.

Callers should ensure the APPS schema is initialized (via FND_GLOBAL.APPS_INITIALIZE or an equivalent session setup) before execution, and should recognize that the operation is destructive and unconditional. No row-level filtering is offered; partial deletions require direct DML against the underlying tables. Given the package's vintage, organizations on 12.2.2 should treat it as a supported legacy utility rather than a modern feature-rich API.