Search Results clone_schema_type

Overview

AD_CLONE_UTILS is a low-level PL/SQL utility package owned by the SYSTEM schema and shipped as part of the Oracle E-Business Suite database tier. Its principal business function is to support the Rapid Clone / AutoConfig schema-cloning infrastructure that underpins EBS patching, cloning, and multi-node deployment operations. In releases 12.1.1 and 12.2.2, the package provides the primitive operations required to create, synchronize, merge, and validate database schemas that participate in a clone operation, most notably the APPSCLONE and APPSSPEC schemas whose names are hard-coded into the package as constants (G_CLONE_SCHEMA_NAME and G_SPEC_SCHEMA_NAME). It also supplies diagnostic and logging helpers used by the AD utilities when recording clone progress. Because it manipulates schemas, synonyms, and object metadata directly, it is classified as an OTHER API in the ETRM repository rather than a public, supported interface.

Key Procedures and Functions

The package exposes fifteen documented routines. Several are diagnostic in nature: GET_DB_VERSION returns the database version from the instance, and PRINTLN writes timestamped or line-wrapped messages into the AD_GENERIC_TEMP table through the internal sequencing logic. PRINT_TIMESTAMP is referenced in the source excerpt as a companion logging helper.

The clone lifecycle operations are grouped as follows. CREATE_SCHEMA establishes a new schema, while CLONE_SCHEMA and CLONE_TABLE copy schema definitions or individual tables between environments. SYNC_SCHEMA and MERGE_SCHEMA reconcile a cloned schema against its source, and REPOINT_SYNONYMS redirects synonyms so that compiled objects resolve correctly in the new environment. VALIDATE_SCHEMAS is the documented validation entry point; the source excerpt shows an internal VALIDATE_SCHEMA worker routine that checks the schema type against the recognized constants SOURCE_SCHEMA_TYPE, CLONE_SCHEMA_TYPE, and SPEC_SCHEMA_TYPE, raising an application error for unrecognized values. This is the routine most relevant to the user search term "validate_schema".

Status and progress control are handled by GET_STATUS and IS_PHASE_COMPLETE, which report clone progress to the calling AD utility. Final cleanup is provided by CLEAN_UP, supported by the more granular CLEANUP_CHKFILE_INFO, CLEANUP_CLONE_SCHEMA, and CLEANUP_SPEC_SCHEMA procedures that remove temporary artifacts from each respective schema.

Tables Accessed

Through APPS synonyms, the package queries DBA_OBJECTS, DBA_SOURCE, DBA_SYNONYMS, DBA_TAB_COLUMNS, and DBA_TYPES to enumerate the objects, source text, columns, and types that must be replicated or validated. V$INSTANCE supplies the database version. FND_ORACLE_USERID is queried by the internal GET_SCHEMA_INFO function to determine the read_only_flag of a schema, which is critical before any modification. AD_GENERIC_TEMP is the sole write target visible in the package body, receiving sequenced log lines. DBMS_OUTPUT and PLITBLM are used for diagnostic output and PL/SQL table handling respectively.

Usage Notes

AD_CLONE_UTILS is not intended for direct invocation by end users or application forms. It is called internally by Rapid Clone scripts, AD utilities, and AutoConfig during schema-cloning and patching phases in 12.1.1 and 12.2.2. Custom code should treat it as an unsupported internal API. The search term "validate_schema" corresponds to the internal validation worker routine documented here; the publicly listed equivalent is VALIDATE_SCHEMAS. Any custom integration should reference VALIDATE_SCHEMAS and be aware that the package operates on privileged SYSTEM-schema objects and hard-coded clone schema names.