Search Results add_pending

Overview

CTXSYS.DRIIMP is an Oracle Text (interMedia) import utility package that ships with the CTXSYS schema. Its role in Oracle E-Business Suite 12.1.1 and 12.2.2 is to reconstruct Oracle Text index metadata inside the data dictionary during an import operation, such as a database-level import (imp/impdp), a transportable tablespace operation, or a clone that copies Oracle Text objects between environments. Rather than re-creating the index from scratch, DRIIMP inserts the catalog rows that describe an existing text index — index attributes, partition definitions, object mappings, and preference values — into the DR$ dictionary tables. In an EBS context this is significant because Oracle Text indexes underpin functionality such as the Attachments search, Knowledge Management (Knowledge Base) document search, and iStore/CRM text lookups. When these schemas are migrated, DRIIMP ensures the index metadata travels with the data.

Key Procedures and Functions

The ETRM metadata documents eight procedures in the DRIIMP package, all of which are catalog-population routines invoked during import rather than during normal runtime query processing:

• CREATE_INDEX — Populates DR$INDEX with the defining attributes of a text index during import, excluding the generated ID, owner, and status columns which are supplied by the import process itself.
• CREATE_PARTITION — The procedure matched by the user's search term. It inserts rows into DR$INDEX_PARTITION during import, taking a partition ID, partition name, document ID counts, next ID values, and optional synchronization settings (sync type, memory, parallel degree, interval). It is the partition-level counterpart to CREATE_INDEX.
• SET_OBJECT — Inserts rows into DR$INDEX_OBJECT, associating a class name (the object or column being indexed) with the index definition.
• SET_VALUE — Writes index-level preference values into the Oracle Text dictionary, preserving non-default preference settings across the import.
• SET_SUB_VALUE — Writes subordinate (nested) preference values, used where a preference such as a lexer or datastore itself contains sub-attributes.
• ADD_PENDING — Registers pending (unindexed or partially indexed) rows so that the imported index can be synchronized correctly after the import completes.
• ADD_CDICOL — Adds a column to the Change Data Capture / incremental index tracking definition, supporting DML-aware text index maintenance.
• ADD_USER_EXTRACT_RULE — Registers user-defined extraction rules that govern how document content is parsed into indexable tokens.

Tables Accessed

The only table documented via APPS synonyms is DUAL, which is unsurprising for a CTXSYS-owned package: DUAL appears in the metadata simply as a generic reference, while the true targets of DRIIMP are the Oracle Text dictionary tables DR$INDEX, DR$INDEX_PARTITION, DR$INDEX_OBJECT, and the preference tables referenced by SET_VALUE and SET_SUB_VALUE. These tables do not normally surface as APPS synonyms because they reside in the CTXSYS schema and are accessed through direct Oracle Text internal calls rather than through EBS application synonyms.

Usage Notes

DRIIMP is not intended for direct invocation by EBS forms, concurrent programs, or custom application code. It is called internally by Oracle's import utilities when the export dump contains Oracle Text indexes and the importing session has sufficient privileges over CTXSYS objects. In practice, an EBS 12.1.1 or 12.2.2 DBA encounters DRIIMP only indirectly — through errors surfaced during impdp/imp of a schema that owns Oracle Text indexes — most commonly ORA-06508, ORA-04063 (package body has errors), or CTX-level errors caused by an invalid or incomplete DRIIMP package body after a CTXSYS upgrade. Remediation is normally to re-run the Oracle Text catalog scripts (e.g., catctx.sql) or apply the relevant CTX patch, not to call DRIIMP manually. Because the package body is wrapped and owned by CTXSYS, changes to its signature or availability should be treated as an Oracle-supplied upgrade concern.