Search Results update_objlink_stats




Overview
Explore in AI Chat

Overview

SYS.DBMS_PDB is an Oracle-supplied database package that provides the programmatic interface for managing Pluggable Databases (PDBs) within a Container Database (CDB) architecture. In the Oracle E-Business Suite context, it is relevant primarily because EBS 12.2.2 introduced support for the multitenant option, and this package underpins the operations that Oracle EBS uses to maintain an EBS PDB. The package is declared with AUTHID CURRENT_USER, meaning that its procedures execute with the privileges of the invoking user rather than the definer, and several of its routines are explicitly documented as being for internal Oracle use only. Within EBS, DBMS_PDB supports the lifecycle operations of describing, validating, synchronizing, and recovering a PDB, as well as maintaining the metadata linkage between the PDB and the CDB root.

Key Procedures and Functions

Fourteen procedures and functions are documented for this package in the ETRM 12.2.2 metadata. The public-facing routines include:

  • DESCRIBE — Generates an XML file describing the tablespaces and datafiles belonging to a pluggable database. The PDB name may be supplied, or the currently connected PDB is described by default; an error results if no name is given while connected to the root.
  • CHECK_PLUG_COMPATIBILITY — Determines whether a PDB described by a given XML file is compatible with the current CDB.
  • EXEC_AS_ORACLE_SCRIPT — Enables execution of certain restricted statements, most notably DDL against metadata-linked objects, from within a PDB by running the statement with the internal _oracle_script parameter set to TRUE. Documented as intended for Oracle internal packages only.
  • CLEANUP_TASK — Removes leftover artifacts associated with a completed or failed PDB operation such as a clone or unplug.
  • SYNC_PDB — Synchronizes the PDB with the CDB, propagating root-level metadata changes.
  • RECOVER — Performs recovery of a PDB, typically recovering a PDB from a standby or resuming a failed operation.
  • UPDATE_CDBVW_STATS, UPDATE_COMDATA_STATS, UPDATE_OBJLINK_STATS — Refresh statistics and internal metadata associated with CDB views, common data, and object links respectively. These are the routines most closely tied to the UPDATE_VERSION keyword surfaced in user searches.
  • UPDATE_VERSION — Updates the version stamp recorded for the PDB within the CDB, ensuring the PDB reports the correct Oracle version and patch level during upgrades and post-patch synchronization.
  • NONCDB_TO_PDB — Converts a non-container (traditional single-instance) database into a pluggable database, a prerequisite step when migrating a pre-12.2.2 EBS database into a CDB.
  • CREATEX$PERMANENTTABLES — Creates the internal X$ permanent link tables used to back metadata-linked objects in the PDB.
  • DROPX$PERMANENTTABLES — Drops those X$ permanent tables, reversing the preceding operation.
  • POPULATESYNCTABLE — Populates the internal synchronization table used to drive the metadata-link refresh process between CDB root and PDB.

Tables Accessed

The ETRM metadata does not record any application-level tables accessed via APPS synonyms. DBMS_PDB operates almost entirely against internal fixed tables (X$ views), internal dictionary views such as CDB_* and DBA_PDB_* families, and the X$ permanent tables it creates through CREATEX$PERMANENTTABLES. These tables exist to support metadata-linked object definitions shared between the CDB root and its PDBs, which is the mechanism EBS 12.2.2 relies on to keep the APPS schema consistent across containers.

Usage Notes

DBMS_PDB is not intended for direct invocation by EBS application developers. It is classified in ETRM as OTHER and is called internally by two other documented packages, reflecting its role as infrastructure supporting multitenant operations. In practice it is invoked during activities such as database cloning, PDB creation from a non-CDB, post-patch synchronization of an EBS PDB, standby recovery, and version reconciliation after applying patches. Because EXEC_AS_ORACLE_SCRIPT and the X$ table routines are restricted to Oracle internal use, custom code should never call these procedures directly. Where a version-related refresh is required, DBMS_PDB.UPDATE_VERSION is executed as part of Oracle-supplied upgrade and maintenance scripts rather than from EBS forms or concurrent programs.