Search Results sdo_mbr




Overview
Explore in AI Chat

Overview

MDSYS.RTREE_IDX is an Oracle Spatial (SDO) index type package belonging to the MDSYS schema, the schema that owns Oracle's spatial and locator components. Within the Oracle E-Business Suite 12.1.1 and 12.2.2 technology stack, this package is not an EBS application object in its own right; it is part of the underlying Oracle Database Spatial option on which certain EBS modules depend. Its business function is to implement the R-tree spatial indexing scheme, which organizes spatial data (geometry and geography columns) into a hierarchical, minimum-bounding-rectangle structure so that location-based queries can be resolved efficiently rather than through full-table geometry scans.

The package is registered as an extensible index type. It supplies the implementation of the ODCI (Oracle Data Cartridge Interface) routines that the database invokes when a spatial index is created, maintained, or queried. The reference to SDO_MBR, the minimum bounding rectangle type, confirms that the R-tree implementation constructs and compares bounding rectangles during index build and maintenance. EBS objects that store spatial geometry — for example site, asset, or network location columns created with the SDO_GEOMETRY datatype and indexed for proximity searching — rely indirectly on this package whenever their spatial index is exercised.

Key Procedures and Functions

The ETRM metadata records zero explicitly documented procedures or functions for this object; the package is classified under the API grouping OTHER. The metadata instead exposes the package through its dependency graph rather than a public API listing. RTREE_IDX references ODCIENV and ODCIINDEXINFO, the ODCIIndex environment and index-information structures, indicating that the package body consists of ODCIIndex interface implementations (the standard create, drop, insert, update, delete, and query/scan operations required of any extensible index type) together with internal helper logic for building and probing the R-tree.

No parameter lists are published in the metadata, and none should be assumed. The package is intended to be driven by the Oracle Spatial kernel and the query optimizer, not called directly by application code. The one documented internal relationship is that RTREE_IDX is referenced by another MDSYS object, RTREE_INDEX_METHOD, which acts as the registered index method definition that binds the R-tree type to the database. MDSYS.RTREE_IDX also references itself, reflecting the recursive descent typical of tree-based index traversal, and depends on STANDARD for base PL/SQL functionality.

Tables Accessed

The metadata lists no tables accessed via APPS synonyms. This is expected: RTREE_IDX operates against the index and table segments supplied through the ODCI index interface at runtime rather than against fixed, named application tables. The data it manipulates is the user's spatial index itself and the associated geometry columns of the base table being indexed. Spatial metadata describing the index, its dimensionality, and its bounds resides in the MDSYS spatial metadata views, but RTREE_IDX does not reference application dictionary tables and has no documented dependency on EBS transactional tables.

Usage Notes

RTREE_IDX is invoked implicitly by the Oracle Database whenever a spatial R-tree index is created or used. In an EBS context this occurs through standard SQL and DDL, for example a CREATE INDEX ... INDEXTYPE IS MDSYS.SPATIAL_INDEX statement, or a spatial operator such as SDO_WITHIN_DISTANCE or SDO_RELATE in a query predicate. Application developers and DBAs do not call the package directly from forms, concurrent programs, or custom PL/SQL; doing so would bypass the supported interface.

Because the package is owned by MDSYS and is Oracle proprietary, it must never be modified or recompiled outside the supported Oracle Database upgrade or patch process. It is validated as part of the database's internal consistency check (for example, by utlrp or the object validity verification performed post-patch). Its presence and VALID status confirm that the Spatial option is correctly installed and functional on the EBS database tier.