Oracle Spatial (9.0.1) on Sun Solaris 32 bit

Question

Here's some sql*plus output. My question is below:
SQL> DELETE from user_sdo_geom_metadata;
1 row deleted.
SQL> DROP INDEX geometry_idx FORCE;
Index dropped.
SQL> INSERT INTO USER_SDO_GEOM_METADATA
2 VALUES ('geometry'
3 ,'sdo_geometry'
4 ,MDSYS.SDO_DIM_ARRAY(MDSYS.SDO_DIM_ELEMENT('X', -
180.0, 180.0, 0.00005)
5 ,MDSYS.SDO_DIM_ELEMENT('Y', -
90.0, 90.0, 0.00005)
6 ,MDSYS.SDO_DIM_ELEMENT('Z', -
99999.0, 99999.0, 0.00005))
7 ,8307);
1 row created.
SQL>
SQL> DELETE from geometry;
1 row deleted.
SQL> insert into geometry
2 values(1,'N',MDSYS.SDO_GEOMETRY
(3003,8307,NULL,MDSYS.SDO_ELEM_INFO_ARRAY(1,2003,1)
3 ,MDSYS.SDO_ORDINATE_ARRAY(12,13,GetZ
(12, 13)
4 ,12,14,Get
Z(12, 14)
5 ,12,15,Get
Z(12, 15)
6 ,12,16,Get
Z(12, 16)
7 ,12,13,GetZ(12, 13))));
1 row created.
SQL> CREATE INDEX geometry_idx ON geometry (sdo_geometry)
2 INDEXTYPE IS MDSYS.SPATIAL_INDEX
3 PARAMETERS('TABLESPACE=INDX SDO_INDX_DIMS=2');
CREATE INDEX geometry_idx ON geometry (sdo_geometry)
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE
routine
ORA-13236: internal error in R-tree processing: [specified index
dimensionality
should be 2 for geodetic layers]
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_9I", line 7
ORA-06512: at line 1
Why am I getting this error message? The getz you see
referenced when I insert the geometry object is a function that
returns the elevation at the lat long and this function is
working correctly.
Anyone know what the problem is here? I need a 3-dimensional
geometry (lat, lon, elevation) based on SRID 8307 (WGS84). I
can't seem to create an index for it. The only way I can get
this to work is to eliminate the Z value from the
user_sdo_geom_metadata and change the gtype to 2003.
Thanx in advance.

Answer 1

Hi Frank,
This is a bug in 9.0.1. It is fixed in 9.2 and
backported to 9.0.1.2 (rdbms 9.0.1.2 patch). Note that you
need to specify the sdo_indx_dims=2 in the parameter clause.
As a workaround in 9.0.1.0 you could do:
(1) remove the z coordinate (as you mentioned),
(2) set the srid to null (instead of 8307) both in
the geometries as well as the index metadata,
(3) set geodetic=false in the create-index parameters.
Hope that helps,
Ravi.