Search Results dbms_scheduler




Overview
Explore in AI Chat

Overview

The ORACLE_OCM.MGMT_CONFIG package body belongs to the Oracle Configuration Manager (OCM) schema and provides the scheduling and execution infrastructure for automated configuration and statistics collection within an Oracle E-Business Suite environment. In EBS 12.1.1 and 12.2.2, OCM operates as a background telemetry mechanism that periodically gathers system configuration details and database statistics, transmitting them to Oracle Support for proactive diagnostics and inventory purposes. This package does not participate in any business transaction processing; it serves an operational and support-facing role, ensuring that configuration snapshots and statistics are captured on a predictable schedule without manual intervention. Because it resides in the ORACLE_OCM schema rather than APPS, it is isolated from the EBS application data model and is treated as infrastructure rather than functional logic. The package's principal responsibilities are to register DBMS_SCHEDULER jobs, verify their existence to prevent duplicate submissions, and expose entry points that collect configuration and statistics data on demand or on a recurring basis.

Key Procedures and Functions

The package exposes six documented program units. SUBMIT_JOB creates the two DBMS_SCHEDULER jobs used by OCM: MGMT_CONFIG_JOB, which runs daily at 01:01:01 to invoke COLLECT_CONFIG, and MGMT_STATS_CONFIG_JOB, which runs monthly on the first day at 01:01:01 to invoke COLLECT_STATS. The internal JOB_EXISTS function queries DBA_SCHEDULER_JOBS to detect prior registrations and raises RAISE_APPLICATION_ERROR errors (-20000 and -20001) if a job already exists, preventing duplicate scheduling. RUN_NOW triggers an immediate collection cycle, allowing an administrator to bypass the scheduled interval. STOP_JOB disables or terminates a currently registered collection job. PRINT_JOB_DETAILS emits diagnostic information about job status, presumably through DBMS_OUTPUT, to assist in troubleshooting. COLLECT_CONFIG performs the actual configuration snapshot, while COLLECT_STATS gathers database statistics. No parameter lists are documented, and the procedures should be invoked as published by Oracle rather than extended.

Tables Accessed

The package reads DBA_SCHEDULER_JOBS via its JOB_EXISTS function to determine whether a named job owned by ORACLE_OCM is already present. This is the sole query demonstrated in the source excerpt and is central to idempotent job registration. The metadata further lists DBMS_SCHEDULER, DBMS_OUTPUT, V$INSTANCE, and GV$INSTANCE as referenced objects. DBMS_SCHEDULER is the call interface used to create jobs; DBMS_OUTPUT supports the diagnostic printing performed by PRINT_JOB_DETAILS; and the V$INSTANCE and GV$INSTANCE dynamic performance views supply instance-level identification and status information used during collection, ensuring the gathered configuration is correctly attributed to the originating instance in Real Application Clusters configurations. Access is via APPS synonyms where applicable.

Usage Notes

In Oracle EBS 12.1.1 and 12.2.2, this package is not exposed through any standard EBS form and is not referenced by other PL/SQL packages, as confirmed by the zero referencing-package count. It is invoked exclusively by Oracle Configuration Manager itself, either through its scheduled DBMS_SCHEDULER jobs or through direct administrator calls during OCM installation, upgrade, or troubleshooting. DBAs may execute RUN_NOW, STOP_JOB, or PRINT_JOB_DETAILS manually to force a collection, halt an unwanted cycle, or inspect job health. With respect to the user's search concerning decimal precision for assemblies on work orders, this package has no bearing on that configuration; assembly quantity precision in EBS work orders is governed by the item's unit of measure precision and the applicable UOM and item attribute settings, not by any OCM collection logic.