Unable to execute spatial operators when the layer is partitioned, underlying DBMS error 'ORA-29902: error in executing ODCIIndexStart() routine' when using Spatial type for Oracle.
Last Published: August 25, 2014No Product Found
Bug ID Number
NIM012924
Submitted
November 8, 2007
Last Modified
June 5, 2024
Applies to
No Product Found
Version found
9.3
Version Fixed
9.3
Status
Fixed
The bug has been fixed. See the Version Fixed and Additional Information, if applicable, for more information.
Description
Performing a spatial query or using a st_geometry relational operator against a partitioned table with local st_spatial indexes fails with the following Oracle error ORA-29902:
"SQL> SELECT owner, address, parcel_id 2 FROM parcels 3 WHERE st_envintersects(shape,:1,:2,:3:,:4) = 1;
SELECT owner, address, parcel_id * ERROR at line 1: ORA-29902: error in executing ODCIIndexStart() routine ORA-00942: table or view does not exist ORA-06512: at "SYS.DBMS_SYS_SQL", line 906 ORA-06512: at "SYS.DBMS_SQL", line 39 ORA-06512: at "SDE.SPX_UTIL", line 1173 ORA-06512: at "SDE.ST_DOMAIN_METHODS", line 137."
Cause
An error is occurring in the sde.spx_util package, when building an internal cursor used for spatial queries or relational operators.
Workaround
Do not use Oracle partitioning with st_geometry attributes when a spatial index is required.
Contact ESRI Support Services if further assistance is required or additional information is needed.