Search Results patch_script

Overview

SYS.DBMS_REGISTRY_SYS is a core Oracle Database-supplied PL/SQL package that underpins the component registry used by Oracle E-Business Suite and the underlying RDBMS. In the Oracle EBS 12.1.1 and 12.2.2 environments, this package operates in the SYS schema and provides the low-level infrastructure that tracks database components, their versions, patch histories, and upgrade states. It is not an EBS application-level API; rather, it is a database utility that EBS relies upon during installation, patching, and upgrade operations, including the AD (Applications DBA) utilities and AutoConfig processes.

Key Procedures and Functions

The package exposes a broad set of documented procedures and functions (34 total) organized around registry maintenance, validation, and script resolution.

• Validation procedures: VALIDATE_CATALOG, VALIDATE_CATPROC, VALIDATE_CATJAVA, and VALIDATE_COMPONENTS confirm that catalog, catalog procedure, Java catalog, and component registrations are consistent and intact. VALIDATE_RDBMS_IN_UPGRADE_MODE and VALIDATE_RDBMS_IN_NORMAL_MODE verify that the database is in the correct operational mode before registry actions proceed.
• Timestamp functions: TIME_STAMP, TIME_STAMP_DISPLAY, and TIME_STAMP_COMP_DISPLAY return registry timestamps for a given component identifier, supporting diagnostics and status reporting.
• Script resolution functions: DBUPG_SCRIPT, DBDWG_SCRIPT, PATCH_SCRIPT, RELOD_SCRIPT, CPU_SCRIPT, and REMOVAL_SCRIPT return the names of scripts associated with upgrade, downgrade, patch, reload, CPU, and removal operations for registered components.
• Registry maintenance procedures: DROP_USER removes the registry user associated with a component; CHECK_COMPONENT_DOWNGRADES evaluates whether component downgrades are permissible; RECORD_ACTION logs an action with an identifier and comments; DIAGNOSTICS returns a numeric diagnostic result; GATHER_STATS collects statistics for a component; and POPULATE, POPULATE_92, POPULATE_101, and POPULATE_102 seed the registry tables for specific database releases.
• Property and context utilities: SELECT_PROPS_DATA, DELETE_PROPS_DATA, INSERT_PROPS_DATA, and UPDATE_PROPS_DATA manage registry property rows, while SET_REGISTRY_CONTEXT establishes context variables.
• Configuration file helpers: GET_PFILE_PATH, GEN_PFILE_FROM_MEMORY, UTLMMIG_SCRIPT_NAME, and DIR_EXISTS_AND_IS_WRITABLE assist with parameter file path resolution and migration scripting.

Tables Accessed

The documented ETRM metadata does not enumerate specific tables referenced through APPS synonyms. In practice, DBMS_REGISTRY_SYS reads and writes the underlying registry dictionary objects owned by SYS, including the registry component and registry properties tables that hold component identifiers, versions, status indicators, and timestamps. These are the data stores that the POPULATE and property-management routines maintain and that the validation and timestamp functions query.

Usage Notes

The package is invoked in a limited, tightly controlled manner. It is not intended for direct use by EBS application users or custom forms. Typical invocation occurs during database and EBS installation, upgrade, and patching cycles — for example, when the AutoUpgrade or OPatch tooling records component actions, resolves upgrade scripts, or validates catalog state. It is referenced by at least one other package and is called internally by registry tooling operating in the SYS schema. Administrators should treat it as an internal database utility: it should not be modified, and any invocation should follow Oracle-supported patching and upgrade procedures.