Search Results get_domain_index_metadata
Overview
DBMS_EXPORT_EXTENSION is a SYS-owned PL/SQL package that forms part of Oracle's Data Pump and legacy Export/Import infrastructure. It resides in the SYS schema, holds a VALID status, and is classified under the ETRM taxonomy as an "OTHER" API, reflecting its role as an internal database utility rather than a business-facing application program interface. Although documented and present within the EBS 12.1.1 and 12.2.2 technology stack, the package is not an EBS product module. Its principal function is to support the export and import of complex, non-standard schema objects — most notably domain indexes and their associated metadata — that standard export utilities cannot handle through generic mechanisms alone. In the Oracle E-Business Suite context, DBMS_EXPORT_EXTENSION matters because EBS schemas contain numerous domain indexes created by Oracle Text, Oracle Spatial, and similar extensible components, and the transportability of these objects across environments depends on the callbacks provided by this package. It is effectively the extension hook through which export and import clients obtain object source, object comments, and domain index definitions, and through which they coordinate event handling during import operations.
Key Procedures and Functions
The ETRM metadata documents 32 procedures and functions, of which the following are enumerated:
- PRE_TABLE and POST_TABLES — lifecycle hooks invoked around table processing during export operations, allowing dependent objects to be prepared before and consolidated after table-level work.
- GET_DOMAIN_INDEX_METADATA — retrieves metadata describing a domain index so that the export dump can capture the index definition accurately.
- GET_OBJECT_SOURCE — returns the source text of a schema object, enabling export utilities to capture definitions not otherwise accessible.
- GET_DOMAIN_INDEX_TABLES and GET_V2_DOMAIN_INDEX_TABLES — return the underlying tables associated with a domain index; the V2 variant supports the newer metadata representation.
- BEGIN_IMPORT_DOMAIN_INDEX — signals and initiates domain index import processing.
- INSERT_SECOBJ — inserts security object information as part of import handling.
- CHECK_MATCH_TEMPLATE — validates or matches templates, typically associated with metadata comparison during import.
- GET_OBJECT_COMMENT — retrieves the comment text for a schema object so that comments are preserved in dumps.
- Event control routines — SET_IMP_EVENTS, SET_HAKAN_EVENT, SET_SECONDARYOBJ_EVENT, RESET_SECONDARYOBJ_EVENT, SET_IOT_EVENT, SET_EXP_OPQ_TYP_EVENT, and RESET_EXP_OPQ_TYP_EVENT toggle internal event flags that govern behaviors such as index-organized table handling, secondary object processing, and opaque type export.
- Session configuration routines — SET_NO_OUTLINES, SET_NLS_NUMERIC_CHAR, and RESET_NLS_NUMERIC_CHAR temporarily alter session-level export settings and restore them afterward.
Tables Accessed
The documented metadata for this object lists no tables accessed through APPS synonyms, which is consistent with its location in the SYS schema and its dependence on internal data dictionary views and fixed tables rather than on EBS application tables. Its export and import routines operate against dictionary metadata such as object definitions, comments, and index descriptors sourced through internal SYS structures. Custom EBS code should therefore not expect this package to expose application data; any dependency on it is structural, arising from the physical organization of index and LOB segments within the EBS schema set.
Usage Notes
DBMS_EXPORT_EXTENSION is invoked indirectly, chiefly by Oracle Data Pump (expdp/impdp) and the legacy exp/imp clients, when those utilities encounter extensible objects requiring specialized handling. It is not exposed through EBS forms, concurrent programs, or Oracle Applications menus, and it carries no application-level profile options. The ETRM metadata notes that the package references only SYS and STANDARD internally, while it is itself referenced by DBMS_EXPORT_EXTENSION and DBMS_EXPORT_EXTENSION_I, and it is referenced by one other package. In practice, EBS administrators encounter the package in clone, migration, and schema-refresh scenarios, particularly when transporting Oracle Text or Spatial indexes. Because it is an Oracle-supplied SYS component, it must not be modified, wrapped, or called directly by custom code. Any errors surfacing from it during export or import — such as ORA-39126 or ORA-06512 traces naming DBMS_EXPORT_EXTENSION — should be treated as symptoms of dump-level or metadata inconsistency and resolved through Oracle Support guidance rather than by altering the package itself.