Search Results cutover_indexes

Overview

AD_ZD_TABLE is an Oracle E-Business Suite database package owned by the APPS schema that forms part of the Online Patching (Edition-Based Redefinition) infrastructure introduced in EBS 12.2. Its central business function is to manage the physical database objects — tables, views, columns, indexes, and materialized views — that are created, revised, and cut over during an online patch cycle. Rather than operating a database in a conventional single-state manner, EBS 12.2 maintains multiple editions of the same logical object so that users can continue transacting against the run edition while a patch is applied to the patch edition. AD_ZD_TABLE provides the programmatic primitives that let the patching engine determine whether a given object exists in a specific edition, create or revise it, and later finalize or drop it once the cutover completes.

Key Procedures and Functions

The documented interface exposes 23 procedures and functions, classified generically as OTHER. The existence-check family includes EV_EXISTS, EV_VIEW, EV_TABLE, EV_VIEW_COLUMN, EV_TABLE_COLUMN, and EV_TABLE_COLUMN_REVISION; these interrogate the data dictionary to confirm whether a table, view, column, or revised column already exists in the target edition. IS_SEED identifies seed (reference) data objects, distinguishing them from transactional or customer-owned data. The core lifecycle procedures are UPGRADE and UPGRADE_DB, which build the patch-edition copy of an object and its dependent structures, and DOWNGRADE, which reverses these changes. DROP_TABLE removes physical tables during cleanup. Index management is handled by REVISED_INDEX_NAME, REVISED_INDEX_REGEXP, ORIGINAL_INDEX_NAME, ORIGINAL_INDEX_REGEXP, REVISE_INDEXES, and CUTOVER_INDEXES, which together rename, rebuild, and switch indexes between the original and revised naming conventions. The final group — PATCH, APPLY, and FINALIZE — coordinates the transition of an object from the patch edition into the run edition, completing the adoption of the revised definition.

Tables Accessed

AD_ZD_TABLE reads and writes a focused set of data dictionary and EBS metadata tables through APPS synonyms. AD_PATCHED_TABLES and AD_OBSOLETE_OBJECTS record which tables have been patched and which are obsolete. FND_PRODUCT_INSTALLATIONS supplies product installation status, allowing the package to scope its work to installed applications. The DBA_* views — DBA_CONSTRAINTS, DBA_CONS_COLUMNS, DBA_DEPENDENCIES, DBA_EDITIONING_VIEWS, DBA_EDITIONING_VIEW_COLS, DBA_INDEXES, DBA_IND_COLUMNS, DBA_MVIEWS, DBA_OBJECTS, DBA_POLICIES, DBA_QUEUE_TABLES, and DBA_SYNONYMS — provide the structural metadata the package inspects when deciding how to build or revise an object. These are the authoritative sources for column lists, index definitions, editioning view properties, and dependency chains that govern whether an operation is safe.

Usage Notes

AD_ZD_TABLE is infrastructure-level code and is not intended for direct invocation by end users or by ordinary customizations. It is called by the AD Online Patching driver (ADZD) and by related internal packages, and is referenced by AD_MO_UTIL_PKG, AD_OBSOLETE_PRODUCTS, AD_UTIL, AD_ZD, AD_ZD_MVIEW, AD_ZD_PREP, and AD_ZD_SEED. In practice it is exercised automatically during the patch, apply, and cutover phases of online patching in EBS 12.2.2, and its procedures may also be called by Oracle-supplied scripts executing in the patch edition session. Custom development should not depend on this package because its interface and behavior are controlled by Oracle and may change between patch levels; developers who need edition-aware behavior should rely on documented AD_ZD facilities rather than calling AD_ZD_TABLE directly.