Search Results update_types

Overview

AD_ZD_PREP is an internal Oracle E-Business Suite patching and Online Patching support package, owned by the APPS schema and classified under the OTHER API classification. Its name derives from the "AD" (Applications DBA) product prefix combined with "ZD" (the Online Patching / editioning infrastructure introduced in EBS 12.2) and "PREP," indicating its role as a preparation utility. The package body orchestrates preparatory work performed against the database prior to or during the application of an Online Patch. This includes manipulating editioned database objects, recompiling and evolving user-defined types, and repairing supporting objects such as queues, synonyms, and XML schemas that must be consistent for a patch cycle to complete successfully.

The metadata records this package as failing to compile completely in the environment from which the ETRM extract was taken. The exception log lists PLS-00302 errors stating that components RECOMPILE_TYPES, UPDATE_TYPES (twice), and SPLIT_SOURCE must be declared, each accompanied by "PL/SQL: Statement ignored." The SPLIT_SOURCE reference occurs at line 1020. These errors indicate the package body references identifiers that are absent from the compiled specification or its dependencies, a condition frequently observed where a package body version is out of step with its specification during or after an upgrade. Because the documented package compiles with these errors, functional behavior of the affected code paths cannot be guaranteed until the body is recompiled against a matching specification.

Key Procedures and Functions

The ETRM metadata documents 29 procedures and functions. Representative entries include:

• IS_TYPE_EVOLVED / IS_TYPE_EXISTS — Predicate functions that test whether a database type has been evolved or exists, used to condition type-repair logic.
• CREATE_PATCH_SERVICE — Creates the database service used by the patching infrastructure.
• MOVE_XML_SCHEMAS — Relocates XML schema registrations as part of patching preparation.
• DO_PREP — The main orchestration entry point that drives the preparation steps.
• RECOMPILE_TYPES — Recompiles user-defined types; note that this component is reported as undeclared.
• DROP_TEMP_QUEUES / DROP_QUEUES / STOP_QUEUE — Manage Advanced Queueing objects during patching.
• ENABLE_EDITIONS / ENABLE_USER_4EDITION — Enable editioning and edition-enable the relevant schema user.
• FIX_PUBLIC_SYNONYMS / FIX_PUBLIC_SYNONYM — Repair public synonyms affected by patching.
• COPY_TYPES / COPY_TYPE / COPY_EVOLVED_TYPES / COPY_EVOLVED_TYPE — Copy and evolve type definitions.
• FIX_TYPES / FIX_TYPE — Repair type definitions following evolution.
• RECREATE_AQ_OBJECT — Recreates Advanced Queueing objects.

No parameter lists are documented; the descriptions above reflect purpose only.

Tables Accessed

The package queries data dictionary views through APPS synonyms rather than application tables. Documented references include DBA_OBJECTS, DBA_DEPENDENCIES, and DBA_INVALID_OBJECTS for object and dependency status; DBA_TYPES and DBA_TAB_COLUMNS for type structure; DBA_USERS and FND_ORACLE_USERID for schema and user identity; DBA_SYNONYMS for synonym repair; DBA_QUEUES and DBA_QUEUE_TABLES for AQ management; DBA_VIEWS, DBA_MVIEWS, DBA_TABLES, DBA_SERVICES, and DBA_XML_SCHEMAS for services, schemas, and relational object inspection.

Usage Notes

AD_ZD_PREP is invoked internally by the AD Online Patching driver and is not intended for direct end-user or custom-application calls. It is triggered during patch application and patching preparation phases, and because it touches editioning, type evolution, and queue infrastructure, it must run in the APPS schema with DBA-level privileges. The recorded compile errors (RECOMPILE_TYPES, UPDATE_TYPES, SPLIT_SOURCE) should be resolved by recompiling the package body against its correct specification before relying on preparation logic. Referenced by zero other packages, it is a leaf dependency in the patching chain.