Search Results sdo_join




Overview
Explore in AI Chat

Overview

MDSYS.SDO_IDX is an Oracle Spatial index maintenance package owned by the MDSYS schema. In the context of Oracle E-Business Suite 12.1.1 and 12.2.2, this package is part of the Oracle Spatial and Graph option shipped with the Oracle Database, and is surfaced within EBS because several applications — most notably Oracle Field Service, Oracle Inventory, and Oracle Property Manager — store spatial data using the SDO_GEOMETRY datatype and rely on spatial indexes for proximity and containment queries. The package encapsulates the internal mechanics of creating, populating, and refreshing the R-tree and quadtree spatial index structures that accelerate geometry-based lookups.

The package is declared with AUTHID current_user, meaning it executes with the privileges of the calling user rather than the definer. This design is relevant in EBS, where custom or third-party code invoked under the APPS schema may call into the package; the invoking session's privilege context is preserved. From an ETRM perspective, SDO_IDX is classified as OTHER and is referenced by three other packages, indicating that it functions as a lower-level utility layer rather than a directly user-facing API.

Key Procedures and Functions

  • IE_CRT_GEOMETRY_METADATA — Populates geometry metadata required before a spatial index can be built or used. It ensures the USER_SDO_GEOM_METADATA view contains the dimensional and bounds information Oracle Spatial needs.
  • CMT_IDX_CHNGS — Commits index change records accumulated during index maintenance operations, reconciling insert and delete counters (ins_no, del_no) against a specific schema, index name, and index partition.
  • ENDIANCONVERT — A deterministic, parallel-enabled function that converts a BLOB spatial index entry between big-endian and little-endian byte ordering, supporting cross-platform index portability.
  • TTS_INDEX_INITIALIZE — Initializes a transportable tablespace spatial index, accepting parameters such as index type, level, tiling, R-tree height, fanout, tablespace storage clauses, partitioning, geodetic flags, and root MBR. This is the most parameter-rich routine in the package and is used when moving spatial indexes between databases.
  • PROCESS_PARAMS — Parses a parameter string and applies an inversion mask to derive destination, units, and mask values, supporting internal parameter normalization for index operations.

Tables Accessed

The ETRM metadata documents no tables referenced via APPS synonyms for this package, which is consistent with its MDSYS ownership — its native dependencies are MDSYS spatial dictionary tables and views rather than EBS application tables. In practice it reads and writes the internal SDO_INDEX_METADATA and related dictionary structures that track index state, and it operates against the target geometry column's index table named by the caller. Because EBS spatial columns reside in application tables, any index maintenance performed through this package indirectly affects those application objects.

Usage Notes

SDO_IDX is not exposed through any standard EBS form or concurrent program; it is an internal Oracle Spatial component. EBS DBAs and developers encounter it indirectly when creating or rebuilding spatial indexes with CREATE INDEX ... INDEXTYPE IS MDSYS.SPATIAL_INDEX, and when invoking transportable tablespace procedures such as SDO_UTIL or the tts_index_initialize path. Custom code should never call SDO_IDX directly, as its signature is undocumented and subject to change across database releases. The search term "SOUNDEX() in sfmc" reflects a separate, unrelated string-matching concern; SOUNDEX has no association with SDO_IDX or Oracle Spatial indexing, and the two should not be conflated when troubleshooting EBS spatial or matching requirements.