Category: Spatial
-
ORA-30554 errors on Function-Based Spatial Indexes after Spatial Bundle Patch
After applying the Spatial Bundle Patch, ORA-30554 errors may occur on functional indexes that use spatial operators. Functional indexes provide the benefit of spatial indexing but can become disabled after changes to dependent functions. Specific commands are required to re-enable them. This blog post provides details on handling spatial operations, managing indexes, and troubleshooting issues that arise after updates.
-
A 3D data with a 2D SRID may result with ORA-13029 #JoelKallmanDay
This post discusses the importance of correctly storing 3D geometry with an appropriate 3D Spatial Reference Identifiers (SRIDs) following Oracle’s upgrade to version 19c. It details the ORA-13029 error encountered when a 3D data stored with a 2D SRID and provides solutions, including applying patch 31022826 and setting event 54713. Alternatively, it suggests updating metadata with an equivalent 3D SRID and recreating the spatial index as another solution.
-
“spatial_vector_acceleration” parameter improves Oracle spatial vector query performance
Oracle Database 12c and above introduce significant speed improvements for spatial operations. The SPATIAL_VECTOR_ACCELERATION parameter, set to TRUE, enhances index performance, geometry engine efficiency, and CPU and memory usage. Oracle Spatial and Graph is included in the Oracle Database license at no extra cost. Rebuilding spatial indexes with INDEXTYPE=MDSYS.SPATIAL_INDEX_V2 can simplify index management and improve performance for specific queries.
-
Dropping unused MDRT tables in Oracle database
The MDRT_$ tables in Oracle Spatial are crucial for spatial indexes and should not be moved, altered, or replicated. It’s possible to drop unrelated tables if using Oracle DB version 12cR2 or later. While MDXT_# tables, which supported spatial index statistics, can be dropped after use, changes to the tablespace for MDRT_# tables are permitted. Queries are provided to identify and clean up unnecessary tables, resulting in a significant reduction in table count.
Osman’s DBlog 