Search Results oracle_ocm_config_dir

Overview

ORACLE_OCM.MGMT_CONFIG_UTL is a utility package owned by the ORACLE_OCM schema and shipped as part of the Oracle Configuration Manager / Management Configuration infrastructure embedded in the Oracle E-Business Suite technology stack. In EBS 12.1.1 and 12.2.2, the database tier relies on this package to maintain the directory object that points the configuration-collection tooling at the correct file system location after an ORACLE_HOME change. Its single documented procedure, CREATE_REPLACE_DIR_OBJ, recreates the directory object ORACLE_OCM_CONFIG_DIR so that its path reflects the current ORACLE_HOME, ensuring that configuration metadata continues to be written and read from a valid location after cloning, relocation, or an upgrade of the database home.

The package is classified as OTHER under the ETRM API classification scheme, indicating that it is an internal Oracle-maintained utility rather than a supported public application programming interface. It is not part of the EBS application schema set and does not participate in the business data model.

Key Procedures and Functions

• CREATE_REPLACE_DIR_OBJ — The sole documented procedure. It creates or replaces the directory object used by ORACLE_OCM so that the stored path is regenerated against the new ORACLE_HOME. The procedure is declared AUTHID CURRENT_USER, meaning it executes with invoker's rights rather than definer's rights. According to the package comments, this design choice is deliberate: it avoids the need to grant EXECUTE on the DBMS_SYSTEM package directly to the ORACLE_OCM user. Only SYS can invoke the procedure without error, because SYS already holds the privilege required to execute DBMS_SYSTEM and to recreate the ORACLE_OCM_CONFIG_DIR directory object, which is owned by that account.

No parameters are documented for this procedure in the ETRM metadata; its behavior is entirely derived from the environment of the invoker and the current ORACLE_HOME setting. No other procedures or functions are exposed by the package specification.

Tables Accessed

The ETRM metadata records two fixed views referenced through APPS synonyms: V$DATABASE and V$INSTANCE. These are standard SYS-owned dynamic performance views. In the context of this package they are used to establish database identity and instance context when the configuration directory object is created or refreshed, so that the generated path and associated configuration data are correctly associated with the running database and instance rather than a stale or unrelated environment. The package does not read or write any EBS application tables.

Usage Notes

MGMT_CONFIG_UTL is invoked at the database tier, typically during or immediately after operations that alter the ORACLE_HOME path, such as cloning an EBS database environment, relocating a database home, applying a technology-stack patch that changes the home location, or performing an upgrade between EBS releases. In practice it is called by Oracle-supplied configuration or post-install scripts under the SYS account, since the invoker's-rights model documented in the package header explicitly restricts successful execution to SYS.

The package is not intended for direct invocation from EBS forms, concurrent programs, or custom application code. Because it is undocumented in the public EBS API surface and its behavior depends on DBMS_SYSTEM privileges and the physical home layout, custom code should not call it directly; the supported path is to rely on the Oracle-provided configuration scripts. In EBS 12.2.2, where the database tier may be hosted separately from the application tier and the online patching file system introduces additional directory structure, the importance of maintaining an accurate ORACLE_HOME path for the configuration directory remains relevant, and this package continues to serve as the internal mechanism for that maintenance. Administrators should verify that the creating session runs as SYS and that DBMS_SYSTEM is available, since the procedure requires the GET_ENV capability supported from database release 10.2 onward.