Search Results tablefunc_asown




Overview
Explore in AI Chat

Overview

CTXSYS.DRVDISP is an Oracle Text (interMedia Text) dispatch package owned by the CTXSYS schema. It provides the low-level "trust callout" infrastructure that Oracle Text uses to invoke external (non-PL/SQL) routines, typically operating-system executables or user-defined C routines, in a synchronous manner. Within the Oracle EBS 12.1.1 and 12.2.2 environments, this package is not an Applications-owned object; it is delivered as part of the standard CTXSYS schema installed by the database, and it is present in both the 11g and 12c Oracle Text codebase that EBS runs against.

The business function of DRVDISP is to act as a controlled gateway between the Oracle Text indexing engine and "trusted" callout programs. These external routines are registered by an administrator in the Oracle Text index metadata, and DRVDISP executes them when a document is indexed, filtered, or otherwise processed. The functions prefixed with EXECTRUST implement the synchronous trust callout command, while the EXECASOWN family executes callouts under a different (as-owner) privilege context. The package is one of the most heavily reused CTXSYS components, referenced by 26 other packages according to the ETRM classification metadata.

Key Procedures and Functions

The documented package exposes 13 procedures and functions, all of which are callout-dispatch entry points:

  • EXECTRUST — synchronous trust callout command; invokes a registered callout with up to ten optional arguments, returning no value.
  • EXECTRUST_RET — synchronous trust callout command with two return values (ret1, ret2) in addition to the argument list.
  • EXECTRUST_RET1 — synchronous trust callout command returning a single VARCHAR2 value and accepting up to ten optional arguments.
  • EXECTRUST_ARRAY — synchronous trust callout command supporting array-valued arguments for multi-valued callouts.
  • EXECASOWN — executes a callout under "as owner" (definer's rights) semantics rather than current user.
  • EXECASOWN_CLOB — as-owner callout variant that passes a CLOB argument.
  • EXECASOWN_IN_CLOB — as-owner callout accepting an input CLOB.
  • EXECASOWN_IN_OUT_CLOBS — as-owner callout accepting and returning CLOB data.
  • EXECASOWN_IN_CLOB_RET — as-owner callout taking an input CLOB and returning a value.
  • EXECASOWN_RET — as-owner callout with two return values.
  • EXECASOWN_RET1 — as-owner callout returning a single value.
  • TABLEFUNC — dispatches a callout that returns a table/collection result.
  • TABLEFUNC_ASOWN — the as-owner variant of TABLEFUNC.

The common parameters across these routines are idx_owner, idx_name, part_name, and func_code, which together identify the target index, its partition, and the specific callout function code being invoked.

Tables Accessed

The ETRM metadata for this package does not list any tables referenced through APPS synonyms, which is consistent with its role as a dispatch/plumbing package rather than a business-data accessor. Any index metadata it consults resides in CTXSYS-owned dictionary tables (such as the Oracle Text index tables) rather than in EBS Application Object Library tables. Custom code should therefore not assume that DRVDISP touches EBS base tables, nor should it attempt to join through this package to EBS data.

Usage Notes

CTXSYS.DRVDISP is invoked indirectly, not from EBS forms or concurrent programs directly. It is called by the Oracle Text engine when a domain index with a registered trust callout is created, synchronized, or queried. In EBS 12.1.1 and 12.2.2 it surfaces in contexts such as Oracle Text-based searches, interMedia index maintenance, and any custom workflow or concurrent manager job that rebuilds a Text index invoking a user-supplied filter or lexer. Because these routines execute privileged "trusted" code with broad filesystem/database access, administrators should treat DRVDISP as a security-sensitive interface: execute privileges on EXECTRUST and the EXECASOWN family should be granted only to trusted CTXSYS users and the Application Object Library accounts that legitimately own Text indexes. Direct grants to end-user or custom application schemas are not recommended, and any use in custom PL/SQL should be limited to controlled index maintenance routines where the target callout has been reviewed and approved.