Results for “status_name”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

SYS.DBMS_REGISTRY is the Oracle Database-supplied registry package that governs the lifecycle state of every registered database component, including the Oracle E-Business Suite database tier and its associated schemas (such as APPS, ABM, and the product-specific schema owners). Within the Oracle EBS 12.1.1 and 12.2.2 environments, this package provides the authoritative mechanism by which individual components are loaded, validated, upgraded, downgraded, and removed, and through which their current status is reported. In practice it is the bookkeeping layer that the EBS AutoConfig, AD Utilities (adpatch, adadmin), and Rapid Install/upgrade driver scripts consult and update during installation, patching, and upgrade cycles. Because EBS 12.2.x adopts the Online Patching (adop) model with editioning and a physical standby-aware architecture, DBMS_REGISTRY plays an even larger role in coordinating component status across the primary and patch editions.

The ETRM classification lists this object as an OTHER-type API owned by SYS. The reference to "NJE" in the search context reflects Oracle's internal notation used in the registry's status strings — most notably the state labels documented below — rather than a distinct public API.

Key Procedures and Functions

The package exposes 68 documented routines. The principal public ones include:

  • SET_SESSION_NAMESPACE / SET_COMP_NAMESPACE — Establish the namespace context (session-level and component-level, respectively) under which subsequent registry operations execute. These are prerequisites for many other calls.
  • SET_RDBMS_STATUS / SET_RDBMS_UPGRADED_STATUS — Write the current RDBMS component status and its upgraded status into the registry.
  • INVALID / VALID — Mark a component as invalid or valid, controlling whether dependent components may proceed.
  • LOADING / LOADED — Transition a component through the loading phase during installation or patch application.
  • UPGRADING / UPGRADED / DOWNGRADING / DOWNGRADED — Manage direction-of-change state during EBS upgrades and downgrades.
  • REMOVING / REMOVED — Mark and confirm component removal.
  • OPTION_OFF — Record that a component option is disabled.
  • STARTUP_REQUIRED / STARTUP_COMPLETE — Signal that a startup action is pending or has completed.
  • RESET_VERSION — Reset a component's recorded version.
  • UPDATE_SCHEMA_LIST — Refresh the schema membership list associated with a component.
  • STATUS_NAME — Return the human-readable status name for a component/state pair.

Parameter lists are intentionally not enumerated here; the reader should consult the wrapped source or Oracle support documentation for exact signatures.

Tables Accessed

Although ETRM does not expose the internal synonym list, DBMS_REGISTRY reads and writes the underlying registry tables in the SYS schema (principally REGISTRY$ and its dependent views such as DBA_REGISTRY, ALL_REGISTRY, and USER_REGISTRY). These tables store one row per registered component, capturing the component ID, namespace, version, status code, and last-modified metadata. Because DBMS_REGISTRY is owned by SYS, any EBS reference passes through SYS-granted privileges rather than APPS synonyms.

Usage Notes

DBMS_REGISTRY is invoked automatically, not by end users. It is exercised by EBS installation, adpatch, adadmin, AutoConfig, and the 12.2 adop cycle, which set a component to LOADING, apply changes, then to LOADED or UPGRADED. In 12.2.x, the online patching driver invokes these routines in both the run and patch editions to keep component status synchronized. Custom code should query DBA_REGISTRY rather than call DBMS_REGISTRY for status, and should not invoke its status-altering procedures outside an Oracle-sanctioned patching or upgrade workflow, as doing so can corrupt the component registry and break subsequent EBS maintenance operations.