Search Results sdo_stattab

Overview

MDSYS.SDO_PRIDX is an Oracle Spatial component package that resides in the MDSYS schema, the schema owned by Oracle that holds the Spatial and Locator data types, operators, and supporting PL/SQL infrastructure. The suffix "PRIDX" denotes a primary index handler: the package implements the domain index interface that Oracle uses when a spatial index is created on a geometry column. In the Oracle EBS 12.1.1 and 12.2.2 environments, this package is not an E-Business Suite application object; it is part of the Oracle Database option set that EBS inherits because the EBS database tier is a standard Oracle database. Its business function is therefore infrastructural rather than transactional: it allows spatial queries issued against tables containing SDO_GEOMETRY columns to be resolved efficiently through an R-tree spatial index. Any EBS customization, third-party extension, or localization that stores geographic or spatial data in the EBS database depends on this package being present and valid.

Key Procedures and Functions

The ETRM documentation records this object as a package with zero explicitly documented procedures or functions; the metadata captures the object as VALID with both a package specification and a package body. In practice, SDO_PRIDX implements the routines required by the Oracle Data Cartridge / domain index interface, including the ODCIIndexInfo-driven entry points that Oracle invokes for index creation, index maintenance on DML, and cost and selectivity estimation during query optimization. Because the published metadata does not enumerate callable subprograms, no parameter lists are asserted here. The package should be treated as an internal, non-API package that is not intended for direct invocation by application developers.

Tables Accessed

The documented dependency information shows SDO_PRIDX referencing MDSYS.SDO_NUMTAB and MDSYS.SDO_STATTAB. SDO_NUMTAB is a Spatial number table used to pass collections of numeric values between the domain index layer and the Spatial engine, while SDO_STATTAB is the spatial statistics table that stores index statistics used for cost-based optimization of spatial predicates. These tables are read and written as part of index metadata and statistics maintenance rather than as application data stores. The package also has a documented dependency on SDOCURPKG, a Spatial utility package, and on SYS.ODCIINDEXINFO, the Data Cartridge type that carries index name, parameters, and column information into domain index routines. References to DBMS_ROWID, ODCICONST, and PLITBLM are additionally recorded through APPS synonyms in the 12.2.2 metadata, reflecting ROWID manipulation, Data Cartridge constants, and PL/SQL table management used internally by the index implementation.

Usage Notes

SDO_PRIDX is invoked indirectly. It is called by the Oracle kernel when a spatial index is built, rebuilt, or maintained, and when the optimizer evaluates a spatial operator such as SDO_FILTER, SDO_RELATE, SDO_WITHIN_DISTANCE, or SDO_ANYINTERACT against an indexed geometry column. It is not designed to be called from EBS forms, concurrent programs, or custom PL/SQL. Administrators encounter it only when diagnosing invalid objects in the MDSYS schema, when validating or rebuilding spatial indexes after a database upgrade, or when running the Oracle Spatial validation and upgrade scripts that recompile MDSYS packages. In EBS 12.1.1 and 12.2.2, the correct operational stance is to leave the package untouched: it is delivered by the database, patched by database patch sets or the Spatial option bundle, and any manual recompilation should be performed only through the supported Oracle Spatial scripts and as MDSYS or SYSDBA. Custom code should never reference MDSYS.SDO_PRIDX directly; instead it should use the supported Spatial operators and index DDL.