Search Results delete_gcs

Overview

APPS.OAM_GCS is a technical PL/SQL package within Oracle E-Business Suite that manages the registration, configuration, and monitoring of Oracle Application Manager (OAM) Generic Collection Services (GCS) for the Oracle Concurrent Manager infrastructure. The package, whose header comment identifies it as afamgcss.pls (version 120.1, dated 2005), is declared AUTHID CURRENT_USER, meaning that its database operations execute under the privilege set of the calling user rather than the package owner. Its central purpose is to maintain the binding between a concurrent manager node and the collection service that gathers diagnostic and performance data, and to expose that binding status programmatically.

In the 12.1.1 and 12.2.2 releases, this package is closely associated with the FND concurrent processing schema. The Generic Collection Service concept supports centralized monitoring of concurrent manager health and throughput, and OAM_GCS functions as the administrative interface through which such services are created, modified, or removed. The package declares a single public variable, ServiceExists (boolean), and five documented program units.

Key Procedures and Functions

• REGISTER_OAMGCS_FCQ — Registers a Generic Collection Service for a concurrent manager node, associating the node with its Oracle home, an RTI directory location, and a polling or sampling interval. It is the entry point for establishing a new service definition.
• UPDATE_GCS — Modifies the configuration attributes of an existing registered service, such as the node, Oracle home, RTI directory, or interval. It parallels REGISTER_OAMGCS_FCQ in parameter intent but operates on an existing service record.
• DELETE_GCS — Removes a registered collection service for a specified node, cleaning up the associated configuration.
• SERVICE_EXISTS — A function that reports whether a collection service is defined for a given node, returning a character result. It allows callers to test for prior registration before attempting an update or delete.
• SERVICE_STATUS — A function that returns the numeric status of the collection service for a given node. This is the object most relevant to the search term "service_status"; it provides a programmatic health check on the registered service.

No parameter lists beyond those documented should be assumed; callers should consult the package specification in the target environment.

Tables Accessed

The package reads and writes primarily through APPS synonyms over the FND concurrent manager tables:

• FND_CONCURRENT_QUEUES and its _S (security) and _TL (translation) variants — the core definition of concurrent managers and their associated information.
• FND_CONCURRENT_QUEUE_SIZE — governs the worker process sizing for a manager, relevant to service registration and interval behavior.
• FND_CP_SERVICES — the concurrent processing services repository where service definitions are likely persisted.
• DUAL — used for single-row lookups and function return evaluations.

Usage Notes

OAM_GCS is a low-level administrative utility rather than a public business API. It is typically invoked by Oracle Application Manager components, concurrent manager administration forms, or setup scripts that provision monitoring services for a node. The ETRM metadata records that no other packages reference it directly, indicating it is called externally — from forms logic, concurrent programs, or custom diagnostic scripts — rather than through internal package dependencies. Custom code that needs to verify whether a collection service is active for a node can call SERVICE_STATUS or SERVICE_EXISTS, and administration utilities may call REGISTER_OAMGCS_FCQ, UPDATE_GCS, or DELETE_GCS during environment setup or migration. Because the package runs AUTHID CURRENT_USER, invoking sessions must hold the necessary privileges on the underlying FND tables.