Search Results collect_config

Overview

The ORACLE_OCM.MGMT_CONFIG package is a component of Oracle Configuration Manager (OCM), the framework Oracle uses to collect and transmit configuration and inventory information from Oracle software installations. In an Oracle E-Business Suite environment running release 12.1.1 or 12.2.2, this package operates within the ORACLE_OCM schema and provides the database-side interface for scheduling and executing configuration collection jobs. Its business purpose is to gather metadata about the Oracle database instance, including initialization parameters, installed components, and runtime environment characteristics, which together describe the relationship between the Oracle Base and Oracle Home configuration of the EBS database tier. This information supports Oracle Support diagnostics, proactive health checks, and the My Oracle Support (MOS) configuration repository.

Key Procedures and Functions

The package exposes six documented procedures, each serving a distinct role in the configuration collection lifecycle:

• SUBMIT_JOB — Creates and schedules the configuration collection job using DBMS_SCHEDULER, defining the execution parameters that determine what metrics are gathered and where the collection output is written.
• RUN_NOW — Triggers the configuration collection job immediately rather than waiting for the next scheduled interval, allowing on-demand diagnostics.
• STOP_JOB — Terminates an active or scheduled configuration collection job, providing administrators control over resource consumption.
• PRINT_JOB_DETAILS — Emits information about the collection job's status, parameters, and scheduling state, typically through DBMS_OUTPUT.
• COLLECT_CONFIG — Executes the core configuration collection logic, gathering database and environment metadata relevant to OCM reporting.
• COLLECT_STATS — Performs statistics collection, capturing performance and instance-level metrics for transmission to Oracle.

Tables Accessed

The package does not read or write EBS application tables. Instead, it relies on the following data dictionary and dynamic performance views, referenced through APPS synonyms:

• DBA_SCHEDULER_JOBS — Read to verify job existence, confirm scheduling state, and support the PRINT_JOB_DETAILS and STOP_JOB logic.
• DBMS_SCHEDULER — The PL/SQL package used to create, run, and drop the underlying scheduler job objects.
• DBMS_OUTPUT — Used to emit diagnostic and job-detail output to the client.
• V$INSTANCE and GV$INSTANCE — Queried to capture instance-level identification and status, providing the fundamental Oracle Home and instance context for the collected configuration.

Usage Notes

MGMT_CONFIG is not intended for direct invocation from EBS forms or standard concurrent programs. It is typically invoked internally by the Oracle Configuration Manager collection engine, or manually by a DBA during a support engagement, for example when Oracle Support requests an immediate configuration upload. In R12.1.1 and R12.2.2 deployments, the ORACLE_OCM user and its objects are provisioned automatically during database creation and are subject to maintenance via OCM patches. Because the package is referenced by no other documented packages, its execution surface is self-contained. DBAs should treat the procedures as administrative utilities, invoke RUN_NOW sparingly to avoid load during peak operating windows, and consult the OCM logs in the collection directory when PRINT_JOB_DETAILS output indicates job failure.