Search Results dbms_csx_admin




Overview
Explore in AI Chat

Overview

XDB.DBMS_CSX_ADMIN is an Oracle-supplied administrative package that forms part of the XML DB (XDB) infrastructure shipped with the Oracle database on which Oracle E-Business Suite 12.1.1 and 12.2.2 are deployed. Its principal business function is the administration of token table sets — the internal repository structures that XML DB uses to store and index tokenized XML path, QName, and namespace identifiers. These token tables are fundamental to the performance of XMLType storage and XMLIndex operations, and their correct registration and maintenance is a prerequisite for any EBS module that persists or queries XML documents, including Oracle Payments, iProcurement, and various interface and integration flows.

Although owned by the XDB schema rather than by APPS, the package is exposed to EBS through the standard APPS synonym layer, allowing DBAs and support engineers to invoke it from the EBS database tier. It is classified as an OTHER API within ETRM, reflecting its role as a database-vendor administrative utility rather than a business-facing EBS API.

Key Procedures and Functions

The package declares ten documented procedures and functions. The following are the most significant:

  • REGISTERTOKENTABLESET — Registers a token table set by inserting a corresponding entry into XDB$TTSET and, where required, creating the associated token tables and their indexes. It accepts parameters controlling the target tablespace or table number, the globally unique identifier of the token table set, the registration level (table, tablespace, or no registration), the extent of physical object creation, and whether default token mappings are inserted.
  • COPYDEFAULTTOKENTABLESET — Copies the default token table set into a specified tablespace, enabling new tablespaces to inherit the standard token mappings used by XML DB.
  • GETTOKENTABLEINFO — Returns metadata describing the token tables associated with a given token table set.
  • GETTOKENTABLEINFOBYTABLESPACE — Returns equivalent token table metadata resolved by tablespace rather than by token table set identifier.
  • PATHIDTABLE, QNAMEIDTABLE, NAMESPACEIDTABLE — Utility functions that resolve the physical token table names used for path identifier, QName identifier, and namespace identifier tokenization respectively.
  • INSTANCE_INFO_EXP — Exposes instance-level information pertinent to the XML DB token repository.
  • GATHERTOKENTABLESTATS — Gathers optimizer statistics on the token tables, supporting stable execution plans for XML queries.

Tables Accessed

The package operates against a defined set of data dictionary and XDB-internal objects, referenced through APPS synonyms. It reads USER_TABLESPACES and USER_USERS to resolve the current schema's tablespace and user context. DBMS_ASSERT is used to validate dynamically constructed identifiers, protecting against SQL injection during dynamic DDL. DBMS_DATAPUMP and DBMS_PRIV_CAPTURE are leveraged for export/import and privilege capture operations connected with token table management, while DBMS_STATS and KU$_STATUS support statistics gathering and status reporting. PLITBLM serves as the PL/SQL table intermediate layer used internally by these utilities. The persistent token data itself resides in XML DB internal tables such as XDB$TTSET together with the underlying token tables that the package creates and maintains.

Usage Notes

DBMS_CSX_ADMIN is not invoked from EBS forms or concurrent programs. It is typically executed by database administrators during XML DB installation, patch application, tablespace reorganization, or performance tuning of XML-intensive EBS functionality. Regeneration of token tables and statistics gathering are common remedial actions when XML query performance degrades or when XML DB objects are migrated between tablespaces. Because the package executes dynamic DDL and operates on XDB-internal structures, execution should be restricted to SYS or other highly privileged accounts, and standard change-control procedures — including a validated backup — should precede any invocation in a production EBS 12.1.1 or 12.2.2 environment.