Search Results sdo_relate
Overview
MDSYS.SDO_3GL is a wrapped Oracle Spatial and Graph package that provides the spatial geometry engine underlying the Oracle Locator and Oracle Spatial feature set. In Oracle EBS 12.1.1 and 12.2.2, the E-Business Suite database is hosted on an Oracle Database instance that includes Oracle Spatial (MDSYS schema) as a standard option, and SDO_3GL is one of the internal packages shipped with that option. Its name reflects its role: a "3GL" (third-generation language) interface that exposes low-level geometry processing routines used by higher-level Spatial operators and by EBS modules that store and query spatial data. The package is owned by MDSYS and classified under the ETRM as API classification "OTHER"; it is not an Oracle EBS Applications-owned API, and it is not intended to be called directly by application code.
Key Procedures and Functions
The ETRM documentation for this object records zero documented procedures or functions. This is expected: SDO_3GL is a wrapped PL/SQL package, as evidenced by the wrapped source in the documentation excerpt. Wrapped packages have their bodies obfuscated into an unreadable bytecode-like representation, and their internal routine signatures are deliberately hidden from the data dictionary views and documentation that ETRM harvests. Consequently, no procedure or function names, parameters, or signatures are published here.
Functionally, SDO_3GL is known to contain the primitive geometry computation routines that support spatial operations such as intersection, union, distance, area, length, buffer, and validity checking. These routines are invoked indirectly through the public SDO_GEOM and SDO_UTIL APIs and through Spatial operators used in SQL. Any attempt to call SDO_3GL routines directly would be unsupported and version-dependent.
Tables Accessed
The ETRM metadata records three objects referenced through APPS synonyms: ALL_IND_EXPRESSIONS, DUAL, and PLITBLM.
- ALL_IND_EXPRESSIONS — a data dictionary view exposing function-based index expressions on accessible indexes. SDO_3GL or its installation/validation logic may consult it when evaluating index-based spatial queries or when validating that a spatial index is usable.
- DUAL — the standard one-row utility table used for expression evaluation and control-flow checks.
- PLITBLM — an internal Oracle support table used by PL/SQL instrumentation and error-tracing machinery; its appearance indicates the wrapped package carries standard PL/SQL runtime instrumentation.
No EBS application tables are referenced, confirming that SDO_3GL operates purely on Spatial data structures, not on EBS business data.
Usage Notes
SDO_3GL is not invoked directly by Oracle EBS forms, concurrent programs, or business APIs. It is called transparently by Oracle Spatial whenever a spatial predicate, operator, or geometry function is executed. In an EBS 12.1.1 or 12.2.2 environment, this occurs in scenarios such as spatial-enabled location data, customer or site geo-coordinates, asset maps, and any custom or third-party extension that stores SDO_GEOMETRY columns and uses MDSYS spatial operators. The package is also referenced by 31 other packages, reflecting its role as a shared internal dependency rather than a standalone entry point.
Because the package is wrapped and owned by MDSYS, it must never be modified, renamed, or called directly. Troubleshooting should target the public Spatial APIs (SDO_GEOM, SDO_UTIL, SDO_CS) and the database version's Spatial patch set. The ETRM classification of "OTHER" and the absence of documented routines signal that this object is present in the environment as infrastructural support, not as a supported EBS customization surface.
-
SYNONYM: PUBLIC.SDO_RELATE
12.2.2
owner:PUBLIC, object_type:SYNONYM, object_name:SDO_RELATE, status:VALID,
-
OPERATOR: MDSYS.SDO_RELATE
12.1.1
owner:MDSYS, object_type:OPERATOR, object_name:SDO_RELATE, status:VALID,
-
SYNONYM: PUBLIC.SDO_RELATE
12.1.1
owner:PUBLIC, object_type:SYNONYM, object_name:SDO_RELATE, status:VALID,
-
OPERATOR: MDSYS.SDO_RELATE
12.2.2
owner:MDSYS, object_type:OPERATOR, object_name:SDO_RELATE, status:VALID,
-
SYNONYM: PUBLIC.ST_RELATE
12.1.1
owner:PUBLIC, object_type:SYNONYM, object_name:ST_RELATE, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
SYNONYM: PUBLIC.ST_RELATE
12.2.2
owner:PUBLIC, object_type:SYNONYM, object_name:ST_RELATE, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
INDEXTYPE: MDSYS.SPATIAL_INDEX
12.2.2
owner:MDSYS, object_type:INDEXTYPE, object_name:SPATIAL_INDEX, status:VALID,
-
INDEXTYPE: MDSYS.SPATIAL_INDEX
12.1.1
owner:MDSYS, object_type:INDEXTYPE, object_name:SPATIAL_INDEX, status:VALID,
-
PACKAGE: MDSYS.SDO_3GL
12.2.2
owner:MDSYS, object_type:PACKAGE, object_name:SDO_3GL, status:VALID,
-
PACKAGE: MDSYS.SDO_3GL
12.1.1
owner:MDSYS, object_type:PACKAGE, object_name:SDO_3GL, status:VALID,
-
TYPE: MDSYS.ST_GEOMETRY
12.1.1
owner:MDSYS, object_type:TYPE, object_name:ST_GEOMETRY, status:VALID,
-
TYPE: MDSYS.ST_GEOMETRY
12.2.2
owner:MDSYS, object_type:TYPE, object_name:ST_GEOMETRY, status:VALID,
-
TYPE: SYS.ODCIINDEXCTX
12.1.1
owner:SYS, object_type:TYPE, object_name:ODCIINDEXCTX, status:VALID,
-
TYPE: SYS.ODCIINDEXCTX
12.2.2
owner:SYS, object_type:TYPE, object_name:ODCIINDEXCTX, status:VALID,
-
TYPE: MDSYS.SDO_INDEX_METHOD_10I
12.2.2
owner:MDSYS, object_type:TYPE, object_name:SDO_INDEX_METHOD_10I, status:VALID,
-
TYPE: MDSYS.SDO_INDEX_METHOD_10I
12.1.1
owner:MDSYS, object_type:TYPE, object_name:SDO_INDEX_METHOD_10I, status:VALID,
-
TYPE: MDSYS.SDO_GEOMETRY
12.1.1
owner:MDSYS, object_type:TYPE, object_name:SDO_GEOMETRY, status:VALID,
-
TYPE: MDSYS.SDO_GEOMETRY
12.2.2
owner:MDSYS, object_type:TYPE, object_name:SDO_GEOMETRY, status:VALID,
-
PACKAGE: SYS.STANDARD
12.1.1
owner:SYS, object_type:PACKAGE, object_name:STANDARD, status:VALID,