Search Results mgr_name

Overview

APPS.OAM_GCS is a server-side PL/SQL package body that supports the Oracle Applications Manager (OAM) Generic Collection Service (GCS) infrastructure within Oracle E-Business Suite. Its principal business function is to programmatically register, configure, and maintain the concurrent manager service instances that OAM uses to collect diagnostic, runtime, and forms runtime information from application tier nodes. These registered service instances appear as specialized concurrent managers of type "OAMGCS" and upload collected data at a defined interval. The package therefore bridges OAM's data-collection framework with the standard concurrent processing architecture, ensuring that each targeted node has a correctly named, correctly parameterized collector manager.

Key Procedures and Functions

The documented API surface consists of five procedures and functions, classified as OTHER:

• REGISTER_OAMGCS_FCQ — Registers a service instance for a specified node. It constructs the manager name by prefixing "OAMGCS_" to the uppercased node name, truncates it to a 30-byte limit, and assembles a service-parameter string (NODE, LOADINTERVAL, RTI_KEEP_DAYS, FRD_KEEP_DAYS, ORACLE_HOME, FORMS60_RTI_DIR). It checks for an existing queue on the node before inserting, and resolves a display name from FND message lookup.
• UPDATE_GCS — Updates the configuration of an existing GCS service registration, allowing parameters such as the load interval or node-specific paths to be revised.
• DELETE_GCS — Removes a previously registered GCS service instance, cleanly decommissioning the collector from the concurrent manager configuration.
• SERVICE_EXISTS — Boolean-style function returning whether a GCS service registration already exists, used to guard against duplicate registrations.
• SERVICE_STATUS — Reports the operational status of a registered GCS service, enabling administrators to confirm whether the collector is active.

Tables Accessed

The package operates primarily against the concurrent processing data model, referencing the following tables through APPS synonyms:

• FND_CONCURRENT_QUEUES — The core concurrent manager definition table; queried by node name and manager type, and the source of the OAMGCS manager registration.
• FND_CONCURRENT_QUEUES_S — The sequence source used to obtain a unique suffix when a manager-name collision is detected.
• FND_CONCURRENT_QUEUES_TL — Stores translated (language-specific) queue names and descriptions.
• FND_CONCURRENT_QUEUE_SIZE — Holds worker-process sizing information for the manager.
• FND_CP_SERVICES — The service registry that maps the "OAMGCS" service handle to its numeric service ID, used to filter queues by manager type.
• DUAL — Used for sequence and utility evaluations.

Usage Notes

Operator or administrator action, rather than direct end-user invocation, normally drives OAM_GCS. It is typically called from Oracle Applications Manager's administrative pages or from concurrent-program and registration routines that provision a new collector manager when an application tier node is added or reconfigured. The parameter profile shows a default load interval of 300000 milliseconds (five minutes), with retention defaults of one day for RTI data and seven days for FRD data. Because the documented metadata indicates zero referencing packages, OAM_GCS is effectively a top-level entry point called by forms or administrative scripts rather than a shared library. The "mgr_name" local variable and its 30-byte truncation logic reflect the FND_CONCURRENT_QUEUES naming constraint, so custom callers must expect manager names to be shortened and, on collision, suffixed with a generated sequence value. All deployment should respect the APPS schema ownership and standard EBS patching conventions.